Migrating to Custory

Most teams do not start from zero. They already have journey work scattered across spreadsheets, notes, workshop docs, support summaries, and product sources. Migrating to Custory means choosing the best of that material, turning it into one working journey, and dropping the rest.

​

What migration means here

You are not trying to preserve every old artifact exactly as it is. You are trying to:

• keep the useful customer evidence
• turn it into a journey the team can maintain
• get to a first reviewable map quickly

That usually means one focused source at a time, not a giant import of everything the team has ever collected.

​

What you can migrate from

Useful source material can include:

• a CSV or spreadsheet
• a Notion page
• a workshop document
• a whiteboard export
• a website or help center page
• a GitHub repository
• a Figma file, when Figma import is available
• pasted notes from interviews, support, or onboarding calls

​

When to use this path

This page is for you when:

• the team already mapped part of the journey somewhere else
• research notes already explain the flow well enough to draft from
• onboarding or activation material is spread across several tools
• you want AI to draft the structure before the team refines it

​

The usual migration path

For most teams, migration looks like this:

1. choose the narrowest source that explains one journey well
2. bring that source into Custory through AI import or AI chat
3. ask Custory to draft the structure
4. clean up stages and step names
5. attach the first real items so the draft becomes useful

The narrow source matters. One strong spreadsheet or one focused doc usually produces a better result than several mixed sources dumped together.

​

How to choose the source

Bring in the source that already tells the customer story most clearly. Good examples:

• a CSV of onboarding steps and friction notes
• one Notion page with a workshop draft
• one public docs page that explains setup
• one repo when the real flow is easiest to infer from the product
• pasted interview or support notes when that detail is not stored anywhere else

If you use AI chat instead of a direct import path, add clear framing. Do not paste content and hope the model guesses the scope correctly. Better prompt: Create a trial-to-paid journey for first-time workspace owners. Use this CSV and these notes to draft stages, steps, and likely friction points.

​

Example

Say your onboarding journey currently lives in a spreadsheet with columns like:

• stage
• customer step
• friction
• evidence
• owner

You can bring that CSV into Custory, ask AI to draft the journey, then:

1. keep the stages that match the real flow
2. rewrite vague step names in customer language
3. turn repeated friction notes into insights and opportunities
4. add the first metrics that will tell you whether things are improving

The goal is not “our spreadsheet, but prettier.” The goal is a journey the team can review and keep current.

​

What to clean up first

After the draft appears, fix these before wider team review:

• vague stage names
• internal shorthand in step names
• duplicate or off-scope sections
• missing evidence links
• missing item relationships

That cleanup pass is where the draft becomes a useful journey instead of an import artifact.

​

Common migration mistakes

​

Next step

Read Import journey with AI for the direct import flow. Then read Your first journey to turn the imported draft into a map the team can actually use.