Simply Migrate - Metalogix Archive Manager Exchange Edition Migrations

This guide will provide steps on how to migrate Metalogix to Mimecast using the Simply Migrate software. 

Prerequisites

1. Determine the SQL server name/instance that the Metalogix database is on.
2. Ensure that the account you are using has permission to read all the Metalogix databases.
3. Ensure the account being used has access to the Metalogix file shares.
4. Determine if the archives are user-only, journal-only, or a combination of the two.
5. Check if there is a journal cut-off date.

Performing a Migration from the Archive Manager Exchange Edition

As this is a source that contains a database you would need to first load the connection string to the SQL server and the name of the HSM Database and the Metalogix schema used.

Set-SmConfiguration -MetalogixConnectionString "Server=SMLABSQL\SMArchives;Database=PAMExchange;Trusted_Connection=True" -MetalogixHSMDBName PAMHSM -MetalogixSchemaName svarchiving

The below command will create a job to migrate the Metalogix mailbox “123” to PST.

New-SmJob -BatchID 1 -Source Metalogix -SourceInput 123 -Target Mimecast -TargetOutput [e-mail] -DateTo 2019-07-01

To generate a list of all mailboxes (mailbox "123") you can run the below command, be sure to change the output path to something relevant to your environment.

Get-SmMetalogixMailBox | Export-Csv -NoTypeInformation -Path C:\temp\metalogix.csv

Simply Migrate Metalogix PowerShell Commands

Analyze and test your migrations before starting.

Some of the examples below make use of the Export-CSV command in PowerShell which can sometimes be useful to visualize a lot of data.

The first command Get-SmMetalogixMailBox can be used to retrieve a list of Metalogix mailboxes.

Before running this you need to update the Simply Migrate configuration with 3 settings listed below:

1. Metalogix Connection String (SQL Server location).
2. The Metalogix HSM Database Name (normally something like HSMDB).
3. And the schema name (This is seen if you expand the tables i.e. dbo.ATPAMDBVERSION the schema is dbo).

Get-SmMetalogixMailBox -ExcludeDeleted -DisplayName Paul | Export-Csv -NoTypeInformation -Path r:\temp\metalogix.csv

In the above command we are retrieving all non-deleted mailboxes with a display name starting with Paul and exporting to CSV. The basic stats on each mailbox can help you plan and prioritize your migrations while the outputted CSV can be imported to create the migration jobs for each user.

The output of Get-SmMetalogixMailBox can be used to discover and plan as well as create migration jobs.

Once you have a mailbox you can inspect it further to make valuable decisions about the priority or filters to apply (folder or date ranges). For example, the next command Get-SmMetalogixFolderStructure retrieves the folder structure for a specific mailbox and the message count for each folder.

Get-SmMetalogixFolderStructure -MailBoxId 115 | Export-Csv -NoTypeInformation -Path r:\temp\folders.csv

A list of folders in a Metalogix mailbox can be used for analysis and planning as well as setting up Job filters.

If you want even deeper information you can use the Get-SmMetalogixDiscovery command to run a Mailbox discovery, this will show you basic folder and message information. You might want to use this information to find particular messages or plan your migration. 

Get-SmMetalogixDiscovery -MailBoxId 115 | Export-Csv -NoTypeInformation -Path r:\temp\meta.csv

A full Discovery can be exported to Return Folder and Message data from Metalogix helping to identify individual messages and plan migrations.

Finally, with the Export-SmMetalogixMessage command you can export individual messages, which offers an excellent solution for both testing and for extracting small subsets of data.

Export-SmMetalogixMessage -MessageId 212143 -OutputPath r:\temp