Per-row results
Import batches record every row and its outcome, so a partial failure names the rows and reasons instead of leaving you to compare totals.
Migration
Move in stages, and verify each one.
Migration is a batch import with per-row results, rehearsed in staging before anything touches live data. We would rather tell you what will not map cleanly before the work than after.
How a migration runs
- 01
Inventory
Agree what moves: customers, contacts, properties, equipment, price book, open work, history.
- 02
Map
Map your columns onto Crescove records and your own vocabularies for lead sources and lost reasons.
- 03
Price book first
Load the catalogue before the work, so imported jobs and estimates reference real services.
- 04
Import to staging
Load batches into staging and read the per-row results.
- 05
Verify
Check counts, spot-check records, exercise a full job end to end in staging.
- 06
Cut over
Repeat the verified import for the live Brand, with the operator's approval.
Open work needs a decision
Jobs in flight during a cutover need an explicit plan — finish them in the old system, or import them mid-state. We will make that choice with you rather than for you.
History has limits
Some systems export history that cannot be mapped faithfully. Where that is true we will say so, rather than importing something that looks complete and is not.
No live migration without approval
A first import never runs against live customer data, and a production cutover is an explicit operator decision.
See Field Service & CRM against your own workflow.
Tell us how your business runs today and we will walk through what is available now, what is still being built, and what would need to be connected for you.