Skip to content
Ferry
FERRYAI-LED MIGRATION

Migrate to Edesk Knowledge Base by talking to Sakura.

Move articles, media, hierarchy, permissions, redirects, and search metadata. Connect accounts or add files; Sakura inventories, maps, tests, and prepares the transfer in hours, with migration experts reviewing the exceptions.

Start a free assessment→Estimate the timeline

Connectors or files in. A reviewed migration plan out.

Migration briefReady
CUFROMCurrent knowledge base
TOEdesk Knowledge Base
✓ Articles & pages✓ Collections & hierarchy✓ Images & files✓ Authors & permissions
SakuraMigration expert

Move us to Edesk Knowledge Base. Keep the relationships and open work.

I found the objects, dependencies, and three mapping decisions. I drafted the WBS and a pilot run for your review.

Review mappingOpen WBS
1 · Connectors & files2 · AI inventory in hours3 · Expert-reviewed exceptions4 · Approved cutover

WHAT MOVES

Not just rows. The working knowledge base.

Sakura scans the source model first, then builds the mapping, dependencies, tests, and transfer order around what is actually there.
01Articles & pagesInventoried · mapped · validated
02Collections & hierarchyInventoried · mapped · validated
03Images & filesInventoried · mapped · validated
04Authors & permissionsInventoried · mapped · validated
05RedirectsInventoried · mapped · validated
06SEO & search metadataInventoried · mapped · validated

MIGRATION DIRECTORY

Sources we can move into Edesk Knowledge Base

54 platforms in this category. If yours is not listed, connect an API or provide CSV, Excel, JSON, or database extracts for scoping.
IntercomMove to Edesk Knowledge BaseGoogle DocsMove to Edesk Knowledge BaseSharePointMove to Edesk Knowledge BaseSlabMove to Edesk Knowledge BaseConfluenceMove to Edesk Knowledge BaseHubSpotMove to Edesk Knowledge BaseNotionMove to Edesk Knowledge BaseContentfulMove to Edesk Knowledge BaseCodaMove to Edesk Knowledge BaseCannyMove to Edesk Knowledge BaseHelp Scout DocsMove to Edesk Knowledge BaseReadmeMove to Edesk Knowledge BaseZendesk Help CenterMove to Edesk Knowledge BaseWebflowMove to Edesk Knowledge Basemonday.comMove to Edesk Knowledge BaseDiscourseMove to Edesk Knowledge BaseEgainMove to Edesk Knowledge BaseDocument360Move to Edesk Knowledge BaseHelpjuiceMove to Edesk Knowledge BaseIT GlueMove to Edesk Knowledge BaseGuruMove to Edesk Knowledge BaseEgnyteMove to Edesk Knowledge BaseBOXMove to Edesk Knowledge BaseQuipMove to Edesk Knowledge BaseGleanMove to Edesk Knowledge BaseBloomfireMove to Edesk Knowledge BaseStonlyMove to Edesk Knowledge BaseGitbookMove to Edesk Knowledge BaseMintlifyMove to Edesk Knowledge BaseArchbeeMove to Edesk Knowledge BaseFreshdesk Knowledge BaseMove to Edesk Knowledge BaseZoho Desk Knowledge BaseMove to Edesk Knowledge BaseLiveagent Knowledge BaseMove to Edesk Knowledge BaseKustomer Knowledge BaseMove to Edesk Knowledge BaseHappyfox Knowledge BaseMove to Edesk Knowledge BaseGorgias Help CenterMove to Edesk Knowledge BaseGladly AnswersMove to Edesk Knowledge BaseJira Service Management Knowledge BaseMove to Edesk Knowledge BaseHelpshift Knowledge BaseMove to Edesk Knowledge BaseKayako Help CenterMove to Edesk Knowledge BaseGroove Knowledge BaseMove to Edesk Knowledge BaseDeskpro Knowledge BaseMove to Edesk Knowledge BaseTidio Knowledge BaseMove to Edesk Knowledge BaseReamaze Knowledge BaseMove to Edesk Knowledge BaseSalesforce KnowledgeMove to Edesk Knowledge BaseEnchant Knowledge BaseMove to Edesk Knowledge BaseTrengo Help CenterMove to Edesk Knowledge BaseLivechat Knowledge BaseMove to Edesk Knowledge BaseTawkto Knowledge BaseMove to Edesk Knowledge BaseZammad Knowledge BaseMove to Edesk Knowledge BaseDesk365 Knowledge BaseMove to Edesk Knowledge BaseFreshservice Knowledge BaseMove to Edesk Knowledge BaseRichpanel Help CenterMove to Edesk Knowledge Base

MIGRATION TIMELINE

See the work before the migration starts

Change the record volume to see a planning estimate and who owns each step.
<10K50K250K1M5M+
Connect1hYour team
AI inventory & mapping2hSakura
Review & pilot2hTogether
Full transfer3hFerry
Delta & cutover2hTogether

Planning estimate~10 hours

Estimate assumes working connectors and timely review. Attachments, rate limits, and custom logic can extend transfer time.

COMPARE YOUR OPTIONS

AI-led migration changes where the time goes

Ferry gives AI the repetitive discovery and transformation work, while people keep control of business rules, risk, and approval.
CriteriaFerryEngineer-led serviceAutomated toolIn-house
Who runs the migrationSakura + migration expertsDedicated engineersYour team in a wizardYour engineers
Time to first mappingHoursDaysMinutes, if standardDays to weeks
Complex transformationsAI drafts; experts verifyEngineers scriptUsually limitedYou build them
Project workspaceDiagram, WBS, tasks, transfers, chatDocuments and meetingsWizard and logsYour own tools
Pilot and re-runsBuilt into the runProject dependentPlan dependentYou operate them
ValidationAutomated checks + approval gatesEngineer QAMostly self-serveYour QA
Delta cutoverBuilt into the planProject dependentOften an add-onYou build it
After cutoverArtifacts, logs, and workspace remainSupport windowTicket supportYour team owns it

THE MIGRATION PLATFORM

One conversation, with the work visible behind it

Talk to Sakura like a migration expert. She updates the diagram, WBS, task sheet, mapping decisions, transfer runs, and approval queue in the same workspace.
  • System and dependency diagram
  • WBS with owners and decisions
  • Task sheets for exceptions
  • Transfer runs and reconciliation
  • Sakura chat with migration context
FerryOverviewDiagramWBSTasksTransfers
Current knowledge base→Edesk Knowledge Base
01InventoryDone02Mapping reviewReview03Pilot transferReady

I updated the WBS and flagged two decisions before the pilot. Review them?

PRICING

Scoped once. Visible from plan to cutover.

Ferry is quoted per migration based on systems, volume, transformations, pilot cycles, and cutover needs. The migration workspace, Sakura, validation artifacts, and expert review are included in the scope.
PER MIGRATIONFixed-scope quote
  • Migration brief and WBS
  • Pilot and validation
  • Transfer and cutover
  • Expert exception review
Start a free assessment →

FAQ

Questions migration owners ask before they connect anything

What data can Ferry migrate?

Ferry inventories standard and custom knowledge base objects, files, relationships, and relevant configuration. The exact scope is confirmed in the migration brief before anything writes.

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

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

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.

How long does 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. Use the timeline above as a planning estimate, not an SLA.

Will there be downtime?

Ferry is designed for parallel operation, a final delta sync, and a controlled cutover. Whether zero downtime is possible depends on the source and destination APIs and the business process being moved.

Can you 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 if the pilot finds problems?

The issue becomes a task with the affected objects, examples, owner, and decision. The mapping or transform is revised and the pilot can be run again before the full transfer.

How is the migration validated?

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

What happens after cutover?

The workspace keeps the diagram, mapping, WBS, task decisions, transfer logs, validation reports, and approvals. Post-cutover issues can be traced back to the exact rule and run.

How is pricing determined?

Ferry is scoped per migration. The quote considers source and destination systems, record and attachment volume, custom transformations, number of pilot cycles, and cutover requirements. The scope is agreed before the run starts.

Can Ferry move us from Current knowledge base to Edesk Knowledge Base?

If both systems expose APIs, exports, or accessible files, Ferry can inventory the route. We confirm object coverage, write constraints, rate limits, and any manual steps during scoping.

Tell Sakura what you are leaving and where you want to land.

Connectors or files are enough to start the inventory.

Start my assessment →Estimate timeline