Skip to main content
Most teams do not start from zero. They already have journey work scattered across spreadsheets, workshop notes, customer calls, support threads, and planning docs. Migrating to Custory means choosing the easiest starting source, turning it into one usable journey, and leaving the rest for later.

​
What migration means here

Migration is not a file conversion project. You are not trying to preserve every old artifact exactly as it looked. You are trying to create a journey your team can review, maintain, and use for decisions. You are trying to:
  • keep the useful customer evidence
  • turn scattered context into stages, steps, and items
  • get to a first reviewable journey quickly
The easiest migration is usually one focused customer flow from one strong source.

​
Choose the easiest route

Start with the source that already explains the customer flow most clearly. Do not begin by importing every artifact. Broad imports create broad cleanup.

​
Fast migration path

Use this path when you want the quickest useful result.
  1. Pick one journey, such as trial to paid, new user onboarding, or support escalation.
  2. Choose the one source that explains that journey best.
  3. Create a draft through AI import, AI chat, a template, or a blank journey.
  4. Keep only the stages and steps that describe the real customer flow.
  5. Turn important evidence into items.
  6. Review the journey with the smallest useful group.
If the source is clean and connected, use Import journey with AI. If the source is rough, use AI chat or build the first structure manually.

​
What to move first

Move the parts that make the journey useful:
  • stages that describe broad phases
  • steps that describe customer moments
  • evidence that explains where customers get stuck
  • insights, opportunities, solutions, metrics, or touchpoints that are still relevant
  • links back to source material the team will want to inspect later
Leave behind:
  • duplicate workshop notes
  • old internal labels
  • stale priorities
  • low-confidence assumptions
  • every artifact that does not help the first review

​
Example

Say your onboarding journey currently lives in a spreadsheet with columns like:
  • stage
  • customer step
  • friction
  • evidence
  • owner
Bring that into Custory and ask for one draft: Create a new onboarding journey from this spreadsheet. Use the stage and customer step columns for the map. Turn repeated friction notes into likely insights and opportunities. Then clean the draft before the team uses it:
  1. remove duplicate stages
  2. rewrite internal labels in customer language
  3. keep only current evidence
  4. attach the first metrics or follow-up items
The goal is not “our spreadsheet, but prettier.” The goal is a journey the team can use.

​
What good looks like

A good migration produces:
  • one journey with a clear scope
  • stages that someone can scan in one pass
  • steps written from the customer’s point of view
  • a small number of useful items
  • enough evidence for a team review
  • one obvious next action
If the migration creates a huge map that no one trusts, narrow the journey and remove low-value material.

​
When to use the detailed import guide

Use Import journey with AI when you need the source-specific flow for URLs, repositories, docs, or other import sources. Use this migration page when you are deciding the easiest path and what to move first.

​
Next step

Read Import journey with AI if you have a clean source ready. Then read Your first journey to turn the migrated draft into a map the team can actually use.