Per-row results
An import batch records each row and its outcome. A partial failure tells you which rows failed and why instead of leaving you to compare totals.
Migration
Bring your customers with you, row by row.
Migration into Crescove is a batch import with per-row results, run against staging first. Nothing about it requires you to trust that a silent job worked.
How a migration runs
- 01
Inventory
Agree what is moving: customers, contacts, tags, notes, and where applicable properties and equipment.
- 02
Map
Map your columns onto Crescove records and Brand-defined vocabularies such as lead sources.
- 03
Import to staging
Load a batch into staging and read the per-row results before touching anything else.
- 04
Review
Check counts, spot-check records, and fix the source data where rows failed.
- 05
Cut over
Repeat the verified import for the live Brand once you are satisfied, with the operator's approval.
Idempotent where it matters
Repeating a request with the same idempotency key returns the original result rather than creating a second copy.
Staging first
Migrations are rehearsed in staging. We do not run a first import against live customer data.
What we will tell you honestly
Some source systems export data that cannot be mapped cleanly. Where that is true we will say so before the work starts rather than after.
See 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.