IMAP to Exchange 2003 Migration Errors

Attempting to migrate mail for 30 users (single site, single domain) from qmail IMAP on BSD 5.4 to Exchange 2003 SP2 running on MS Small Business Server 2003 R2, using the migration wizard that comes with Exchange 2003.  We have created the requisite .csv file and many accounts migrate without error.

A few accounts, however, do not fare so well.  We are getting the following messages on the SBS server before the migration wizard blows up and disappears:

Event ID: 8067 - Unable to allocate memory
Event ID: 8071 - Unexpected error while streaming out data

The SBS server is an HP Proliant ML-310 with 3GB of ECC DDR2 over a 100baseT connection.  The qmail server is far less robust, but shares the 100baseT line.  Migration attempts have taken place during busy hours and dead hours with similar results.

Please help?
Who is Participating?
This behavior occurs when you do the following

1. You create an Imapuser.csv user list file.

2. You run the Migration Wizard, you click Migrate from Internet Mail (IMAP4), and you then click Extract migration files only.

3. You run the Migration Wizard again, you click Import from Migration Files, and you then click Migrate to .pst files in the Migration Destination dialog box.
During the file extraction process, the IMAP4 extractor extracts the mailbox contents to Interchange File Format (IFF) files. Although the Migration Wizard user interface does not prevent you from importing IFF files that are generated from an IMAP4 extract, the migration from these IFF files to personal folder files is not supported by the Migration Wizard.

To work around this behavior, do not use the Migration Wizard to convert the mailboxes to personal folder files. Use the Migration Wizard to migrate the messages directly from an IMAP4-based messaging system to a computer that is running Microsoft Exchange. You can then use Microsoft Outlook to export the mailbox contents to personal folder files.

There are three types of IFF files: packing list files (.pkl), primary files (.pri), and secondary files (.sec).
waifurchinAuthor Commented:
Ah... I wasn't clear in the first message - many apologies.

We are doing a single step migration.  Most of the accounts work fine, but some of the larger mailboxes are causing issues.  

Doing a bit of digging, we found a different free utility to convert the mail from IMAP to Exchange that doesn't stall out.  Utility is called IMAPCopy.  It requires roughly the same information, and runs from a DOS command line, but works great.
for those large boxes the above analogy works.
Forced accept.

EE Admin
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.