How MigrationWiz Licensing Works

Each MigrationWiz license covers a specific data threshold. When a migration job exceeds that threshold, an additional license is consumed automatically. Because the same job can run multiple times with different settings, licenses can accumulate faster than expected if the migration isn’t scoped carefully from the start.

Questions to Ask Before Running Any Pass

Are you running full migrations when a delta sync would capture everything that’s changed? Have you filtered out data you don’t need to migrate before the pass runs? Are you migrating duplicate or redundant items that could be consolidated? Have you reviewed which data actually requires migration versus which data is being migrated out of habit?

Answering these before the first pass runs costs nothing. Answering them after licenses have been consumed costs real money.

Strategies to Reduce License Consumption

Filter before migrating. Before any pass runs, exclude old email, trash folders, and outdated file versions. Data that doesn’t need to move shouldn’t move.

Use delta syncs strategically. Pre-stage migration passes do not consume additional licenses. Run pre-stages to move the bulk of data before the cutover window opens, then use the final pass only for changes that occurred after the pre-stage completed.

Scope the migration accurately. If users only need recent email, don’t migrate the entire mailbox. Migrate what’s relevant and document the exclusions so the decision is on record.

Monitor license consumption during the project. The BitTitan License Consumption Dashboard shows how many licenses each job is using in real time. Check it during the migration, not after it finishes.

Sequence migration waves logically. Group users by department, workload size, or dependency relationship. A well-structured wave plan reduces the number of passes needed and keeps license consumption predictable.

#Migration #CloudMigration #Azure #M365Migration #EmailMigration