  Overview
FirstClass Migrator establishes a FirstClass connection when the migration process begins. After logging in, FirstClass Migrator retrieves FirstClass Directory information, caches it locally in system memory, and verifies Migration Status Log integrity. If no problems are found in the Migration Status Log, FirstClass Migrator starts migrating distribution lists, user accounts, and public folders, in that order.
After the migration process ends, whether from a successful completion, user interruption, or a fatal error, FirstClass Migrator ends the FirstClass connection and displays summarized migration results in a pop-up window.
Retrieving FirstClass Directory information
FirstClass Migrator retrieves FirstClass Directory information and uses it to build a structured table to cache the whole Directory in the local machine memory.
 NoteIf your FirstClass Directory is large, this process may take awhile.
When the Directory duplication is complete, FirstClass Migrator verifies the integrity of the Migration Status Log. If there are any inconsistencies, FirstClass Migrator stops the migration, ends the FirstClass connection, and prompts the user to perform a Migration Status Log synchronization before trying again. If there is no inconsistency, FirstClass Migrator proceeds with distribution list migration.
Migrating distribution lists
Microsoft Exchange distribution lists migrate to FirstClass as mail lists. The members of each list are replicated as follows:
� if the member has not been migrated, it appears in the FirstClass mail list as an SMTP address
� if the member has already been migrated, it appears as an existing FirstClass directory object
� if the member has not been migrated nor does it have a valid SMTP address, it is ignored and omitted from the mail list.
NoteIf a member was initially replicated as an SMTP address and is later migrated, the SMTP address in the mail list is automatically replaced with the corresponding FirstClass object.
FirstClass Migrator migrates each distribution list and records the result in the Distribution List Migration History Log. Once all selected distribution lists are migrated, FirstClass Migrator proceeds with account migration.
Migrating accounts
Microsoft Exchange accounts migrate to FirstClass based on your selections on the Application Properties form.
Hiding from Exchange Global Address List
To hide migrated Exchange accounts from Exchange Global Address List upon migration, you need to select the option "Hide from Exchange Global Address List" on the "Account Migration" settings tab.
We recommend this if you are using FirstClass Connector for Microsoft Exchange. If you do not set this option, two entries will exist in the Microsoft Exchange Global Address List when a Microsoft Exchange account is migrated to FirstClass: the original Microsoft Exchange account, and a contact (custom address entry) added by the FirstClass Connector that points to the migrated FirstClass user. This can be confusing, as both entries refer to the same individual. This will also cause message synchronization issues.
 ImportantSetting this option will affect distribution list migration significantly. If an account is hidden from the Global Address List, all backlinks are broken. So if an account is a member of one or more distribution lists, the account is removed from every list as soon as it is hidden, and ignored by FirstClass Migrator when the list is migrated.
The solution is to keep the "Hide from Exchange Global Address List" option unselected until all affected distribution lists have migrated, and then select Tools > Hide Migrated Accounts to hide the accounts all at once.
Forwarding messages from original Exchange accounts to corresponding FirstClass accounts
In order to enable the message forwarding function, you need to select the option "Forward received messages to the corresponding FirstClass account using FirstClass Connector" on the "Account Migration" settings tab.
Whenever FirstClass Migrator creates a new account in FirstClass, FirstClass Connector creates a corresponding contact (custom address entry) in the Microsoft Exchange Global Address List (see FirstClass Connector documentation for details). FirstClass Connector automatically forwards any messages sent to this contact to the corresponding FirstClass account.
To forward these messages, FirstClass Migrator sets the Exchange account's LDAP property "Alt-Recipient" ("altRecipient" for Microsoft Exchange 2000) to the address of the above contact. While Exchange 5.5 accepts any value (real or false) for this property, Exchange 2000 validates the property against the Global Address List, forcing FirstClass Migrator to wait until FirstClass Connector creates the Custom Address entry on Microsoft Exchange before setting the property. This operation can take up to a few minutes under certain circumstances.
Notes� While Microsoft Exchange 5.5 accepts any value (even a false one) when setting the Microsoft Exchange account's LDAP property "Alt-Recipient", Microsoft Exchange 2000 validates the given value against the Global Address List first. This forces FirstClass Migrator to pause the update until FirstClass Connector actually creates the contact in the Microsoft Exchange Global Address List.
This operation can take up to a few minutes under certain circumstances. You can specify a timeout on this operation on the "Account Migration" settings tab.
� A copy of the message will remain in the Microsoft Exchange account.
� Another way to implement message forwarding function is to use the "Forward Messages for Migrated Accounts" option after accounts have been migrated. This method is more flexible in that it allows you to select specific accounts to assign this option.
FirstClass Migrator migrates each account and records the result in the Account Migration History Log. Once all selected accounts are migrated, the Migrator proceeds with public folder migration.
Migrating public folders
Microsoft Exchange public folders migrate to FirstClass as conferences. The original public folder tree hierarchy is retained during the migration. You can designate a specific FirstClass conference, which resides on the FirstClass administrator's Desktop, as the root container for all migrated conferences.
You can choose to migrate any public folder, regardless of whether their parent public folders have been migrated. FirstClass Migrator automatically migrates the parent folders from the top level down if they have not already been migrated.
All types of public folders are treated equally by FirstClass Migrator except folders containing Appointment Items. These public folders are migrated as FirstClass group calendars, which are special conferences that contain FirstClass calendar events and tasks.
FirstClass Migrator migrates each public folder and records the result in the Public Folder Migration History Log. Once the selected public folders and their corresponding parent folders are migrated, FirstClass Migrator proceeds to migrate messages.
Migrating messages
FirstClass Migrator migrates Microsoft Exchange messages as follows:
� contacts migrate as personal addresses
� private distribution lists migrate as personal mail lists
� documents migrate as uploaded files
� appointments migrate as calendar events
� tasks migrate as tasks
� sticky notes migrate as documents
� all other supported message types migrate as plain messages.
FirstClass Migrator only migrates content that has not already been migrated, and migrates messages using direct field mapping (for example, Subject to Subject, To: Names to To: Names, and so on) except for the Last Modified Time.
| ||