Connect · Inventory · Map · Validate · Parallel-run · Cutover

Move systems without losing the business.

Ferry is the migration platform for CRM, ERP, and legacy systems — every crossing validated, parallel-run, and signed off before cutover. Run it with the Sanka team.

The crossing, in six stages

Every stage leaves a reviewable artifact. Nothing cuts over until the numbers match and someone signs off.

1ConnectSource connected, credentials verified.
2InventoryObjects, fields, record counts, automations — one inventory report.
3MapField & object mapping with type checks; reusable templates.
4ValidateDry-run report: rejects, coercions, duplicates — before anything writes.
5Parallel-runSource vs. new system diffed on counts and aggregates until they match.
6CutoverFreeze, delta sync, final diff, sign-off — with the audit trail kept.

Routes we sail today

These migrations run today as Sanka services; Ferry productizes them.

Operator-first, by design

Ferry v1 is run with the Sanka team: we drive the stages inside your workspace, you review every artifact and approve every step. Self-serve comes later — certainty comes first.

Frequently asked questions

How long does a migration take?

Inventory and a validated mapping typically land within the first week; full crossings run days to weeks depending on volume — never quarters.

What happens to open transactions?

Open work is part of the inventory; the cutover stage freezes, delta-syncs, and reconciles it before sign-off.

Can we keep both systems running for a while?

Yes — the parallel-run stage exists precisely for that: both systems live, diffed on counts and aggregates until you trust the new one.

What does it cost?

Scoped per migration today — tell us the source system and rough volumes and we'll quote the crossing.

Tell us what you're leaving behind.