Migrations · from $899
Move platforms without losing the database
Dry run, validate, go live, rollback available. The source system stays intact until you sign off on the numbers.
The process
Boring on purpose
Everything moves into a sandbox on the target platform first.
Record counts, field mapping and spot checks, signed off by you.
Scheduled cutover window, usually out of hours.
Source stays available. Reversal is a decision, not a rescue.
Field mapping
Agreed and verified before anything moves
You get the mapping sheet as a document, row by row, including every field we propose to drop. Nothing moves until it's approved.
| Source field | Target field | Transform | Status |
|---|---|---|---|
| Account_Name | company.name | trim + title case | Approved |
| Mobile | contact.phone | E.164 (AE default) | Approved |
| Lead_Source | contact.source | value map (12 values) | Approved |
| Custom_Field_7 | — | dropped, unused since 2021 | Flagged |
Spreadsheet to CRM
Contacts, companies, deals and notes from CSV/XLSX, deduplicated and normalised on the way in.
Merged cells, multi-header sheets, dates as text, and one tab per rep with different columns.
3–5 working days
Zoho to another platform
Leads, contacts, accounts, deals, activities, notes, attachments and owner assignment.
Custom layouts per module, picklist values that don't exist on the target, and workflow-generated tasks that shouldn't come across.
1–2 weeks
HubSpot to another platform
Contacts, companies, deals, pipeline stages, engagements and lifecycle stage history where the target supports it.
Association labels, lifecycle-stage semantics with no equivalent, and marketing email consent that must map to a real suppression state.
1–2 weeks
Salesforce to another platform
Accounts, contacts, leads, opportunities, cases, tasks, events and attachments.
Record types, validation rules blocking inserts, formula and roll-up fields that must be recreated rather than copied, and sharing rules with no counterpart.
2–4 weeks
Odoo to another platform
Partners, contacts, CRM leads, opportunities, activity logs and linked sales records.
Partners doubling as both companies and contacts, multi-company records, and accounting links you probably don't want in a CRM.
2–3 weeks
Stated honestly
What doesn't transfer
Rebuilt on the target platform, never copied. Logic rarely maps one-to-one.
Recreated as target-native fields. Historic computed values are not portable.
Rebuilt. Query semantics differ enough that a copy would mislead.
Stays in the source system. Export it before you decommission.
Re-modelled to the target's permission system with you in the room.
Threads may transfer as activity records, not as sendable email history.
Timeline and pricing
From $899
Scope is set by record volume, module count and how much custom structure exists. A $99 audit first tells us all three, and is credited against the migration.
| Scenario | Records | Typical duration | From |
|---|---|---|---|
| Spreadsheet → CRM | up to 25k | 3–5 days | $899 |
| Platform → platform, standard modules | up to 50k | 1–2 weeks | $1,900 |
| Platform → platform, heavy customisation | up to 100k | 2–4 weeks | $3,800 |
| Above 100k records | quoted | quoted | on volume |
Start with a dry run, not a cutover
Audit first at $99, credited against the migration.