With this variant of the migration, users can continue to work almost as usual during the migration. The users are migrated one by one from Exchange to the Intra2net system.
The only limitation is that the individual user currently being migrated cannot work in Outlook during their migration. However, it is still possible for them to receive emails. The emails received during the migration can then be used as normal. In addition, during the migration phase, shared resources such as public folders or shared folders cannot be accessed across system boundaries.
Fully functional Microsoft Exchange Server
Intra2net Business Server in default configuration
Administrator rights for Exchange Server, Active Directory Domain and Intra2net Business Server
List of all users and their passwords in the local Active Directory
Access to the existing Outlook installations of all users
When fetching emails from an external provider via POP3: List of all logins and passwords for email retrieval.
Set up the Intra2net Business Server to have at least one IP on the LAN, DNS, appropriate local SSL certificate and access to the Internet. It requires a different IP than the former Exchange Server so that both can communicate with each other during migration. The configuration of the individual points is described in the Part 2, „General Functions“.
Ensure that on the Intra2net system, under no accounts have been created yet for normal users.,
Configure email dispatch via the Intra2net system, see Section 15.1, „Email Relay“.
In Exchange, store the Intra2net system as a relay server for sending all emails to the Internet.
Configure receiving emails via the Intra2net system and forward the emails to the Exchange. See Section 15.3, „Receive emails using the Intra2net system“ and Section 15.4, „Forwarding of entire domains“.
Test the receipt and dispatch of emails with the new configuration.
Test sending internal emails from Exchange to the Intra2net system. Use the login as the address and the fully certified local DNS name of the Intra2net system as the domain, e.g.
firstname.lastname@example.org. Check the Intra2net system's web groupware to see if the test email arrived.
If it is not already done, configure and enable access to emails on the Exchange Server via IMAP protocol.
If one or more users have mobile devices connected to the Exchange Server via ActiveSync, prepare them for ActiveSync use with the Intra2net system as described in 33. Chapter, „Connecting Mobile Devices using ActiveSync“.
Configure email archiving on the Intra2net system by going to. Archive either in a dedicated archiving system or at least in a separate email account. This will serve as a backup for newly received emails if something goes wrong during the migration.
Create a backup of all emails and groupware data on the Exchange Server.
Wait until the backup has been fully created and copy it to another server, for safety reasons.
Perform the following steps for each individual user.
Create the user with their access data and group membership on the Intra2net system.
Configure the user's email addresses under. Specifically, select the domains forwarded to the Exchange. From this moment on, new emails from the Internet to this user will arrive at the Intra2net system account and no longer on the Exchange.
On Exchange, set up an email forwarding for this user to their account on the Intra2net system. Use the login as the address and the fully certified local DNS name of the Intra2net system as the domain, e.g.
email@example.com. From this moment on, local emails to this user will also arrive at the Intra2net system and no longer at the Exchange.
During the migration, ensure that this user is no longer allowed to work in Outlook or OWA. Also deactivate all mobile devices that access this account via ActiveSync.
Use IMAPCopy to copy the emails of this one user from Exchange to the Intra2net system. The usage of IMAPCopy is described in 27. Chapter, „Migrating Emails with IMAPCopy“.
Open the user's Outlook installation.
Create a local Outlook data file that contains all groupware folders (not necessarily the email folders). To do this, use the Import/Export function of Outlook.
Install the Intra2net Groupware Client on the user's PC.
Create a new Outlook profile for this user and configure it for use with the Intra2net Groupware Client as described in Section 19.1, „Installing the Program“ and the following sections.
Transfer the groupware data from the previously created local Outlook data file as described in Section 126.96.36.199, „Importing to the Groupware Client“.
Check if there are users from the local domain in the contacts folders. If so, then the email addresses of these users must be changed from internal Exchange addressing to normal email addresses.
Check the Calendar and Task folders whether there are future appointments or open tasks in which other participants from the local domain are invited. These other participants are stored in the form of internal Exchange addressing and must be converted to normal email addresses.
For this user, reconfigure any existing mobile devices so that they are now using the Intra2net system for ActiveSync.
Open an Outlook installation with an Exchange profile that has full access rights to the shared folders.
Create a local Outlook data file that contains all public folders. To do this, use Import/Export on Outlook.
Create a general user account on the Intra2net system, such as
Set up a temporary Outlook profile on a PC for use with the Intra2net Groupware Client. Use the newly created user account.
Import the previously created data file into this Outlook profile.
Share folders with the Groupware Client to groups or individual users as required. See Section 22.1, „Sharing Own Folders“.
Give at least one user theright for all folders of the account. This user can manage access to the account.
Open themenu and wait for all data to be written to the server.
Close Outlook. The newly created Outlook profile is no longer needed and can be deleted.
Users who want to access the shared folders can now subscribe to them. The necessary steps are described in Section 22.2, „Linking Shared Folders“.