Customer migration
How we moved 900+ companies to a new platform without a single missed filing
Segmenting clients, checking readiness before every move, keeping a way back and planning for the problems we hadn't found yet.
Written by
Bianca Lomeli
Technical Program Manager
Some deadlines can move. Regulatory filing deadlines can't.
When listed companies in the EU file their annual reports, they have to do it in a machine-readable format, on time, every time. If the software they use fails at the wrong moment, it isn't a late feature. It's a company missing a legal filing.
That was the backdrop when ParsePort, the regulatory reporting company I worked for, built a brand-new platform from the ground up. The new platform, V4, was better in almost every way. But better software is worth nothing if you can't get your customers onto it safely. And we had to move all of them: our entire client base, 900+ companies across Europe, auditors included, each with its own filing deadline.
I was responsible for defining how we'd do it. Here's what I learned.
A switch-over succeeds or fails before it happens
Earlier in my career, I'd seen a system switch-over go wrong. Everyone was ready on paper, but it hadn't been tested against real use, and within months the business rolled back. That stuck with me. By the time you flip the switch, the outcome is already decided by the preparation you did or didn't do.
So most of the work on this migration happened before a single client moved.
Not every client is the same, so don't move them the same way
The first thing I did was segment the client base. Some clients could move early with little risk. Others needed more care, because of how they used the platform or how close they were to a deadline.
Moving the straightforward clients first gave us confidence and early lessons. By the time we reached the clients who needed the most care, we'd already worked out the rough edges.
Check readiness before every move
Professional Services carried out the migrations, and I coordinated the work with them. Before clients moved, the team tested V4 for them. It's a simple rule, but it's the difference between finding a problem yourself and having a customer find it during filing season.
Keep a way back
The legacy platform stayed open as a fallback. That decision cost us something: running two platforms is more work than running one. But it meant no client was ever stuck. If something went wrong on V4, they still had a way to file.
The best fallback is one you never need. You keep it anyway, because in regulated work the cost of being wrong is too high.
Plan for the problems you haven't found yet
After each move, we reserved time to fix major issues before moving on. In other words, hypercare. It meant the team wasn't scrambling to fix the last group's problems while moving the next one, and that clients who'd just moved got fast help if they needed it.
Professional Services also checked in with clients after they moved, and I checked in with the team throughout. A migration isn't done when the last account switches over. It's done when the customer is confident working in the new system.
The result
Every client on the legacy platform, more than 900 companies including auditors, moved to V4 before their filing deadlines, with zero filing issues. That cleared the way to retire the old platform.
What I'd tell anyone running a high-stakes migration
Decide the outcome in the preparation. Test against real use, not just the plan.
Segment, then sequence. Move the easy cases first and learn from them.
Check readiness every time, even when it feels repetitive.
Keep a way back until you're sure you won't need it.
Budget time for the problems you haven't found yet.
Finish with the customer, not with the cutover.
The same principles apply well beyond regulatory reporting. Any time the people depending on your system can't afford for it to fail, the work that matters most happens before anyone notices anything changed.