# 18-Sep-2026 — Move Brevo — propagate domain, senders, lists and contacts to a new account [ref #392](https://github.com/nbarrett/ngx-ramblers/issues/392)

## [build 958](https://github.com/nbarrett/ngx-ramblers/actions/runs/35666683234) — [commit 736220e](https://github.com/nbarrett/ngx-ramblers/commit/736220ebc1083000546249f0672f13582ed494e1)

_____

### **mail**: Move Brevo ([#392](https://github.com/nbarrett/ngx-ramblers/issues/392))

## What's new

Move Brevo moves an environment's email set-up to a different Brevo account. It recreates the sending domain, committee senders, lists, member contacts and list memberships on the new account, points Mail Settings and notifications at the new list ids, and registers the events webhook there.

## At a glance

- Pick an environment, paste the destination Brevo API key, Validate Plan, then Propagate
- Duplicate list names and do-not-email members are reported up front
- Propagate runs in the background while the page follows it, so a long contact load is not reported as failed because a proxy timed out
- Nothing changes in the environment's own database until every step on the new account has succeeded
- Running it again after a failure is safe

## Where to find it

Admin → Platform → Environment management → Move Brevo. Role addresses and list settings are still edited in Committee Settings and Mail Settings.

## How it behaves

If the sending domain's DNS is not managed through Cloudflare, the run stops and shows the records to add rather than failing part-way. If a member write fails at the end, the exact members already updated are listed, and Mail Settings keep pointing at the old account until a full run completes. On a second run, existing contacts, folders, lists and the webhook are matched by name or address and reused rather than duplicated.