Migrating to Journey Frameworks

Every week, we improve TheyDo. Most of the time that means adding features and enhancing what’s already there. Sometimes it also means saying goodbye to something we built earlier.

A few years ago, we introduced Frameworks to help you organize your complete customer experience using Boards. It gave you a visual way to show which Journeys belonged together. Over time, we learned that the structure also created limitations.

Meanwhile, Journeys became much more powerful. You can now add metrics, insights, opportunities, images, and nest journeys inside other journeys. The original purpose of Frameworks is now fully supported directly within Journeys.

So it’s time to simplify.

Journey Hierarchies will be sunset on May 1, 2026.

  • Starting March 17, 2026, you won’t be able to create new hierarchies.

  • On April 14, 2026, we will automatically migrate your existing hierarchies and boards to Framework Journeys with nested journeys. All content will be preserved.

We’re moving to a simpler structure, powered entirely by Journeys.

Why the naming is changing

You may currently see two sections in your App Menu:

  • Journey Hierarchies

  • Journey Frameworks

Previously, “Journey Hierarchies” was the heading where you added Frameworks.
Each Framework contained Boards, and each Board contained Journeys.

This created an extra structural layer that is no longer needed.

Going forward:

  • You will add a Journey directly under Journey Frameworks

  • That Journey becomes your Framework

  • Nested journeys replace Boards

Everything becomes a Journey.

This simplifies your structure and makes it easier to manage and scale.

Moving from Journey Hierarchies → Journey Frameworks

We do need your help to move from hierarchies to Journey frameworks, but we believe that you’ll love it.

It involves just 5 steps:

  1. Create your Framework Journey

  2. Name the phases in the Journey according to your boards in your framework

  3. Name the steps in the Journey according to the stages in your boards

  4. Add the nested Journeys that live in each board into a nested Journeys lane in your new Framework Journey

  5. Add the Framework Journey to the App Menu and delete the old Framework

Create your Journey Framework

You’ll create a new Journey that functions as the Framework you have already set up. Here you see how I create a new Journey with the same name as the Framework that I want to move.

I choose the ‘Lifecycle Journey’ template because it automatically adds a summary lane and is designed for this level of Journey. You can, of course, use any template that suits your needs!

Immediately you see how we now can utilize the extra capabilities that a Journey brings even on this level. Like Metrics, but also Key Opportunities, Insights, Solutions and even images.

Name the phases in the journey

In the Journey you just created edit the phases to correspond to the boards that were in your Framework. In this case:

  1. Discovery

  2. Onboarding

  3. Habit building

  4. Mastery

Delete phases you don’t need.

Name the steps according to the stages in your boards

Now that each board is a phase, the stages become steps.

In some cases this might result in a very long Journey (e.g. when you have a lot of stages in each board). You could solve for that by e.g. creating a Journey ‘above’ the highest level that summarizes that Journey.

In the nested Journeys lane you can now add the Journeys you had in your boards.

If you have multiple lanes in your boards you can also add additional lanes in your Journey. The only thing that is not possible is to have different lanes per board (although if you’d want to you could create a Framework Journey that captures your boards as separate Journeys, essentially adding another level in between).

Add the Journey Framework to the app menu

If you’re a workspace admin, you can add the Journey through its menu or search for it after pressing the + button next to the "Journey frameworks" heading. The Framework Journey will then be visible to everyone in your workspace, serving as an entry point for understanding your experience.

If you’re not a workspace admin, ask your admin to do this for everyone!

Finally, you can go back to the Framework under the ‘Journey Hierarchies’ you just migrated, and delete it. Remember to check ‘also delete boards’ to remove them as well.

Continue reading: