I'd like to start by stating that no formal training on BES administration but I've inherited a BES migration from 4.1.7 to 5.0.4. The 5.0.4 has already had a dozen or so users added but I have over 100 more users to migrate. The Transporter seems like the best option considering the circumstances but when I ran my first test the process completed with a MigrationCompletePending message. The test account was removed from the original BES but never appeared on the new one.

I've seen a post here suggesting to not assign policy during the transport so I left all those fields blank for my second test - still no joy.

Any recommendations?

I am using the transporter from brk 5.0.4.8 which is the latest available. My new BES is running at version 5.0.4 MR 1 (Bundle 52).

Thanks,
Cam

Is the transporter able to make a successful connection to the destination database?

Connection tests on source and destination BESMgmt databases were successful. No errors or warning in the Preview step.

Have you tried migrating any other accounts, and does the error happen for all account migration attempts?

I've tried twice now, the only difference being the group and policy assignments being left as default during the second transport. I read on another forum that this had allowed a transport when the assignment had resulted in MigrationCompletePending.

I also receive the following warnings in the BBET log:

SWITCH_SERVICE is still pending, device may be out of coverage
SET_IT_POLICY is still pending, device may be out of coverage

While going through the transporter logs I noticed my destination BES shows up as [5.0.3.13] when Programs lists it as 5.0.4 MR1; could the mismatch cause this or is it just how the versions are displayed?

I'm no expert on Transporter, but I use it occasionally. If you are using the same manifest file each time you attempt a migration, you might try to create a new manifest file and retry.

Also, if possible I would try and migrate an account in which you are able to verify that the device is not out of coverage and that is successfully communicating with BES.

Unfortunately I have used new manifest files each full attempt. I realized after I attempted to migrate my first test account a second time that the manifest keeps track of accounts that have already been transported.

Didn't help that my test user also existed in the destination database despite not appearing in BAS manage users.

Both tests were done with a fully functional BlackBerry. I've tested activation on the new and old BES with this device to confirm and my signal strength is indicated as full.

I'm going to try a test with wireless connectivity and see whether that makes any difference. I'll post my results.

Still looking for help though if anyone has anything else to try.

Thanks,
Cam

The target BES needs to have all it's modules from the same version.

A couple years ago I used Transporter to move 2100 Users from BES 4 to BES 5.
The few that failed went out of coverage DURING the move.

I wrote an SQL query to read the Last Active Device, then automatically created the Manifest file. Worked like a charm, I moved about 100 people a night.