With proper administrative privileges on both sides, you can create the .PST files from separate desktops running simultaneously. Note that Microsoft does everything it can to make true full administrative privileges difficult in Exchange, but it can be done.
We did a modified version of the second part of Rick’s suggestion (creating a second Domino server) and that worked well when we were testing migration. Timing becomes an issue, but you can do mail forwarding from Domino when the mail database is migrated to minimize lost mail. When all done, then you can change the MX record.
CSUS System Office
Hartford, CT 06105
The server-side tool would require access to the Domino / Notes server. Since you don't have that, Kevin suggested an approach that gets you where you need to be.
It's not pretty nor elegant, but it meets the requirements you presented.
An alternate approach could be to stand up an Exchange server (and from the sound of things, a DC) in close proximity to the Notes server, use the server tools that are available (either free, which are a bit wonky but generally work, or a commercial tool), migrate to that server, then disconnect it and transport it to your other location. Turn it back on, and fiddle with it a bit to get it back on the network and replicating with the Exchange Org.
At that point you could move the mailboxes onto your existing infrastructure and retire that server.
Alternately, you could stand up a Notes server at your location and bring the NSF in, then use the server tools to migrate.
Also not pretty but a bit more elegant. And it accomplishes your goal of avoiding hitting each desktop.
But timing would be an issue. You would need to manipulate your MX records to make sure no mail is lost while doing the moves (which I guess, as I think about it, you will need to do anyway given the fat you are planning to export and move the NSF file).
On Apr 29, 2008, at 4:42 PM, Jabber Wock wrote:
Thanks Kevin, that was very helpful. As I understand it, this creates an Outlook PST file. So with this tool, each user will be responsible for creating their own PST file and re-importing it into Outlook?
Is there a tool that can create server side PST files (i.e. ExMerge compatible) from Lotus Notes NSF files, so that we do not have to either rely on each user to do it for themselves or have to visit each workstation (across multiple geographical locations)?
For example I came across some promising and low cost shareware tools, does anyone have any experience with them?
Other tools like this one are super expensive, about 10x the cost of the above:
On Tue, Apr 29, 2008 at 9:06 AM, Kevin Suares <suaresk@xxxxxx> wrote:
In this case, you would have to install the Outlook Connector for Lotus Notes (or DAMO) and create a local .PST file for each mail file in Domino. Once you do this, getting the mail file into Exchange is relatively easy.
Note: on the Lotus side, change the mail template to one of the Web Access templates (assuming Notes v. 6.x or higher) then synchronize the Address Book and Journal (if used) from the client before creating the .PST file. This will populate contacts and journal entries in Exchange, making the transition much easier for the users. If this isn't possible, then march on anyway.
This isn't a trivial move. Do it on a test system several times before running it in production, since the free tools supplied don't work flawlessly. There are multiple issues we ran into with file size and problems with the Lotus / Exchange Migration tool that made this task difficult.
CSUS System Office
Hartford, CT 06105
Jabber Wock wrote:
I need to migrate about 100 users from Lotus Notes to Exchange 2003 (not 2007). The Lotus server is in a remote network, not local LAN. There is no possibility of connecting them on the same network or AD. I am told that I will get the Lotus NSF files and that's it. There is no encryption involved.
Any suggestions on how to migrate these users to Exchange? If you have done such a migration please let me know what you did. All the articles I have found so far appear to assume that the two servers are in the same network and AD and that is not the case foir me.