Migration wizard: Review — Email conflicts during the preview

What happens

During the preview, the wizard checks whether any of your Classic employees' work email addresses already belong to someone else in Simployer One. Depending on what it finds, one of a few things happens automatically — you don't need to do anything to trigger this check.

If you run into a problem

• Records skipped due to email conflicts (same company) — if a work email is already used by an existing active Simployer One employee in your own company, that record is skipped. Hover the count shown for a breakdown by entity (persons, employments, department assignments, manager relationships).
• Email automatically changed to resolve a conflict — if the conflict is with another active employee, that person's work email may instead be automatically changed slightly so they can still be migrated. The original email is visible in the warnings report — correct it in Simployer One after migration.
• "The migration cannot continue" — active person's email registered to another account — if an active person's work email is already registered under a different Simployer One account entirely, the migration is blocked outright. Contact us to resolve this.
• Inactive person's email registered to another account — this doesn't block the migration; the person is migrated with an automatically prefixed email address. Correct it in Simployer One only if that person is ever reactivated.
• "We could not check" for cross-account email conflicts — the preview is otherwise complete; any such conflicts are instead reported when the real migration runs.