All fully compatible automations have already been migrated to the new automation editor. This article covers what happens to your remaining automations that couldn't be migrated in the first phase.
➡️ Learn more about the new editor:
🔍 What types of automations are being migrated during the second phase?
During the first phase of migration, only fully compatible automations were moved to the new editor. Automations containing one or more unsupported steps or options remained in the classic editor and are now being migrated in a second phase.
Thanks to ongoing improvements to the new editor, these automations now fall into two categories:
-
Fully migratable
Your automation can now be fully moved to the new editor. -
Partially migratable
One or more steps or options in your automation are still not supported in the new editor. These include:- Draft campaign used as a trigger or condition
- Record a conversion action
- Regex-based conditions or filters
- Deprecated segment used as an entry point or filter
- A contact clicks an external link entry point
- Identify event
- SMS tags
- Specific Submit_JS_Event trigger configurations ("more than + string", "contains + number", "equalto + number", "equalto + bool", etc.)
During migration, all automations are moved to the new editor with their original names, while their classic editor versions are deactivated and removed.
✅ What happens to fully migratable automations
Fully migratable automations are moved to the new editor with their original statuses (active, inactive, or paused). If your automation was active, it continues running without interruption.
⚠️ What happens to partially migratable automations
Partially migratable automations are moved to the new editor, but their status is set to inactive after migration, even if they were previously active. A tag is added to automations that were previously active to help you identify them easily on the Workflows page.
When migrated, unsupported steps or options are handled in the following way:
- Unsupported steps appear in the workflow but are marked as inactive. You can reactivate your automation at any time, but unsupported steps will remain inactive and will be skipped. You can delete these steps from your automation or replace them with a different step.
- Steps with unsupported options are marked as incomplete. You will need to take action, such as deleting or replacing the unsupported option, before being able to reactivate your automation.
📋 Common behaviors
Expand the following dropdowns to learn more about how automations behave during migration, whether fully or partially migratable:
If contacts are already active in a classic automation when it is migrated, they continue in the original version until they exit. The original automation is no longer visible on the Workflows page, but its logs and statistics appear in the new automation.
Migrated Send an email steps keep their original emails and settings.
However, if the same email is used in multiple automations, editing its design or settings in one automation will overwrite the settings in all other automations using that email, and all steps will become fully synchronized.
Event logs remain unchanged. Workflow logs display "migrated to [new version]", and the new automation logs reference the original version.
The Workflows page and Activity tab include data from both the original and new versions.
Email and SMS reports only show activity from the new automation, but you can still access historical statistics.
❓FAQs
No. Once migrated, you are not able to create or edit automations in the classic editor.
It depends. Fully migratable automations work exactly as before. For partially migratable automations, unsupported steps are marked as inactive or incomplete and will not run until you take action.
Yes. All logs and statistics are retained.
➡️ To learn more, check our dedicated dropdown under 📋 Common behaviors
They appear on the Workflows page under their original name. Classic editor versions are deactivated. Partially migratable automations that were previously active have a tag so you can identify them easily.
Unsupported steps are visually marked inside the new editor, either as inactive or incomplete.
No. Migration is mandatory to provide a consistent and improved experience.
🤔 Have a question?
If you have a question, feel free to contact our support team by creating a ticket from your account. If you don't have an account yet, you can contact us here.
If you’re looking for help with a project using Brevo, we can match you with the right certified Brevo Agency partner.