Table of Contents

How to migrate journeys between accounts

Raquel Updated by Raquel

Migrating journeys between accounts can help streamline your workflow, allowing you to reuse and adapt powerful chat experiences without rebuilding from scratch. This guide will walk you through 2 different methods:

  1. Using Apps to migrate your several journeys effectively.
  2. Using Markdown version to migrate just a few journeys.

Steps to Migrate Several Journeys Using Apps

  1. Export the Journey
    • Access the account with the journey you want to migrate. Make sure you already have Apps enabled. (If that is not the case, please reach out to support)
    • Select the Journeys you want to migrate
    • Click on Actions > Convert to App
    • Give your App a name: for example: Original Journeys, then Create App
    • In the Settings> Apps page > Click on the three dots menu > Export
    • Use the App's export feature to save the journey configuration and assets.
  2. Prepare the Destination Account
    • Log in to the target account.
    • Check for required dependencies (e.g., APIs, templates, profile fields).
  3. Import the Journey
    • Go to Settings > Apps > Install App
    • Upload the exported journey zip file> Install App
  4. Verify and Customize
    • Open the imported journey.
    • Update any account-specific details such as API keys, templates, or triggers.
    • Test the journey flow to ensure it works as expected.

Steps to migrate only a few Journeys using MD version

  1. <> Copy Code the Journey
  • Access the account with the journey you want to migrate. Click on the three dots menu besides the Journey name
  • Click on Copy > Copy Code
  1. On the Destination account
  • Click on New Journey
  • Click on the thre dorts menu > </> Show Code
  • Delete all Default code blocks that appears
  • Click on Markdown file
  • Past the Code version of the Journey > Save the Journey
  1. On the browser: add /canvas at the end of the address.

Tips for Successful Migration

  • Backup the journey and related assets before starting.
  • Document any customizations or integrations in the original journey.
  • Use global data and dictionaries to simplify updates across multiple journeys.
  • Test thoroughly, especially triggers and profile field updates.

If you need help during migration, support is available to assist with specific questions or troubleshooting.

Was this article helpful?

Troubleshooting the Conversion block in turn.io

Test your journeys with the Simulation API

Contact