Repository navigation
Exchange Mailbox Migration 2.0.0
First public release.
Exchange Mailbox Migration moves the mailboxes of an Exchange Server organisation from source databases to target databases with migration batches — for example to empty DB01…DB09 into new databases — with an HTML and CSV report at every step.
Highlights
- System and user mailboxes kept apart:
-Workload System(arbitration, audit log, discovery: individual move requests, completed automatically) and-Workload User(user, shared, room, equipment, linked, public folder mailboxes and archives: local migration batches, completed when you decide). - Monitoring mailboxes never moved, checked when reading, in the plan and before each submission.
- Plan reviewed before anything happens: target database and batch of every mailbox, balanced batches, primary-only / archive-only / both moves.
- One mode per step:
Inventory,Plan,Start,Status(-Follow),Complete(now or-CompleteAfter),Cleanup;-WhatIfsends every Exchange command with-WhatIf. - Only touches its own objects: never removes a move request or a batch it did not create, nor a batch whose moves are not finished.
- Everything driven by
config\ExchangeMailboxMigration.config.psd1.
Download
ExchangeMailboxMigration-2.0.0.zip contains only the files needed to run (example configuration) and the administrator guide as HTML. Unblock the files after download: Get-ChildItem -Recurse | Unblock-File.
Requirements
Windows PowerShell 5.1 only (Exchange Management Shell, or remote PowerShell to an Exchange server) — PowerShell 7 is not supported by Microsoft for Exchange Server management · Exchange Server 2016 / 2019 / SE · RBAC roles Mail Recipients, Move Mailboxes, Migration, View-Only Configuration.
See CHANGELOG.md for the details.
Package updated on 2026-10-02
Same version, same files, no change to what the tool does: the README and the guide now start with a note to unblock the files downloaded from the Internet (Get-ChildItem "C:\Chemin\Du\Dossier" -Recurse -File -Force | Unblock-File). The Install-Module commands of the guide use -Force, with what to do when an older module version still conflicts.