Migration
Switching is a data problem and a people problem. We handle both.
Moving off whatever you use today (a legacy platform, a spreadsheet, a mix of both) isn't something we hand you a tool for and wish you luck. Your history comes over, mapped by our team, and your team gets trained on a real curriculum before they're expected to run on it.
What comes over
Six things, named plainly
Not a vague promise to 'import your data': this is the actual list, and each one has a real, working path onto the platform.
Customers
Your customer list, matched and enriched rather than duplicated if a record already exists from another import step.
Work order history
Past jobs, tied to the right customer and site, with their status and dates preserved.
Quotes
Historical quotes with their status (approved, sent, rejected), so pipeline reporting reflects real history from day one, not a blank slate.
Invoices
Invoice totals, balances and pay status come over as they were. Nothing is recalculated after the fact.
Service agreements
Existing maintenance contracts, including the next scheduled visit, so recurring customers don't fall through the gap during the switch.
Items catalog
Your price list, categorized and costed, so the office isn't rebuilding line items from memory in week one.
How it actually works
Managed the same way the rest of the platform is
You send an export from whatever you're using today. Our team maps it and loads it. You're never handed a schema document and an upload button.
A dry run before anything is final
Every migration step can be previewed first (what would be created, what would be matched to an existing record) before a single row is written.
Nothing gets overwritten
If a customer already exists from an earlier step, later steps enrich that record instead of creating a duplicate or silently replacing it.
No guessed numbers
A service agreement that comes over without a clear dollar amount is imported with billing held off, not started at zero. Someone confirms the real number before it ever invoices.
Done by our team, not left to yours
This isn't a self-serve upload button. Because the platform is fully managed, migration is work we do as part of onboarding: you send an export from whatever you're using today, and we handle the mapping.
Training your team
Nobody gets handed a login and a manual
Adopting new software usually fails on the people side, not the data side. This is the part most vendors treat as an afterthought.
A kickoff session for admins
Before anyone touches real data, whoever will administer the system walks through the mental model: how the pieces connect, and where their day-to-day work actually happens.
Role-based, not one-size-fits-all
Admins get the full operational walkthrough: users and permissions, dispatch, billing, reporting. Technicians get exactly what's on their phone, and nothing they don't need.
Printable references, not just a memory of the session
A one-page reference for the office and one for the truck: the answer to a question three weeks in shouldn't require a call to support.
A structured program, not an improvised walkthrough
Training runs from an actual curriculum, organized by module, so every session covers the same ground the same way regardless of who's running it.
Built to adapt to you
You're not rebuilding your process to fit the software
A lot of what makes a switch painful is a rigid tool forcing your shop to work its way. This one is configured around how you already operate.
Permissions your office can actually live with
32 individual permissions, edited from a matrix by you, not a handful of fixed roles someone else decided your business fits into.
Your own instance, configured for your trades
Business units, pricing tiers and your own items catalog are set up around how your shop is actually organized, not a generic template.
Questions we get
Before you ask
The honest answers, including the one about timelines.
How long does switching actually take?
It depends on how much history you're bringing over and how many technicians need training: for a typical shop, the whole process runs anywhere from a few weeks to a couple of months. We'd rather give you a real estimate once we've seen what you're moving than a headline number that doesn't hold up.
What if our current system doesn't export cleanly?
Send what you can export: a spreadsheet, a CSV, whatever your current system produces. Our team does the mapping on our side rather than asking you to reshape your data to fit us first.
Do we have to stop using our old system on day one?
No. There's no hard cutover forced by the migration itself: most shops run a short overlap while the team gets comfortable, then move fully once training is done.
Can we go back and pull something from our old system later?
Once you've moved on, your old system stops being your system of record; we don't maintain an ongoing sync back to it. If you think you'll need read-only access to old records for a while, keep your old login active on the side; that's a decision for you to make with your previous provider, not something this migration handles.
Will our historical invoices and quotes get recalculated?
No. Imported financial records keep the totals they already had. The platform doesn't rewrite history to match how it calculates things going forward.
Who actually does the migration work: us or you?
Us. This is a managed platform, and migration is part of what that means in practice: you're not handed an import tool and a schema document and left to figure it out.
Tell us what you're moving from
Bring a real export and a real headcount and we'll give you a real estimate, not a rounder number that changes once you've signed.