Migrating EPOS systems in 2026

Last updated: 11 April 2026

Most pubs think migrating EPOS systems takes a weekend and a bit of training. Then reality hits: you’re three days in, your bar staff can’t find anything, stock counts are wrong, and you’ve lost track of yesterday’s takings. The real cost of migrating EPOS systems isn’t the monthly fee—it’s the staff training time and lost sales during those first two weeks of use. I’ve watched licensees stick with aging systems they hate because the thought of migration feels worse than the pain they’re already living with. It doesn’t have to be that way.

When I was evaluating systems for Teal Farm Pub in Washington, Tyne & Wear, the migration question was unavoidable. The real test came during a Saturday night with a full house, card-only payments, kitchen tickets, and bar tabs running simultaneously—exactly when you can’t afford for anything to go wrong. That pressure taught me what actually matters when migrating EPOS systems, and what’s just vendor noise.

This guide walks you through the entire migration process as it happens in real UK pubs. You’ll learn how to plan the switch without losing revenue, how to train staff properly, how to handle the first week of chaos, and how to avoid the mistakes that turn a migration into a nightmare.

Why you should migrate (and when not to bother)

The most important question before migrating EPOS systems is whether you actually need to. If your current system works, if it’s integrated with your accounting software, and your staff know it inside out, the pain of migration might outweigh the benefit. But if you’re sitting with a system that requires workarounds, if staff spend time on manual tasks that the new system could automate, or if you’re locked into a contract that punishes you financially, migration makes sense.

I hear “my current till works fine, why change it?” at least once a month from licensees. The answer depends entirely on what “works fine” means. If you mean “it processes payment,” that’s different from “it gives you real-time stock counts, integrates with your accounts, and doesn’t require three manual spreadsheets to close.” The real value of modern EPOS isn’t the till itself—it’s the data you can access to run your pub better.

Wet-led pubs have completely different EPOS requirements to food-led pubs, and most comparison sites miss this entirely. If you’re running food service, a kitchen display system saves more money than any other single feature. But if you’re a wet-led only pub with no food, you need a different conversation. You need fast payment processing, accurate stock rotation for cellar management, and the ability to run tabs. You don’t need kitchen integration or course sequencing. Before you migrate, make sure your new system is actually built for your pub type.

One more reality check: do pubs actually need EPOS systems? Yes—but not the most expensive one on the market. The question is whether your current system is costing you more in lost efficiency than a new one would cost to implement.

Planning your migration timeline

Migrating EPOS systems requires 4-6 weeks of planning before you press go live—not including the weeks after launch. If you try to rush it, you’ll pay for it in staff confusion and lost sales during your busiest trading days.

Start by setting your go-live date. Here’s the critical bit that most people get wrong: don’t go live on a Friday. Don’t go live during a quiz night, a sports event, or a match day. Don’t go live when you’ve got an event booked or staff holidays scheduled. At Teal Farm, I learned this the hard way. The right time to migrate is a quiet Monday or Tuesday, ideally during a week when your trading is naturally quieter. Winter quiet periods work. Summer bank holidays don’t (you’ll be rammed). Choose a date where you can afford to run at 70% efficiency for a few days.

Next, choose your new EPOS system. This can’t be rushed. You need to:

• Test it with your specific pub type in mind (wet-led, food-led, mixed)
• Check pubco compatibility if you’re a tied pub tenant (this is non-negotiable for some pub groups)
• Verify it integrates with accounting software you’re already using (QuickBooks, Xero, whatever you’ve got)
• Ask the vendor directly: “How long does data migration take? What do you need from me?”
• Confirm offline functionality—what happens when the internet goes down?

Once you’ve signed the contract, give yourself at least 3 weeks before go-live. Your vendor will need access to your current system to extract data. You’ll need to provide a complete list of stock items, pricing structures, staff records, and customer data if you’re migrating that. If your current system is very old or proprietary, this becomes a manual exercise. Assume 2-3 weeks just for data extraction and verification.

In week two of your planning phase, start talking to staff. Tell them what’s happening, why it’s happening, and when. Let them ask questions. The anxiety of not knowing is worse than the reality of change. Create a simple one-page guide showing the new system layout and the three things they’ll do most often on it (usually: ring a sale, take payment, void a transaction).

Data migration and system setup

This is where most migrations go wrong. People assume data migration is instant and automatic. It isn’t. Your current till holds years of data: stock items, prices, staff records, customer history if you’re on a customer loyalty system. Moving it to a new system is not a copy-and-paste exercise.

Data migration requires manual verification of stock, pricing, and customer records before you go live, because automated migration often introduces errors that only show up after launch. When I migrated Teal Farm’s system, we discovered that our stock data had duplicates—three entries for the same lager under different names. Our pricing had notes in fields that didn’t import correctly. Customer records had inconsistent phone numbers and postcodes.

Here’s what actually happens:

• Week 1 of migration prep: Your vendor exports your data and provides it in a format their system understands. You receive a test import—a preview of what your data looks like in the new system.
• Week 2: You check the test import. Stock items: are they all there? Are the prices right? Do you have duplicate entries? Customer records: are addresses formatted correctly? Are phone numbers complete? This is tedious work, but it’s critical.
• Week 3: You fix errors in the test import and send it back to the vendor. They re-import. You verify again. Once it’s correct, you freeze any changes to your old system (you can’t update data in two places simultaneously).
• Go-live day: The vendor does the final import into the live system. You have a window of a few hours where you’re not taking payments—usually mid-afternoon on your chosen quiet day.

During this process, check that EPOS QuickBooks integration is set up if you use QuickBooks. If your accounts are handled by a bookkeeper or accountant, give them advance notice. The first P&L you run on the new system will look different because the data structure is different. Brief them so they’re not alarmed.

For tied pub tenants, verify before data migration that your pubco accepts the new EPOS system. Some pub groups have an approved list. If your new system isn’t on it, you might have compatibility issues later. Check this now, not after you’ve migrated.

Staff training that actually sticks

You can train staff for two hours and they’ll forget everything the moment they hit the new till under pressure. Real training happens over time, with repetition, and with immediate feedback. Plan for multiple training sessions, not just one.

Effective staff training requires at least three separate sessions before go-live, plus ongoing support for the first two weeks after launch. This is not optional—it’s the difference between a smooth migration and chaos.

Session one (one week before go-live): Overview and the three things they’ll do most. Show them the login screen, how to ring a sale, how to take payment. Let them hold a tablet or terminal and get comfortable with the interface. Keep it to 20 minutes maximum. Don’t overload them with features they won’t use.

Session two (three days before go-live): Hands-on practice. Set up a test till, ring some imaginary sales, take imaginary payments. Void a transaction (they will need this). Run through a tab. Ask each staff member to do it themselves. Watch where they struggle. That’s your focus area.

Session three (the day before go-live): Q&A and confidence building. By now they know the basics. Answer the “what if” questions. “What if the card machine stops working?” (It goes back to the till backup—show them where it is). “What if I ring something wrong and the customer sees it?” (Show them how to void and re-ring). “What if I forget my login?” (Tell them who to ask—usually you).

On go-live day itself, have an extra person in the bar if you can. You, a manager, or a senior staff member who’s comfortable on the new system. Their job is to help, not replace. Let staff use the new system with support available. They’ll be slower than usual. Accept this. A transaction that takes 30 seconds on the old till might take 50 seconds on the new one for the first few days. This is normal.

Managing 17 staff across front of house and kitchen at Teal Farm taught me that consistency matters more than perfection. If one person trains staff differently (telling them to do things in a different order, showing them different buttons), you end up with 17 different ways of using the same system. Before training, make sure everyone—you, your manager, your senior staff—all know the one correct way to do each task. Train the same thing the same way every time.

The first week: what to expect and how to survive it

The first 10-14 days after EPOS migration will be slower and messier than normal, and this is expected and temporary. You’re not failing. Your staff aren’t failing. You’re just in the adjustment period.

Day one will feel wrong. Everything feels slow. Your bar staff are thinking instead of reacting. They’re looking for buttons instead of knowing where they are. Your till reconciliation at close will take longer because you’re finding where all the data is. Close of play: you’ll have fewer transactions than usual and might have left some money unreconciled. Don’t panic. Write down what didn’t work, what felt slow, and what staff asked about. These are your learning points for day two.

Days two through five: things get faster. Staff start building muscle memory. By day three, most of your team will be faster on core tasks. By day five, the new system will start to feel normal. Expect till reconciliation to still take longer than your old system—you’re learning where everything is. Expect some voids and adjustments as staff figure out how to fix mistakes. These are all normal.

Days six through ten: this is when the real problems surface. It’s not the obvious stuff (like payment processing) but the edge cases. How do you apply a staff discount? Why did a customer loyalty discount not work? Can you print an invoice instead of a receipt? These questions mean staff are exploring the system beyond the basics. That’s good. It means they’re getting comfortable. Answer them patiently.

Days eleven through fourteen: most staff are faster on the new system than they were on the old one. Some edge-case questions remain. Your till reconciliation is now faster than it used to be. You’re starting to see the value of the new system—real-time stock counts, better reporting, whatever you bought it for.

During this whole period, keep your expectations realistic. If your till reconciliation was perfect on your old system, it won’t be perfect for two weeks on the new one. If you normally do £3,000 in a Wednesday, you might do £2,700 because service is slower. That’s okay. You’ll recover it once staff are comfortable.

One critical thing: don’t migrate mid-week and disappear. If you go live on a Monday, be on the premises Tuesday through Thursday. Not hovering over staff—just there, available, ready to fix problems quickly. If there’s a problem and you’re not there, staff will revert to the old system’s logic, which doesn’t work, and they’ll get frustrated. Your presence matters.

After migration: troubleshooting and optimisation

Once the chaos of the first week is over, you’ll start to notice that the new system has features your old one didn’t. This is when migration actually becomes valuable. But first, you need to troubleshoot the teething problems.

The most common post-migration issues are staff not knowing where features are located, till reconciliation discrepancies that reveal data entry errors, and payments that don’t sync to your accounting software. These are all solvable, but they need to be addressed in the right order.

If staff are still asking how to do something by week three, it’s time for a quick refresh session. Don’t assume they’ll figure it out eventually. Spend 10 minutes showing them. It saves everyone frustration.

If your till reconciliation is off by a few pounds, look at staff training first. The new system might require a different process for applying discounts or handling refunds. Older staff especially might not have shifted their mental model from the old system. Once staff are consistent, reconciliation becomes easier.

If payments aren’t syncing to your accounting software, this is a vendor issue. Contact your EPOS provider. It might be a settings issue or a missing integration step. Don’t assume you need to reconcile payments manually—most modern systems handle this automatically once they’re set up right. Using the pub profit margin calculator or other financial tools will reveal gaps in your data flow quite quickly.

Once the system is stable, start using the features that made you migrate in the first place. If you migrated for better stock management, spend time in the stock module. Learn what your par levels are, set up automated low-stock alerts, and do your stock counts using the system instead of on paper. If you migrated for kitchen integration, make sure your kitchen staff are using the display system correctly. If you migrated for better reporting, pull your first P&L from the new system and compare it to your accountant’s records to make sure the data is accurate.

Check whether cellar management integration is working properly. This matters more than most operators realise until they’re doing a Friday stock count manually and realising the system isn’t tracking their kegs correctly. If it’s not, ask your vendor for a setup check. Sometimes it’s just a configuration issue.

If your EPOS system isn’t working as expected after the first few weeks, it’s often because features aren’t configured for your specific operation. Don’t accept “that’s just how it works.” Ask your vendor to help configure it correctly.

After six weeks, your migration is complete. You’ve got a new system, your staff are comfortable, and you can measure whether it’s actually delivering the benefits you paid for. If it is, you’ve made the right choice. If it isn’t, you now know what to ask for in your next migration.

For more information, visit pub drink pricing calculator.

For more information, visit pub staffing cost calculator.

For more information, visit pub IT solutions guide.