FERRY

Connect · Scan · Map · Test · Transfer · Cutover

Move data from any system. Tell Sakura where it should go.

Connect accounts or add files. Sakura inventories, maps, tests, and prepares the transfer in hours — with Sanka migration experts reviewing the exceptions.

Start a free assessment Explore migration routes

Run with the Sanka team · quoted per migration

What Ferry can moveAI inventory ready

FROMSalesforceZendeskNetSuiteCSV / Excel

TOHubSpotZoho DeskSankaAny API

SakuraI found 42 objects, drafted the mapping and WBS, and flagged three decisions before the pilot.

✓ Diagram✓ WBS✓ Tasks✓ Transfers✓ Approvals

Trusted by 1,000+ companies

6stages — every one leaves an artifact and waits for sign-off

0writes to the new system before validation passes

2systems run in parallel, diffed until the numbers match

MIGRATION PLATFORM

The migration platform, in six stages

After onboarding, Sakura guides every step inside your migration workspace — preparing the artifacts, surfacing decisions, and asking for approval before cutover.

Native integrations to source and target — credentials verified.

Objects, properties, reports, and workflows — one scan report.

Field & object mapping with type checks; reusable templates.

Dry-run report: rejects, coercions, duplicates — before anything writes.

Data moves in dependency order, counts reconciled as they land.

Freeze, delta sync, final diff, sign-off — with the audit trail kept.

Your migration workspaceLive after onboarding

ferry.sanka.com

Ferry

NotificationSupport

Mayu KawasakiSanka Inc.

RunsSourcesTemplatesReports

Salesforce (production) SankaParallel-run182,410 records · 42 objects · 0 rejects

ConnectScanMapTestTransferCutover

ObjectSourceSankaStatus

Accounts48,21048,210Match

Contacts96,54096,540Match

Deals (amount)¥1,284.5M¥1,284.5MMatch

Products3,1203,118Review

Invoices23,08823,088Match

Line items452,921452,921Match

Quotes12,90512,905Match

Payments18,20418,204Match

Attachments74,51274,512Match

Request cutover sign-offFreeze window: Jul 6, 22:00–24:00

SakuraAccess verified

I’ll verify each connector and file before scanning anything.

✓Source connected
✓Target connected
✓Permissions checked

I’ll ask before anything irreversible.Start inventory

MIGRATIONS

Routes we sail today

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

Help Desk MigrationsPreserve tickets, conversations, attachments, SLAs, and customer history.ERP MigrationsMove ERP masters, transactions, approvals, and open work safely.CRM MigrationsMigrate CRM data, relationships, and workflows with validation.Accounting MigrationsMove accounts, partners, journals, invoices, payments, and balances.Ecommerce MigrationsMigrate products, customers, orders, inventory, and fulfillment context.HRIS MigrationsMigrate employee history, documents, leave, compensation, and teams.ATS MigrationsPreserve candidates, applications, interviews, scorecards, and offers.Knowledge Base MigrationsMove articles, hierarchy, media, permissions, redirects, and metadata.ITSM MigrationsMove incidents, assets, catalogs, SLAs, approvals, and audit history.Financial CRM MigrationsMove client, household, relationship, compliance, and portfolio context.

CASE STUDIES

Crossings we've already made

A few of the migrations the Sanka team has run — company names withheld.

SMB · B2B energy

Complex workflows, setup, and a Salesforce exit — done in 1.5 months.

Challenge: Salesforce was too complex to master; forms and partner-sales processes lived in people's heads.
Sanka ran: Built the contact / company / deal management process, the sales playbook, and reporting.
Outcome: Off Salesforce in 1.5 months — a leaner sales system running in weeks.

Public company · Real estate

Forms and CRM moved off Salesforce Account Engagement in under two months.

Challenge: Account Engagement (Pardot) and Sales Cloud had to be migrated within two months.
Sanka ran: Form rebuild from Pardot to HubSpot, automated hand-off into HubSpot tickets, sales setup.
Outcome: Migration done with cost and time held to a minimum — accounts fully set up within two months.

Mid-market · Construction

An underused Salesforce swapped for HubSpot — SFA, forecasting, CRM live in 1.4 months.

Challenge: Salesforce went underused, and the cost wasn't paying back.
Sanka ran: Salesforce-to-HubSpot migration support; Sales Hub, reports, and workflows built out.
Outcome: Beat the two-month plan — every process live and the team operating in 1.4 months.

Enterprise group · EC + wholesale

Orders, customers, and billing unified into one sales-management system.

Challenge: Direct EC, marketplaces, and field sales needed one MA/CRM/SFA across every channel.
Sanka ran: A custom pipeline unifying order data across B2B, EC, and delivery channels.
Outcome: Sales management and sales work rebuilt on one product/order master — annual revenue up 50%+.

OPERATING MODEL

You connect. Sakura runs. Experts review.

The migration experience is one conversation with Sakura; the diagram, WBS, tasks, transfers, validation, and approvals stay visible behind it.

01Connect accounts or filesProvide the source and destination connectors. CSV, Excel, JSON, and database extracts can be added when an API is not available.

02Talk to SakuraDescribe the outcome and answer business-rule questions. Sakura updates the diagram, WBS, tasks, mapping, tests, and transfer runs.

Human review03Experts review the exceptionsSanka migration experts review high-risk transformations, pilot results, and the cutover plan. Nothing moves past a gate without approval.

FAQ

Frequently asked questions

What can Ferry migrate?

Ferry covers help desks, CRM, ERP, accounting, ecommerce, HRIS, ATS, knowledge bases, ITSM, and financial-services CRM. It inventories standard and custom objects, files, relationships, and relevant configuration before scope is approved.

How is Ferry different from an engineer-led migration service?

Ferry is AI-led. Sakura drafts the inventory, mapping, WBS, tests, and exception queue inside one migration workspace. Experts review high-risk decisions instead of rebuilding every step manually.

How long does a migration take?

AI inventory and a first mapping can be ready in hours. End-to-end time depends on data volume, API limits, attachments, custom logic, and how quickly the pilot is approved.

How much of our team's time will it take?

Your team connects accounts or supplies files, answers business-rule questions, reviews the pilot, and approves cutover. Sakura and the Sanka team handle the migration work between those gates.

Can Ferry handle custom fields and relationships?

Yes. Sakura proposes transformations and relationship rules, runs them against a pilot set, and surfaces ambiguous or lossy mappings for human approval.

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 — during Transfer both systems stay 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.

How is the migration validated?

Ferry compares record counts, required fields, relationship integrity, transformed values, rejects, duplicates, and selected business totals. Results stay in the workspace as reviewable artifacts with sign-off gates.

What happens after cutover?

The diagram, mapping, WBS, task decisions, transfer logs, validation reports, and approvals remain in the migration workspace, so issues can be traced to the exact rule and run.

Tell us what you're leaving behind.

Start my assessment See pricing

Tell us the source system and rough volumes — we'll quote the crossing.