If your company is planning to jump from Novell GroupWise to MS Exchange 2010, these five tips will assist you to plan and accomplish a smooth changeover.
There has never been a better time to migrate from GroupWise to Microsoft Exchange Server. MS Exchange Server 2010 has taken a giant jump forward in terms of cost of possession, flexibility of incorporation, and ease of exercise and management. The capability to directly incorporate on-premises and online employments is a significant part of the new functionality of MS Exchange Server 2010, and migrating from Novell GroupWise to Exchange Server can deliver important advantages. Here are some tips to assist you defeat migration challenges and guarantee a flawless move.
1: Carry out a Pre-Migration Review
Attempt to acquire a clear understanding of what will be implicated and what criterion you will use to calculate accomplishment prior to beginning your migration. Be practical. For a variety of reasons, not each message in GroupWise will be unharmed after the migration, so it is difficult to anticipate 100 percent of your data to migrate effectively. Pick a possible threshold -- for example, 95 percent of messages should migrate for 95 percent of mailboxes and monitor your percentages. Monitoring outcomes is the key to any victorious migration, and that is feasible only if you begin with a pre-migration evaluation.
2: Provision Your Exchange 2010 Mailboxes
When you generate Active Directory items for Exchange 2010 mailboxes, you should keep in mind that the GroupWise directory is separate from eDirectory, and GroupWise resources don't require eDirectory user objects. If you are planning to export user objects to eDirectory, you may require to build them using a method that is dissimilar from what you used to generate typical user objects.
3: Incorporate GroupWise and Exchange 2010
Find out how directory synchronization among GroupWise and MS Exchange 2010 will be accomplished to guarantee that the GroupWise Address Book and Exchange Global Address List replicate the similar users, distribution groups, and assets. Use SMTP routing to way mail among GroupWise and Exchange and amid the joint GroupWise/Exchange hybrid system and the exterior world. Take note of message size restrictions and message set-up.
Mail flow among GroupWise and MS Exchange 2010 can be attained in either of 2 ways:
a. Exchange 2003 Connector for Novell GroupWise
b. SMTP forward domain
Calendar free-busy lookup is accessible only if you set up an Exchange 2003 machine running the appropriate coexistence connectors prior you install Exchange Server 2010.
4: Run a Pilot Migration
The objective of a pilot migration is to recognize challenges which you may have to face once full migration begins and find out how to avoid or resolve them. Thus, you should anticipate, and even welcome, troubles throughout the pilot migration, which must be big enough to detain a representative sample of the problems that could take place during migration. If the number of mailboxes you are going to migrate is in the low thousands, then nearly 5% of the total people should give a good sample. This percentage can be lesser for tremendously big migrations.
Prior to running the pilot migration, identify how swift the data can be moved by performing a proscribed migration of a known amount of production GroupWise data on a sole migration server. This will provide you a migration baseline based on the throughput in a GB / hour. The throughput states how much time will be taken to migrate the total volume of data and, so, how long the project will run.
The pilot migration also will aid you in finding out the amount of disk space needed on the target, which can differ to a great extent from the source, depending on your version of Novell GroupWise and the platform on which it is being run. Occasionally, the volume of data on target will be larger than the data on the source, and the only method to recognize how your data is going to perform is to test it.
5: Migrate the Data and Track Migration Progress
After every group of mailboxes is migrated, find out the total number of messages moved, the total number of messages filtered (missed out), and the total number of errors or notices per mailbox. The software solution which you are going to make use of for this task should offer individual logs for every migrated mailbox that includes the total number of messages and appointments the mailbox enclosed prior to migration. Include the number of filtered objects to the number of moving objects, deduct the number of errors, and divide the outcome by the total message count to estimate a percentage. If that percentage is 98 percent or upper, you can self-assuredly sign off on the mailbox as an accomplishment.
If you are still not able to migrate Groupwise to Exchange 2010 successfully using the above tips due to some problem in the migration process, then it is recommended to make use of any third party migration software which can easily migrate your Groupwise data to Exchange 2010 without causing any data loss during the migration process. You can try out Stellar GroupWise to Exchange Migrator which is the most-widely used migration software by the small to mid-sized to large corporations around the world.