Search

Migration to the new automation editor: what Enterprise customers need to know

đź’ˇ Good to know
If you're on a Free, Starter, Standard, or Professional plan, check our dedicated article Migration to the new automation editor: what happens to automations that haven't been migrated yet instead.

Brevo is moving automations from the classic automation editor to the new automation editor, a more flexible and reliable way to build your workflows. 

➡️ Learn more about the new editor:

đź“… Migration plan

Starting August 24, 2026, we're gradually migrating Enterprise customers to the new automation editor. You'll receive an email and in-app notification a few weeks before your automations are migrated. Once your migration begins, it can take up to 7 to 10 days for all your migratable automations to move over.

During this time:

  • Migratable automations, meaning those for which all steps and options are available in the new editor, move automatically. You don't need to take any action.
  • Automations that aren't migratable yet, meaning those with at least one unsupported step or option, stay in the classic editor and keep running as they are.
❗️ Important
After the notice, you can no longer create new automations in the classic editor, but you can still update your existing ones.

âś… Migratable automations

Here's what happens to migratable automations:

  • They move to the new editor with their original name and status (active, inactive, or paused).
  • If they were active, they continue running without interruption.
  • Their classic version becomes read-only. You can still view it to compare with the new version, but you can no longer edit it.
  • All contacts, logs, and statistics are preserved.

Expand the following dropdowns to learn more:

Send an email step

Migrated Send an email steps keep their original settings, including tags, subject line, preview text, send time, and reply-to address.

Templates keep the same ID after migration, so your existing statistics stay accurate.

However, if the same email is used in multiple automations, editing its design or any setting in one automation overwrites all settings in the other automations, and all steps become fully synchronized.

➡️ For example
In the classic editor, the same email might be used in Automation A and Automation B with different sending times. After migration, the email is reused in both automations, and each Send an email step initially retains its original sending time. However, if you edit the email's design or any setting in Automation A, all settings, including the sending time, are overwritten in Automation B.
Contacts already in an automation

Contacts already in an automation continue in the classic version until they exit it. 

❗️ Important
If you update the new automation, contacts still in the classic version are not affected. They continue through the steps of the classic version until they exit.
Logs and statistics
  • Event logs remain unchanged.
  • Workflow logs show "migrated to [new version]". The new automation logs reference the classic version.
  • The Workflows page and Activity tab include data from both the classic and new versions.
  • Email and SMS reports only show activity from the new automation, but you can still access historical statistics.
Exit criteria and re-entry settings

Exit criteria for your automation are migrated as well. If contacts were allowed to re-enter an automation, this setting is preserved too.

Custom event triggers

Triggers based on custom events are preserved in the new editor.

⚠️ Automations that aren't migratable yet

These automations stay in the classic editor and keep running exactly as they are. Nothing is deactivated.

Unsupported steps and options for this migration include:

  • Draft campaign used as a trigger or condition
  • Regex-based conditions or filters
  • Deprecated segments 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.)

âť“FAQs

Will my automations stop working during migration?

No. Migratable automations keep running without interruption. Automations with unsupported steps or options keep running unchanged in the classic editor.

Where can I find a list of which of my automations are migratable?

We share a detailed list of your migratable and non-migratable automations after this migration is complete.

Can I opt out of the migration?

No. Migration is mandatory to provide a secure, consistent, and improved experience.

đź’¬ Support and communication

We keep you informed through this help article, in-app notifications, and emails.

If you have any questions or concerns, feel free to contact your dedicated Customer Success Manager for more information.

🤔 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.

đź’¬ Was this article helpful?

0 out of 0 found this helpful