We’re upgrading the automation experience in Brevo! Starting in September 2025, automations created with the classic automation editor will be gradually migrated to our new automation editor.
This migration is fully automated and transparent, requiring no manual action for eligible automations.
➡️ If you'd like to learn more about the new editor before the migration occurs, check our dedicated articles About the new automation editor and Differences between the new and classic automation editors.
📅 What’s planned for the migration
Although the migration will happen in phases for different user groups, the steps remain the same for everyone:
| Step | Description |
|---|---|
| 1 | We’ll notify you a few weeks before the migration of your eligible automations begins. |
| 2 | A few weeks after this initial communication, you’ll no longer be able to create new automations in the classic editor. |
| 3 | On migration day, all eligible automations (both active and inactive) will be automatically migrated to the new editor. |
| 4 | Automations that use unsupported features will be handled separately and migrated later. |
🔁 What happens during the migration?
✅ If your automations are eligible for migration
On migration day, here’s what you can expect:
Automations
- All automations created in the classic editor are automatically migrated and activated in the new editor. They keep their original names.
- The classic versions are deactivated and no longer visible.
- Automations keep running without interruption, and all contacts, logs, and statistics are preserved.
Emails (migrated Send an email steps)
All Send an email steps migrated to the new editor continue to use the same emails and retain their original settings from the classic editor.
However, if the same email is used in multiple automations, editing its design or any setting in one automation will overwrite all settings in the other automations, and all steps will become fully synchronized.
Contacts currently in the automations
Contacts already progressing through an automation remain in the original version until they exit it.
That original version is no longer visible, but its logs and statistics appear in the new automation, and those contacts are included in the new statistics.
Logs
- Event logs: unchanged.
-
Workflow logs / Contacts in workflow:
- The original automation shows "migrated to [name of new version]".
- The logs of the new automation reference the original version.
Statistics
- Workflows page: Includes data from both the original and the new versions.
-
Activity tab (new automation):
- Also includes data from both versions.
- Only activity from the new automation appears in the email and SMS reports, but you can still access previous statistics collected before migration through a link.
⚠️ If your automations use unsupported features
Most automations can be migrated. However, if an automation includes a feature not yet supported in the new editor:
- It remains active and editable in the classic editor.
- It will be migrated later, once the missing features are added.
❓FAQs
No. A few weeks after the first communication about the migration, you’ll no longer be able to create new automations in the classic editor.
However, editing existing automations will still be possible until they are migrated.
If they are eligible, inactive automations will be migrated along with active ones.
If they contain unsupported features, they’ll remain available in the classic editor and be migrated later.
It will not be migrated immediately. It will remain fully functional in the classic editor and be migrated once those features become available in the new editor.
Yes. Only automations that are 100% compatible with the new editor are migrated. All steps, logic, conditions, and data will function as expected.
Yes. All your historical data will be retained.
➡️ To learn more, check our dedicated sections for Logs and Statistics.
You’ll find them on the Workflows page, under the same name as the original.
Yes. The classic version will be will be deactivated and will not be visible anymore on your account. The new version will replace it. A success message will confirm the migration.
Automations not yet migrated will remain visible with a "Classic editor" tag.
No. Migration is mandatory to ensure a secure, consistent, and improved automation experience for all users.
💬 Communications and support
We’ll keep you informed every step of the way through this help article, in-app notifications, and emails before each milestone.
If you have any questions or concerns, feel free to contact our support team by creating a ticket from your account.
🤔 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.