MS (Microsoft) Exchange 2013 email migration Tool
Budget: $750 – $1,500 USD
Objective
The long-term goal is to have all of Microsoft platforms (on-prem Exchange all versions, Hybrid, O365, Exchange Hosted) data migrations handled by the Tool we wish to build. Short term, we need to prioritize Exchange 2013.
Exchange 2013 Requirements
The Tool is Windows Python app with GUI for exporting mailboxes from the Exchange server
The Tool is deployed on the Customer Windows machine on the same network as the Exchange server.
The Tool needs to connect to an external storage drive to store exported PSTs:
- Option 1: Ability to place the files in the CIFS ingestion folder locally
- Option 2: Ability to mount AWS S3 bucket via win3fs
The Tool application needs to install all required underlying libraries to run PowerShell on the customer computer that is deploying the Tool. It should be deployable on Windows 8.1+ or Server 2012+.
The Tool is configured with appropriate Exchange user credentials by the Customer: New-ManagementRoleAssignment -Role "Mailbox Import Export" -User "<user name oralias>"
Customer selects:
- the mailboxes they wish to export in the Tool. By default, this is all mailboxes. But they can select specific ones
- Date Range: from and to date and time
- Content Filter: specific text to filter export by
- Is Archived: select whether to get archived data or not
- Exclude Folder (deleted items, calendar): Include or exclude deleted items and calendar invites
The Tool automatically performs the data export from Exchange 2013 by using the load-balanced Microsoft recommended underlying PowerShell commands automatically for example: New-MailboxExportRequest -Mailbox <user> -ContentFilter {(Received -lt'01/01/2021') -and (Subject -like 'fwd*')} -FilePath \<server FQDN><sharedfolder name><PST name>.pst
The Tool records the PSTs exported onto the storage mounted in step 2.
Tool logs into two logs:
- Error log includes all errors and warnings
- Main log includes all actions that were completed regardless of the outcome
Tool reports progress periodically on the user interface: Exported mailboxes vs total, #errors, elapsed time.
Need to have pause and resume, so Tool needs to keep the state internally on disk so it can resume.
The long-term goal is to have all of Microsoft platforms (on-prem Exchange all versions, Hybrid, O365, Exchange Hosted) data migrations handled by the Tool we wish to build. Short term, we need to prioritize Exchange 2013.
Exchange 2013 Requirements
The Tool is Windows Python app with GUI for exporting mailboxes from the Exchange server
The Tool is deployed on the Customer Windows machine on the same network as the Exchange server.
The Tool needs to connect to an external storage drive to store exported PSTs:
- Option 1: Ability to place the files in the CIFS ingestion folder locally
- Option 2: Ability to mount AWS S3 bucket via win3fs
The Tool application needs to install all required underlying libraries to run PowerShell on the customer computer that is deploying the Tool. It should be deployable on Windows 8.1+ or Server 2012+.
The Tool is configured with appropriate Exchange user credentials by the Customer: New-ManagementRoleAssignment -Role "Mailbox Import Export" -User "<user name oralias>"
Customer selects:
- the mailboxes they wish to export in the Tool. By default, this is all mailboxes. But they can select specific ones
- Date Range: from and to date and time
- Content Filter: specific text to filter export by
- Is Archived: select whether to get archived data or not
- Exclude Folder (deleted items, calendar): Include or exclude deleted items and calendar invites
The Tool automatically performs the data export from Exchange 2013 by using the load-balanced Microsoft recommended underlying PowerShell commands automatically for example: New-MailboxExportRequest -Mailbox <user> -ContentFilter {(Received -lt'01/01/2021') -and (Subject -like 'fwd*')} -FilePath \<server FQDN><sharedfolder name><PST name>.pst
The Tool records the PSTs exported onto the storage mounted in step 2.
Tool logs into two logs:
- Error log includes all errors and warnings
- Main log includes all actions that were completed regardless of the outcome
Tool reports progress periodically on the user interface: Exported mailboxes vs total, #errors, elapsed time.
Need to have pause and resume, so Tool needs to keep the state internally on disk so it can resume.
Related categories:
Windows Desktop
Software Architecture
Microsoft Exchange
Amazon Web Services
Windows Server