From first call to go-live, without the drama.
A move to TABS is a project we have run many times. Here is how it goes, what we need from you, and how we help you switch from spreadsheets, a generic EPOS or a legacy merchant system.
- Discovery, doneSites, tills, channels, accounts
- Data migration, done8,412 products, 19 checks passed
- 3Configuration, in progressPricing, carriers, permissions
- 4Training, bookedTill team Tue, back office Wed
- 5Go-live, date agreedCut-over planned around trading
- 6Ongoing, after go-liveUK support from the builders
Six steps, one team.
The same people run every step, so nothing is lost between a salesperson, an implementer and a support desk.
- 1
Discovery
What you sell, how many sites and tills, which channels and couriers, which accounts package, and what hurts today.
- 2
Data migration
Supplier catalogues and prices from the ETABS Hub. Products, customers, accounts and opening stock brought across through our dedicated migration workflow and checked by Data Health.
- 3
Configuration
Pricing tiers and customer pricing, carrier rules, user permissions, document templates, label formats and the integrations you use.
- 4
Training
On your own data, on site or remotely, role by role. The till takes minutes; the back office takes a morning per role.
- 5
Go-live
Hardware supplied and configured before it arrives, cut-over planned around your trading pattern, and the team on hand for the first days.
- 6
Ongoing
UK support from the people who built it, in-app bulletins for every release, and a feature-request route that shapes the roadmap.
Moving from something else? We help you make the move.
Whatever you run today, the migration path exists because a customer has already walked it.
From spreadsheets
Your product and customer sheets are brought across through our migration workflow. Data Health finds the duplicates and gaps before go-live.
From a generic EPOS
Products and customers exported from your current till are loaded and checked. The trade-counter, purchasing and warehouse depth arrives on day one.
From a legacy merchant system
Accounts, credit terms and contract pricing migrated in a planned cut-over, with the server, the upgrade fees and the version numbers left behind.
What customers and consultants say
Throughout all this experience, ETABS have been the stand-out providers of business technology to any of the companies I have supported. They deliver all the essential features of enterprise solutions, without the unnecessary extras.
Works with the rest of TABS
Onboarding questions, answered
How long does a move to TABS take?
It depends on the size of your business and the modules you need, so we agree a plan and a date with you at the start rather than quoting a number here. Discovery tells us what has to move and what can wait.
Do I have to stop trading to switch?
No. Data is migrated and checked ahead of go-live, hardware is configured before it arrives, and we plan the cut-over around your trading pattern.
What data can you migrate?
Products, customers, accounts and opening stock. Supplier catalogues and prices come from the ETABS Hub. Your own product and customer records are brought across through our dedicated migration workflow, and Data Health checks the result before you go live.
Who trains my staff?
We do, on your own data, on site or remotely. The till is designed to be learnt in minutes; the back office is taught role by role.
What happens after go-live?
UK support from the people who built the system, in-app bulletins for every release, and a feature-request route that has produced most of what is on this site.
Tell us what you run today. We will map the move.
Book a demo with the people who build TABS. We will show the parts that matter to your business, not a canned tour.
See TABS on data like yours.
Tell us what you use today and we will describe the migration path before the demo.