Skip to main content

One or more of your migration users has the same 'Import name'

When you reach the Summary step of a migration batch, CloudM Migrate validates the configuration before it lets you start the migration. If two or more of the items in the batch are set to migrate into the same destination, you see an Attention needed warning instead of being able to continue.

The Summary step of a migration batch with an Attention needed warning and a View migration errors link

Click View migration errors to see the detail. The Configuration errors window names the entity type affected and lists the addresses that clash:

One or more of your migration users has the same 'Import name'. This is not permitted and would cause database and account discrepancies. The duplicate users found were…

The Configuration errors window showing the duplicate Import name error and the list of affected user addresses

Cause

The Import name is the destination identity of an item in Items to migrate. For a user, that is the primary email address of the destination account. Migrate expects every import name in a batch to be unique, so that each source item has its own destination item to migrate into and its own migration report.

This error means at least two items in the batch share an import name while the setting that permits that is switched off. Migrate stops the migration rather than merging the items quietly, because writing two source items into one destination account when you have not asked for it causes database and account discrepancies.

The clash usually arrives with Get items from source. That option scans the source and populates the list with everything it finds that matches the batch type, and it does not check the import names against each other, so nothing flags the problem while you are still on the items list. Items you add with Manually enter are checked as you add them, and the form refuses a duplicate import name outright. Adding Items to a migration batch covers how each option behaves. The habit that avoids this error is reviewing the items list before you move on, rather than leaving it to the Summary step.

How you fix it depends on whether the duplicates are deliberate.

The duplicates are not intended

Correct the import names so that each item points at its own destination.

  1. Note the addresses listed in the Configuration errors window, then click Close.
  2. Go back to Items to migrate.
  3. Search for each address from the list.
  4. Change the Import name on the affected items so that no two items share one, and remove any item that was added twice by mistake.
  5. Return to the Summary step and check that the warning has cleared.

If you built the list from a spreadsheet, it is usually quicker to use Export on the items list, fix the import names in the CSV file, and upload the corrected file with the bulk CSV option.

The duplicates are intended

If you do want several source items to go into one destination item, for example consolidating a number of mailboxes into a single mailbox, turn on the setting that allows it. There are reporting and configuration consequences to this, so read Migrate Multiple Source Items to a Single Destination Item before you start.

  1. Go to Configuration > Advanced settings > System.
  2. Enable Allow multiple sources. This setting allows the migration of multiple source items of the same type to a single destination item.
  3. Return to the Summary step and check that the warning has cleared.

Two things to be aware of before you enable this:

  • The source and destination items must be the same object type, so user to user, or shared drive to shared drive.
  • Reporting is tied to the import item name, so you do not get an individual report for each source item. Migrate produces one report per unique import item, covering the total count of items migrated from all of the source items feeding into it. If you need a report per source item, use separate batch configurations instead of this setting.
Was this article helpful?
0 out of 0 found this helpful