During the third phase, you reconfigure SGMT again, this time to perform the migration to the new platform instead of the analysis, which is a read-only operation on the source Microsoft Exchange platform. In this way, the new target platform is built. At this stage the most critical activity is to enable the synchronization of the source LDAP platform with the target LDAP platform. Once you validate this step, users and mailing lists are synchronized between source and target. On the target platform, “shadow” users are ready with the correct attributes for their respective real users' migration.
During the third phase, you construct components that drive some of the acceptance testing. For example, you need to:
Set up a test LDAP server, on which you:
Add the SGMT schema, password plugin, indexes, and so forth
Pass the dirmapping on the current source LDAP server
Find and resolve LDAP errors
Implement mapping functions and test
Build a meta store of the source system, and process archival data that exists perhaps for legal or business reasons but that can be reprocessed afterwards, with:
A 'per message' md5, size, IMAP uid of mail messages for all users and folders
Reporting that enables you to understand users mail usage profiles
User allocation preparation and simulation until satisfying rule is found