Skip to content
Back to blog tecnologia

How to Migrate from Glop POS to a Cloud TPV Without Losing Data (Perpetual or Cloud)

By Pablo Bouzon · 22 May 2026 ·8 min read
How to Migrate from Glop POS to a Cloud TPV Without Losing Data (Perpetual or Cloud)

Glop has two customer profiles that in 2026 are asking themselves the same question for different reasons.

The first: perpetual-licence users. They bought it a few years back, it feels like it’s “already paid for”, and suddenly they’re facing the Verifactu obligation — which Glop’s old firmware doesn’t cover — with a paid per-terminal upgrade and tight deadlines. This isn’t a hypothetical scenario: Glop is one of the few Spanish POS systems with a genuine perpetual licence, and that model now sits awkwardly alongside the AEAT’s (Spanish tax agency) tax regulations.

The second: Glop cloud users. The base fee is reasonable (€35/month), but the stock and inventory module is separate (€15–25/month), so is the kitchen display, and the total ends up higher than expected. If you also need table bookings or your own online ordering, you’re contracting even more suppliers.

The good news: technical migration away from Glop — in either of its two versions — isn’t especially complex. The key data can be exported, standard hardware is reusable, and the transition period with both systems running in parallel is enough for the team to build confidence before the final cutover.

What data you can export from Glop (and what you can’t)

Before planning the migration, you need to know exactly what carries over to the new system.

What you can export:

  • Product catalogue: Glop lets you export the item list with prices, families and taxes from the web backoffice or the local admin panel. The usual format is CSV or Excel. This is the most valuable data — it saves you rebuilding the whole menu from scratch. Before importing: check VAT per item (alcoholic drinks at 21%, food at 10%, takeaway at 10%), current prices and names without special characters that could break the import.

  • Sales history: available from Glop’s reports module for a date range, as PDF or Excel. It isn’t importable into the destination system (every POS has its own internal database), but it’s your tax reference and your baseline for comparing metrics before and after the switch.

  • Cash closes: keep the PDFs for at least the last full tax year. They’re your backup for any Tax Agency inspection.

What doesn’t carry over automatically:

  • Modifiers and extras groups: Glop’s item CSV generally doesn’t include modifier groups in importable format (meat doneness, sides, priced extras). You’ll need to recreate them on the new system. In practice that’s 2–5 groups with 4–8 options — 45 minutes of work.

  • Perpetual licence configuration: if you have Glop on a perpetual licence, the licence file sits on Glop’s local PC or server. It doesn’t migrate — nor does it need to. The new system is 100% cloud and needs no local licence.

  • Glop’s proprietary hardware: Glop runs well on Windows PCs with a touchscreen. The standard hardware you already have — if it’s a generic touchscreen PC or a standard Android tablet — is reusable with any web-based POS. So is a network-connected ESC/POS kitchen printer. The only hardware that may become obsolete is proprietary terminals locked by Glop’s distributor for the perpetual version — confirm with the distributor whether the device can access Chrome or Firefox before assuming it will work.


The three-phase migration plan

Phase 1 — Preparation (1–2 weeks before cutover)

Don’t cancel Glop yet. You need it active to export data and as a safety net during the transition.

What to do in this phase:

  1. Export the catalogue from Glop’s backoffice and review it line by line. Pay particular attention to VAT per category and to items with variable pricing or mandatory modifiers. VAT errors in the CSV carry over to the new system and can affect the Verifactu hash chain from the very first receipt.

  2. If you’re on a perpetual licence, check the Verifactu status of your Glop version before cutover. Ask the distributor for the upgrade documentation and which firmware version includes it. The migration process doesn’t depend on Glop having Verifactu active — but you need to know whether your current version already generates valid receipts for the AEAT or not, so you can set the cutover date with proper judgement.

  3. Activate the new POS in parallel. If you’re migrating to Bouzon POS, onboarding imports the catalogue from the Glop CSV or from a photo of your physical menu using AI (useful if the CSV has inconsistencies). The system is 100% web-based — nothing to install on terminals, it runs from any browser on the Android device, iPad or Windows PC you already have.

  4. Set up the kitchen printer with the new system. If your ESC/POS printer is network-connected (has a local IP on the router), setup is immediate: you enter the IP and send a test receipt. If it’s connected via USB directly to the Glop PC, you’ll need to switch to a network connection or install the local printing agent — a 10–15 minute process with the setup guide.

  5. Activate Verifactu on the new POS before cutover day. With perpetual Glop, this is the step that depends on the firmware upgrade and the distributor. On Bouzon POS, the Verifactu module is included in the base fee — it’s activated from the Billing panel by uploading the FNMT certificate and the establishment’s tax details. The first receipt issued starts the hash chain logged with the AEAT. No extra cost, no firmware upgrade, no dependency on system version.

  6. Train the team during a quiet shift. Monday lunchtime is usually the best moment. The main workflow the team needs to master: open table → add items with modifiers → send the order to the kitchen → take payment. With 30–45 minutes of pressure-free practice, the team has enough.


Phase 2 — Running in parallel (1–2 weeks)

This is the step most migrations skip, and it causes the most problems when it’s missing.

During this phase, use the new POS for one specific shift — only Monday-to-Wednesday lunches, for example — while Glop stays active for the rest of service. This lets you:

  • Spot items that didn’t import correctly (prices, VAT, missing modifiers).
  • Confirm the kitchen printer receives well-formatted orders from the new system.
  • Verify Verifactu receipts generate correctly: sequential number, validation QR code, the establishment’s tax details.
  • Build the team’s confidence without the pressure of a full service.

The criterion for moving to phase 3: when the team chooses to use the new system even when it isn’t mandatory, you’re ready.


Phase 3 — Cutover day

The final switch should happen on a quiet day — Monday or Tuesday, never a Friday or Saturday, and outside high season or local holidays. The day’s process:

  1. Close every open ticket in Glop before shutting the system down. No pending orders and no open table tabs.
  2. Run the end-of-day cash close in Glop and save the PDF alongside the sales history exported during the preparation phase.
  3. Verify Verifactu on the new POS. Issue a test receipt (a coffee, €1.50) and confirm the PDF includes the AEAT validation QR code, the correct sequential number and the establishment’s tax details. Scan the QR code with your phone: it should redirect you to the Tax Agency’s verification page.
  4. Cancel Glop or notify the distributor according to your contract terms. For a perpetual licence there’s no monthly fee to cancel, but if you had an active annual maintenance contract, check the early-termination terms.

How long it takes and how much you save

The full migration across the three phases takes 3 to 5 weeks. For a small bar with a simple operation the process can be compressed to 2 weeks, but the parallel-running period is worth it for any venue with a separate kitchen or more than 15 covers.

Real cost comparison for a venue with 1 active terminal, kitchen printer, stock module and mandatory Verifactu in 2027:

Glop cloud (base + stock)Glop perpetual licence (24m)Bouzon POS + Stock & Recetas
Monthly fee~€50–60/month0 (paid off) + maintenance€49.98/month
Cost over 24 months~€1,440–1,920~€1,900–2,100 (terminal + 2 yrs maintenance + Verifactu upgrade)~€1,200
VerifactuModule included in cloudPaid upgrade (~€200/terminal, uncertain date)Included in the base fee
Stock and inventoryExtra module (+€15–25/month)HiOffice or additional moduleIncluded in the bundle
Automatic stock decrement on saleYes (stock module)Yes (if you have the module)Yes, configurable
Hardware requiredWindows PC or tabletProprietary or compatible Windows PCAny tablet, iPad or PC (browser)

The saving versus Glop cloud with the necessary modules is €240–720 over 24 months. Versus the perpetual licence with the Verifactu upgrade, the saving is similar — without the uncertainty over the upgrade’s date and cost.

But the real saving isn’t only in the POS. If your restaurant wants its own bookings (without paying TheFork commission) and online ordering (without giving up margin to Glovo), the comparison changes scale. Bouzon scales website + bookings + shop + POS + Stock & Recetas under a single account — the full stack replaces Glop + CoverManager or TheFork + Glovo + an agency website with a single subscription, with savings reaching €15,000–€20,000 over 24 months versus the typical “Glop + TheFork + Glovo + freelance website” model.

To see how it works on your current device without installing anything, try the POS demo →


Frequently asked questions about migrating from Glop

Can I keep using the PC or tablet where I had Glop installed?

If the device has access to Chrome or Firefox (and almost every Windows PC running Glop does), yes. Bouzon POS is 100% web-based — you open the browser, enter the venue’s URL and the POS is up and running. No installation, no specific driver, no dependency on the operating system. Proprietary devices locked by Glop distributors for the perpetual licence may have browser-usage restrictions; confirm compatibility with the distributor before assuming it.

What happens to the Verifactu hash chain when I switch systems?

Every POS starts its own Verifactu hash chain from the first receipt. When you switch systems, Glop’s previous chain closes at the last receipt you issued — that’s correct and expected. Bouzon POS’s new chain starts from sequential number 1 on the new system. Both coexist with the AEAT without conflict. What matters is not issuing receipts in parallel from both systems on the same day for the same tax ID — coordinate a clean cutover on day 3.

Which version of Glop includes Verifactu, and when does it reach the perpetual licence?

Glop cloud has Verifactu built into its current version. For the perpetual licence, Verifactu support requires a version upgrade that the distributor handles separately — the cost and availability vary by distributor and region. If your distributor hasn’t given you a specific date and a fixed price for the upgrade, that’s exactly the risk we mention in the comparison of Glop alternatives.

Do I lose my sales history when I migrate?

Not in the sense that matters. Glop’s sales history is exported onto your local machine and in the cash-close PDFs — that data is yours. What doesn’t migrate is access to the sales history from within the new POS, because each system has its own database. If you need to check sales from the Glop period, you do it from the reports exported during the preparation phase.

Is Bouzon POS compatible with the standard ESC/POS printers I already have with Glop?

Yes. Bouzon POS supports any ESC/POS printer with a network connection (local IP) or USB (via the local printing agent). The Epson, Star and generic Chinese printers that work with Glop also work with Bouzon POS. If you have a Sunmi V2 Pro or an Android device with a built-in printer, those are also supported via the Android agent. The only exception is proprietary printers locked by Glop distributors with restricted firmware — rare, but they exist in some service contracts.