How we work
Switch over a piece at a time: how a new system goes live without a big bang
The safest way to move a business onto a new system is a piece at a time: one part of the work switches over and settles before the next one starts. Here’s how that works, from moving the data to what the first fortnight looks like.
By Seb Lawson · 28 October 2026 · 5 min read
The safest way to move a business onto a new system is one piece at a time. Switch over one part of the work, let it settle, fix what needs fixing, then move on to the next. Avoid the big weekend where everything changes and the team walks into a different business on Monday. It sounds slower, but it’s usually quicker overall, because nothing grinds to a halt while you sort out a problem, and your team is using the first parts long before the last ones are finished.
Big-bang go-lives fail because every problem lands on the same day
When everything switches over at once, the team is learning new screens while customers are ringing, the data has gaps nobody spotted, and the one thing that doesn’t quite work holds up everything else. People quietly go back to their old spreadsheets within days. Then you have two systems and trust in neither.
Choose the order by risk and by hand-off
We agree the order during design, before anything is built, and put a rough date against each piece. The first piece is usually one that:
- hurts enough that the team wants it fixed
- is small enough to switch over without disrupting the week
- doesn’t sit right at the point where cash comes in, so a hiccup costs little
After that, the order follows the way work flows. For a trades firm, a sensible sequence might be enquiries, then quotes, then jobs, then invoicing. For an accountancy practice, it might be client take-on, then document collection, then year-end work. Each piece hands its data to the next, so by the time invoicing switches over, the jobs feeding it are already clean.
Move only the data you need, and check it before you trust it
Moving data is the part people underestimate. Your information is spread across spreadsheets, an old CRM, email folders and Xero, and the copies don’t all agree. We handle it in four steps.
- Decide what comes across. Live customers, open jobs, unpaid invoices and recent history usually do. Ten years of closed jobs can often stay where they are, read-only, with a link from the new system. That’s frequently the cheaper and safer choice.
- Clean it on the way. Duplicate customers merged, addresses tidied, missing details filled in. A new system with the old mess in it feels old on day one.
- Do a trial move and check a sample with you. Does this customer look right? Is this job’s history all there? Do these balances match Xero?
- Do the final move just before switch-over, so nothing is out of date.
Nothing gets deleted from your old tools during the switch. They stay as they are until the new piece has proved itself.
Run old and new side by side, briefly
For the first piece especially, it often helps to run the old way alongside the new one for a short while. The team does the work in the new system, and someone checks the result against the old method. Do the quotes come out at the same price? Do the hours match? Does the invoice in Xero look right?
Keep it short. Doing everything twice is tiring, and if it drags on, the old way starts winning by default. Agree an end date before you begin, and agree what “proved” means: a set number of jobs through without a problem, or a week with no corrections.
Train people on their own work, just before they need it
Training the whole team on every screen a month before go-live doesn’t stick. By the time they need it, they’ve forgotten.
What works is short sessions on the part each person will use, built around their own real jobs, a day or two before that part goes live. The engineer learns how to open a job and log hours on their phone. The office manager learns how quotes are built and approved. Then someone is on hand when they try it for real, and there’s a plain-English guide to come back to.
It also helps to have one person in your team who learns the system more deeply and becomes the first person others ask. They don’t need to be technical, just interested and trusted by the rest of the team.
The first fortnight is for fixing small things quickly
The first two weeks after a piece goes live are when most small problems show up: a field in the wrong place, a reminder that fires too often, a report that needs another column. That’s normal, and it’s why we stay close during that time.
A good first fortnight looks like this:
- Small fixes go in fast, while the team is still forming habits.
- A short check-in every day or two with the person leading it on your side: what’s working, what’s annoying, what’s broken.
- One shared list of issues, so nothing gets lost in email.
- A review at the end of the fortnight to decide whether this piece has settled enough to start the next.
By the end of those two weeks, people should be doing their work in the new system without thinking about it. If they aren’t, we find out why before switching on anything else.
Each piece gets easier, and then we keep running it
Once one piece has settled, the next follows the same pattern, and each switch-over is easier because the team knows what to expect. After the last piece goes live, the work carries on. For a monthly fee we run the system, watch it, fix what breaks and improve it as the business changes.
Our recommendation: agree the switch-over order before you build
Agree the order as part of the design, with a rough date against each piece. It decides what gets built first, gives the team something to plan around, and means you start getting the benefit from the first piece instead of waiting for the whole thing. If you’re still working out what the pieces are, start with how we map a business.
If you’re thinking about moving off a tangle of spreadsheets and old tools and want to know what a sensible order would look like for you, book a review. It’s a free 30-minute call with Mark or me. You can also build your system first and we’ll suggest where to start.