Notes to Exchange Migration » Notes to Exchange

Improper data transfer during Notes to Exchange migration

admin — Sat, 03 Apr 2010 10:35:08 +0000

It is quite common situation that you come across when task information is not migrated properly and completely during Lotus Notes to exchange migration. This happens when you export Lotus Notes profile user’s email messages, calendar information and task information from calendar to Exchange 2000 Server with the use of Migration Wizard for Exchange 2000. During Notes to Exchange migration, some migrated users complain that their tasks got migrated to their Outlook Tasks folders.

The reason behind this issue is that the Migration Wizard exports only the tasks that were included in Lotus Notes calendar. However, it works differently while migrating tasks for Lotus Notes. In order to resolve this issue, follow the procedure given below on the tasks for migrating calendar items.

Open your Notes mailbox in Notes 4.6x client
Change to the “To-Do” folder
Open the task that was not migrated
Now click the Display task on my calendar button. Button will then change to Remove from calendar
Save the task
Run Migration Wizard for Exchange 2000 again, the task is migrated to Exchange 2000

If you don’t get successful this way, then opt for third party tool for Notes to Exchange migration. Dealing with incomplete migration often results in loss of important data. Hence it is recommended that whenever you need to perform Notes to Exchange migration, switch to professional third party tools.

Migration from Lotus Notes to Exchange Server Fails

admin — Sat, 30 Jan 2010 11:30:26 +0000

Lotus Notes and Outlook are the most commonly used email clients in organizations that synchronize with Domino Server and Exchange Server respectively to establish email communication. Both of these email clients are feature rich. However, besides that you may need to switch from Domino Server of Lotus Notes to Outlook’s Exchange Server.

One of the scenario in which you have to switch from Lotus Notes to Exchange can be – you have been transferred to another branch of your organization and you want to bring all email messages with you because they are very important and you may anytime need one or more out of those email messages. But, the problem is that at new location you are provided with MS Outlook instead of Lotus Notes. Therefore, you cannot directly access your email messages because they are in unsupportable Outlook format. To access email messages with Outlook, you first have to convert them into Outlook supportable format that is from .nsf to .pst format. For this purpose, you can use Exchange Migration wizard. However, the Exchange Migration wizard sometimes stops the migration process in between and puts you in a dreadful situation.

Actually when you try migrating email messages from Lotus Notes environment to Exchange environment then Notes.pkl and Directory.pri files are created successfully. But, sometimes the 00000001.pri and 00000001.sec files are not created. At that time, Exchange Migration wizard gets automatically closed leaving the migration process in between.

Reason:

The aforementioned issue often occurs when user’s account using which you are doing migration does not have sufficient rights to access Organization, Site, and Server containers in Exchange Server Administrator program.

Solution:

Abrupt closing of Exchange Migration Wizard can lead to data loss; therefore, before starting the migration process, you must ensure that you have logged in using the service account. If you log in using the service account then the mentioned issue does not occur thus, there will be no fear of data loss.

In case, you face the specified issue even after undertaking the preceding solution, you can use Kernel for Lotus Notes to Outlook, a third-party migration tool, which has been designed for easy and successful migration of email messages from Lotus Notes environment to Exchange environment. If you use Kernel for Lotus Notes to Outlook to migrate email messages from Lotus Notes to Exchange then you do not have to face panic situations that generally occur with Exchange Migration Wizard. The software supports Lotus Notes 6.0, 7.0, and 8.0, all versions of Exchange Server and MS Outlook.

Exchange Server Migration Wizard unexpectedly stops responding

admin — Sat, 02 Jan 2010 10:59:10 +0000

There are various issues related with Exchange Server migration wizard, whose job is to perform migration from Lotus Notes Domino Server to MS Exchange Server. It’s really a tough job to get this whole migration thing done in an unproblematic manner. But one has to do it, if you want all your Lotus Notes stuff exported to MS Exchange Server.

One of the most prominent issues that crop up is the unexpected shutting of Exchange Server migration wizard. This creates panic among the users as the fear of data loss is always there. When you use the Exchange Server Migration Wizard in MS Exchange Server 2003 to migrate a Lotus Notes mailbox, the Exchange Server Migration Wizard all of a sudden stops responding, while exporting the Lotus Notes Calendar items.

Reason

The main reason behind this vague behavior of Exchange Server migration wizard is the corruption. Whenever the Lotus Notes mailbox .NSF file contains corrupted data within, Lotus Notes to Exchange Migration Wizard may unexpectedly stop responding when it tries to process the corrupted data. Hence the outcome is incomplete or unsuccessful migration from Lotus Notes to MS Exchange Server.

Solution

The best way out for dealing with such issue is to obtain the latest service pack for Exchange Server 2003. The latest versions are free from any previous anomalies existing. If still you are not finding the exact solution, then go for some third party email migration tools. They are thorough professional tools that migrate each and every item from Lotus Notes to Exchange Server. Emails, notes, contacts, appointments, to-do lists, drafts, even calendar items everything gets migrated to Exchange Server, without any migration issue arising.

Kernel for Lotus Notes to Outlook is considered to be the best exchange migration software that pips other same range software available. Kernel for Lotus Notes to Outlook/Exchange supports every version of Lotus Notes, MS Outlook, MS Exchange Server and Lotus Domino Server to perform the conversion process.

Nested DocLink is deleted while using Exchange Migration wizard

admin — Sat, 26 Dec 2009 10:54:12 +0000

When you migrate from Lotus Notes to MS Exchange Server, the nested Doclinks are also supposed to be migrated from Domino Notes Server to Exchange Server. But the Exchange migration wizard most of the times, deletes the nested DocLinks during the migration process. Actually a nested DocLink is a DocLink inside another DocLink (nested).

The reason for this abrupt behavior of Exchange migration wizard is the formatting problem. Exchange migration wizard converts email data into RTF format after migration. Converting DocLinks to Rich Text Format (RTF) format creates problem and is bounded with limitations.

For resolving this issue, you must use one of the additional formatting options available in the notes to Exchange Migration Wizard for exporting Lotus Notes to Outlook. Like, you can use a URL format or an OLE format. These options provide a link back to Lotus Notes, so the formatting issue gets resolved in case of nested DocLink. With these options access problems during migration get resolved because the link now points back to the original data in Lotus Notes.

To change the format of DocLinks, follow these steps:

Start the Exchange Migration Wizard for Lotus Notes.
Under “Specify how to convert Notes DocLinks” option on the Migration Information page, select the format that the Exchange Migration Wizard will use to convert Lotus Notes DocLinks.

Following are the options you will be provided with.

OLE format – It is represented by an icon in the Exchange message. When this icon gets clicked, Lotus Notes starts and the nested DocLink works as usual. Lotus Notes must be installed on the client.

RTF format – With this the document is converted to RTF (Rich Text Format) format. This attachment is a copy of the data from the original Lotus Notes document. Therefore, users cannot modify the document.

URL format – This format converts the link to a URL. Firstly when one clicks on the URL, the default Web browser starts. The default Web browser then tries to access the server that the URL points to. This is the server that is running Lotus Notes.

No doubt conversion of DocLink to RTF format creates problem for the user. The aim of the migration wizard must be to resolve and access the DocLink in an unproblematic way. Usually, network or permissions problems may prevent you from accessing the document. Accessing a DocLink that is contained in another DocLink can be even more problematic. With above mentioned steps, you can assure yourself for minimal complexities involved in the whole nested DocLink migration process.

Kernel for Lotus Notes to Exchange Migration is a treat for all those who are looking for a seamless migration from Lotus Notes to MS Exchange Server.