You can move eligible legacy Automation workflows to Automation 2.0 with a one-click migration. Migration creates a new draft in Automation 2.0 and carries over the supported workflow setup so you do not have to rebuild it manually.
The migrated workflow will remain a draft until you Review & Activate to make it live.
Which workflows can be migrated?
Legacy workflows with these statuses can be migrated:
- Active
- Paused
- Inactive
Draft workflows cannot be migrated. If appropriate, you can complete and activate the legacy draft before migrating it, or easily rebuild the workflow directly in Automation 2.0 with written instructions using the new generate from prompt option.
⚠️ Activating a legacy draft may allow contacts to enter it. Review its setup carefully before activating it solely for migration or pause/deactivate right after activation.
Migrate a workflow
- In Keela, open Automation to view your legacy workflows.
- Find the workflow you want to migrate.
- Hover over the workflow row and select Migrate.
- Refer to the Migration status column to track the migration:
- When the migration is complete, the status changes to Migrated.
- If the migration is unsuccessful, the status changes to Can't migrate. Hover over status pill to see why it failed. You can always attempt the migration again after the issue is resolved.
The legacy Automation workflow table showing migration statuses, with the reason for a Can't migrate status displayed.
What happens after a successful migration?
When migration succeeds:
- The workflow is created as a draft in Automation 2.0.
- The original legacy workflow is deactivated so both versions do not run at the same time.
- The Migration status changes to Migrated.
Next:
- Select the button beside Migrated to open the draft in Automation 2.0.
- Review the workflow draft carefully, including its trigger, steps, settings
- Select Review & Activate when you are ready to activate it.
A migrated legacy workflow row showing controls to open the migrated Automation 2.0 draft or migrate again.
What is included in the migration?
A successful migration carries the supported setup from the legacy workflow into the new Automation 2.0 draft, including:
- Workflow steps and their configured selections
- Workflow settings
Review every step before activation to confirm that the draft matches the behavior you expect.
Migrated Legacy workflow emails Update
Legacy Automation emails were created within each workflow. Automation 2.0 uses emails managed in Email Marketing, allowing you to reuse and update them from one place.
When a legacy workflow is successfully migrated:
- Each workflow email is added to Email Marketing as a draft.
- The draft is automatically enabled for automation.
- The email is connected to the corresponding Send Email step in the migrated workflow.
You can later open the email in Email Marketing to update it or reuse it in other Automation 2.0 workflows.
When a workflow cannot be migrated
If migration is unsuccessful, the Migration status column displays Can't migrate. Hover over the status pill to see the reason. You can always re-try the migration if applicable after resolving the issue.
Reasons a workflow may fail to migrate
Below are common reasons a workflow may not migrate and what you can do next.
1. The workflow uses a classic segment
Classic/legacy segments cannot be migrated to Automation 2.0.
What to do:
- Rebuild the segment using Segments V2.
- Update the legacy workflow to use the new segment.
- Return to the workflow list and select Migrate again.
2. The workflow has multiple triggers
Automation 2.0 does not currently support workflows with multiple triggers.
What to do:
- Continue running the workflow in legacy Automation until multiple triggers are supported.
- Or, attempt to rebuild it in Automation 2.0 using the generate from prompt option - you can describe what you want the workflow to do and Automation 2.0 will build the workflow with the appropriate steps where possible. Depending on the workflow, it may be able to create a similar logic.
3. The workflow is a draft
Legacy draft workflows cannot be migrated.
What to do:
- If the workflow is ready to run, activate it and then migrate it.
- Or, rebuild it in Automation 2.0 using the generate from prompt option.
⚠️ Activating a legacy draft may allow contacts to enter it. If you activate it only to make it eligible for migration, review its setup first and pause or deactivate it immediately after activation.
Important things to know
- Active, paused, and inactive legacy workflows can be migrated. Draft workflows cannot.
- Migration creates an Automation 2.0 draft; it does not activate the new workflow.
- A successful migration deactivates the original legacy workflow.
- Migrated emails become Email Marketing drafts enabled for automation.
- Review the migrated draft before selecting Review & Activate.
If migration still fails after you resolve the flagged issue and try again, contact Keela Support.