D://LEAD52PSA Migration
Move the system
that runs the business.
Migration between professional services automation platforms, covering tickets, projects, time, contracts, and billing, with history preserved and invoicing uninterrupted. It is for services businesses outgrowing their current PSA, or consolidating platforms after an acquisition.
THE PROBLEM
A PSA holds your tickets, your time, and your billing. Migrating it badly means you cannot invoice, which concentrates the mind considerably.
The cost of leaving this alone is rarely one visible failure. It is the slow accumulation: the workaround that became the process, the thing only one person knows, the renewal nobody questioned.
Our starting point is always the same: establish what is actually true today, then decide what to change. Work scoped against an assumption tends to solve a problem you do not have.
- 01Nobody owns itIt sits with whoever touched it last, which is not the same as being managed.
- 02No current pictureWhat you have, what it costs, and who has access are all slightly out of date.
- 03Only handled when it breaksAttention arrives after the disruption rather than before it.
WHAT YOU GET
What the engagement covers
Scoped before it starts, so you know what is included and what is not.
- 01
Data mapping
What moves, what is archived, and what is deliberately left behind. The third category is larger than people expect and deciding it early saves weeks.
- 02
History
Historical tickets, time, and contracts preserved so your reporting continuity survives the move and last year remains comparable to this year.
- 03
Billing continuity
Sequenced around your billing cycle, because a missed invoice run is the expensive failure mode and the one that damages trust internally.
- 04
Training
Staff working confidently in the new system before the old one is switched off, rather than on the morning after.
HOW WE WORK
Discover, design, deliver, embed
Four stages with a written output at each one. You always know which stage you are in and what comes next.
- 01Weeks 1 – 2
Discover
We map how the work happens now, including the workarounds people are slightly embarrassed to mention.
- 02Weeks 3 – 4
Design
Options costed against benefit, so the choice is a decision rather than a preference.
- 03Per stage
Deliver
Built in slices that reach production and get used, each with a success measure agreed before it starts.
- 04Post-delivery
Embed
Training, documentation, and a check-in once the novelty has worn off. Adoption is the only measure that counts.
WHAT CHANGES
What you should expect
- Someone other than you owns it, with that written down.
- The current state is documented and stays documented.
- Cost is planned ahead rather than discovered at renewal.
- Decisions are made against evidence rather than assumption.
FAQ
Questions we get asked
01What is PSA migration?
Migration between professional services automation platforms, covering tickets, projects, time, contracts, and billing, with history preserved and invoicing uninterrupted. It is for services businesses outgrowing their current PSA, or consolidating platforms after an acquisition.
02How do we migrate a PSA without missing an invoice run?
By sequencing the cutover around the billing cycle rather than around a convenient weekend. In practice that usually means completing a full billing run in the old system, migrating immediately afterwards, and keeping the old platform readable for a period. The billing run is the immovable object in this project and everything else is planned around it.
03Should we migrate all our historical data?
Rarely all of it. Open items, active contracts, and enough history for year-on-year reporting are usually worth moving. Ten years of closed tickets generally are not, and migrating them adds cost and risk for something nobody will open. The common answer is to migrate the useful subset and keep the old system readable, or export an archive, for the rest.
04How long does a PSA migration take?
For a small services business, a matter of weeks. For a larger one with complex contracts, integrations, and years of history, several months. Data mapping and cleansing take the bulk of it. The configuration of the new platform is rarely the constraint.
05What usually goes wrong?
Contract and billing configuration that did not carry across cleanly, so the first invoice run is wrong in ways nobody catches until a client does. Time entries that mapped to the wrong project. And staff who were trained a month before go-live and have forgotten. All three are avoidable with a parallel run and a proper verification pass over the first billing cycle.
06How much does PSA migration cost in New Zealand?
We quote after scoping rather than before. Anyone pricing this work without looking at your environment is guessing, and the guess is rarely in your favour. Scoping itself is quick, and we tell you what it costs before we start it.
07How long does it take to get started with PSA migration?
A first conversation takes about half an hour and costs nothing. Scoping is usually a week or two of our time depending on the size of the environment, and we agree the delivery dates with you before anything is booked in.
08Can you deliver PSA migration alongside our existing IT team or provider?
Yes, and it is common. We are happy to work as an extra pair of hands under your internal team, or alongside an incumbent provider on a defined piece of work. We will set out in writing where the responsibilities split, so nothing falls between us.
09Do we have to be an existing Atlas client to start a project?
No. This can be delivered as a standalone piece of work for an organisation we have never worked with before, or folded into a managed agreement if you already have one with us. Plenty of clients use us for one thing and keep everything else where it is.
10Do you deliver projects outside Auckland?
Our team is based in Auckland and we attend sites across the wider region. Most of this work is delivered remotely, so we support organisations throughout New Zealand, and we will say up front where being on site genuinely matters.
11Who from Atlas will be on the engagement?
Named people, not a queue. You get a lead who knows your environment and stays with it, which is the difference between explaining your business once and explaining it every time you make contact.
12What happens when the engagement ends?
You keep the documentation regardless, and anything registered in your name stays in your name. Whether we stay involved is your call. Some clients take it in house from there, others move it onto an ongoing agreement with us. We would rather you left cleanly than stayed because leaving was difficult.
Start with a conversation.
Tell us what you are dealing with and we will tell you whether this is the right service for it, and what it would take.
← All services