> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usecustory.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Nested journeys

> Break a broad macrojourney into smaller microjourneys without losing the connection between high-level flow and detailed work.

Sometimes one step grows large enough that it stops behaving like a step and starts behaving like its own journey. Nested journeys let you split that work out without losing the connection to the parent flow.

## What nested journeys are for

Use a nested journey when one part of the broader map needs its own structure, evidence, and follow-through.

Example:

* parent journey: `Self-serve onboarding`
* nested journey: `Connect Slack`
* nested journey: `Invite teammate`
* nested journey: `First value setup`

The parent journey stays useful for coordination. The child journey holds the deeper detail.

## When to create one

Create a nested journey when a single step needs:

* more stages and steps
* its own evidence and items
* its own prioritization work
* its own owners or review rhythm

Do not split a step out just because it feels important. Split it when keeping all that detail in the main journey would make the parent map harder to use.

## Where it lives

Nested journeys are managed in the **Nested journeys** lane inside **Journey view**.

If that lane is hidden, add it back from the lane picker.

The lane keeps the relationship visible without mixing all of the child-journey detail directly into the parent map.

## Create or link a nested journey

In **Journey view**:

1. find the step that needs its own deeper flow
2. open or reveal the **Nested journeys** lane
3. hover that step
4. choose **Create new journey** or **Add existing journey**

Use **Create new journey** when the detailed flow does not exist yet.

Use **Add existing journey** when the detailed flow already exists in the same workspace.

Custory filters out options that would create a circular parent-child relationship, so the hierarchy stays readable.

## What the card shows

Each nested journey appears as a card in the step cell.

The card gives you a quick summary, including:

* journey name
* stage count
* step count
* item count

That is usually enough to tell whether the child journey is still lightweight or has become substantial work on its own.

## Open, move, and reorganize

Click the card to open the linked journey directly.

Nested journey cards can also be repositioned inside the lane when:

* the step should point to a different child journey
* the linked flow belongs under a different part of the parent journey
* the sequence should better match the real customer motion

## Good use cases

Nested journeys are especially useful for:

* onboarding flows with one complex activation step
* billing or checkout flows with several important sub-flows
* support escalation paths with clear branch journeys
* expansion or renewal work that needs a deeper map than the main journey

## A good team pattern

For most teams, the right order is:

1. map the broad journey first
2. notice where the team repeatedly needs more detail
3. split only those steps into nested journeys
4. keep the parent journey focused on coordination
5. keep the child journey focused on deeper diagnosis and action

This prevents the parent map from turning into one giant surface that nobody wants to review.

## When not to use nested journeys

Keep the work in the parent journey when:

* a few more items would solve the problem
* the step is important but not complex
* nobody will maintain the child journey separately

If the child journey will not be reviewed on its own, it may just add structure without adding clarity.

## Nested-journey mistakes to avoid

<AccordionGroup>
  <Accordion title="Splitting too early">
    Start broad. Split only when more detail is clearly helping the team understand or review the work.
  </Accordion>

  <Accordion title="Creating a child journey with no clear owner">
    If nobody will review it, it becomes dead weight instead of a useful map.
  </Accordion>

  <Accordion title="Using nested journeys as folders">
    They should earn their place by improving clarity, not by adding structure for its own sake.
  </Accordion>
</AccordionGroup>

## Next step

Read [Journeys](/journeys) for the broader parent-map model. If the child flow needs a faster starting point, read [Journey templates](/journey-templates).