What it works with
Module: Local PowerShell
Context: Windows PowerShell 5.1 or PowerShell 7 · local CSV transformation
Compatibility: Pure local PowerShell; Windows PowerShell 5.1 and PowerShell 7 are supported.
POWERSHELL / MIGRATION
ProIntermediateRead-onlyLow
Build MigrationWiz Bulk Add mapping CSV
Validates an Opselith migration identity dataset and builds a MigrationWiz Bulk Add CSV containing only the documented Source Email and Destination Email columns, plus a separate validation report.
Pro generation after license validation · Review before running · No tenant access by Opselith
What this PowerShell script does
Validates an Opselith migration identity dataset and builds a MigrationWiz Bulk Add CSV containing only the documented Source Email and Destination Email columns, plus a separate validation report.
Requirements
- Opselith identity dataset CSV - Use the CSV produced by #121 or a compatible dataset containing PrimarySmtpAddress and UPN columns.
- Destination domain - Destination SMTP domain, for example target.example. Do not include @.
- Source address basis - Choose which normalized #121 source column becomes Source Email.
- MigrationWiz Bulk Add CSV path - Output contains exactly Source Email and Destination Email.
- Validation report CSV path - Separate row-level validation report. Use a different path from the Bulk Add CSV.
Environment
- Module: Local PowerShell
- Runtime: 5.1 / 7
- Permissions: No tenant or MigrationWiz permission required for local CSV preparation.
- Risk: Low
Review before you runReconfirm the destination domain and mapping basis. Review the validation CSV before importing the Bulk Add file into MigrationWiz.
OPS / WORKSPACE
Ready to generate
Configure Build MigrationWiz Bulk Add mapping CSV in the Builder, review the generated PowerShell and run it in your own environment.
When to use this template
Use this after reviewing a normalized identity dataset when you need a validated Bulk Add mapping file for MigrationWiz.
Important limitations
- The default output uses only Source Email and Destination Email because current BitTitan documentation identifies those as the required Bulk Add columns.
- Destination addresses are derived by preserving the selected source local-part and replacing its domain with the administrator-supplied destination domain. Review exceptions before import.
- Reverify the vendor schema before a future release if BitTitan changes its documented import format.
Generate the script
- Open this template in the PowerShell Builder.
- Enter the required values and review the documented permissions and output.
- Generate the script, inspect it, then run it in your own PowerShell environment.
OPS / SCRIPT DETAILS
Script details
Validates an Opselith migration identity dataset and builds a MigrationWiz Bulk Add CSV containing only the documented Source Email and Destination Email columns, plus a separate validation report. Review these details before generating or running the script.
Permissions and impact
Permissions: No tenant or MigrationWiz permission required for local CSV preparation.
Risk: Low
Execution impact: Read-only. Reads administrative data and does not intentionally change the target environment.
Parameters
- Opselith identity dataset CSV - Use the CSV produced by #121 or a compatible dataset containing PrimarySmtpAddress and UPN columns.
- Destination domain - Destination SMTP domain, for example target.example. Do not include @.
- Source address basis - Choose which normalized #121 source column becomes Source Email.
- MigrationWiz Bulk Add CSV path - Output contains exactly Source Email and Destination Email.
- Validation report CSV path - Separate row-level validation report. Use a different path from the Bulk Add CSV.
Output
Output: MigrationWiz Bulk Add CSV with exactly Source Email and Destination Email. · Validation CSV with SourceObjectId, SourceAddress, CandidateDestination, Status and Reason.
This template is part of the Pro library. The full Pro script is generated by Opselith after server-side license validation; only the configuration values needed by this template are sent for generation. No tenant connection is required. When you generate a Pro script, only the configuration values needed for that template are sent to Opselith after license validation.
Example use
Validates an Opselith migration identity dataset and builds a MigrationWiz Bulk Add CSV containing only the documented Source Email and Destination Email columns, plus a separate validation report.
Enter the required values in the Builder, review the generated script and confirm the output before running it.
Before you run: Reconfirm the destination domain and mapping basis. Review the validation CSV before importing the Bulk Add file into MigrationWiz.
Opselith quality checks
- Included in the current Opselith PowerShell quality suite
- Vendor schema verified against current BitTitan documentation
- Only required vendor columns emitted
- No password/login columns
- Invalid and duplicate mappings isolated
- No vendor API calls
Was this useful?One click. No email.