We’re upgrading the automation experience in Brevo! Since September 2025, automations created with the classic automation editor are being gradually migrated to our new automation editor.
The migration is automatic. You do not need to take any action for eligible automations.
➡️ Learn more about the new editor before migration:
📅 Migration plan
The migration is happening in phases, but the process is the same for all users:
- We notify you a few weeks before your automations are migrated.
- After this notice, you cannot create new automations in the classic editor.
- On migration day, all eligible automations are moved to the new editor automatically.
- Automations with unsupported features are migrated later.
🔁 What happens during migration
✅ Eligible automations
- All eligible automations are moved to the new editor with their original names and statuses (active, inactive, paused).
- Classic versions are deactivated.
- Active automations continue running without interruption.
- All contacts, logs, and statistics are preserved.
Emails (migrated Send an email steps)
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 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 in an automation continue in the original version until they finish it. Original automations are no longer visible, but their logs and statistics appear in the new automation.
Logs and statistics
- Event logs remain unchanged.
- Workflow logs show "migrated to [new version]". 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.
⚠️ Automations with unsupported features
Automations using unsupported features remain in the classic editor and will be migrated later.
❓FAQs
After you receive the migration notice, you will not be able to create new automations in the classic editor. Existing automations can still be edited until migrated.
They are migrated along with active automations and keep their original status. Automations with unsupported features remain in the classic editor.
Yes. Only fully compatible automations are migrated, and all steps, logic, conditions, and data work as expected.
Yes. All logs and statistics are retained.
➡️ To learn more, check our dedicated section Logs and statistics.
They appear on the Workflows page under the same name as the original. Classic versions are deactivated. Automations not yet migrated show a "Classic editor" tag.
No. Migration is mandatory to provide a secure, consistent, and improved experience.
💬 Support and communication
We will keep you informed about the migration process through this help article, in-app notifications, and emails.
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.