# 18-Nov-2026 — copy from the database a site really uses and keep it on the new cluster after later [#231](https://github.com/Ramblers-GB/ngx-ramblers/issues/231)

## [build 1101](https://github.com/Ramblers-GB/ngx-ramblers/actions/runs/44210594630) — [commit e3d7e19](https://github.com/Ramblers-GB/ngx-ramblers/commit/e3d7e191b31387f68c2267a373dfd82746286457)

_____

## What's new

- Environment Migration now refuses to start when an environment's stored connection string names a different cluster or database from its MongoDB settings, and says which one the site is really using. Correct the MongoDB settings to match the live database first; otherwise the copy would come from an old database and the cutover would put the site onto stale data.
- After a cutover, a later deploy-to-all keeps the site on its new cluster. Previously a stored connection string could put the site back onto the old cluster on the next deploy.