Migration wizard: Skip and failure reasons explained

What this covers

Wherever the wizard reports a skipped or failed record — in the dry-run preview, the live migration, or the verification report — you can view the exact reason next to that record. This article groups the most common reasons by theme so you know what they mean and what, if anything, to do.

Email address problems

• Duplicate work email in Simployer Classic — the same work email is used by more than one person in Simployer Classic. Give each person their own work email in Classic, then run the migration again.
• Work email already used by a different employee in Simployer One — the person was skipped so the existing employee's email isn't overwritten. Correct one of the two addresses, then run the migration again.
• Work email already registered under a different Simployer One account — the person can't be migrated at all. Ask them to use a different work email in Classic, then run the migration again.
• Invalid email format — the person's email address isn't a valid format and was left out. Correct it in Simployer Classic, then run the migration again.

Employment and mapping problems

• Employment type not mapped — the Classic employment category hasn't been mapped to a Simployer One type. Map it on Map employment types, then run the migration again.
• Employment type set to ignore — you deliberately chose to skip this type on Map employment types; this is expected, not an error.
• Employment period overlaps an existing record — check for duplicate or overlapping employment periods in Simployer Classic.
• Employment dates outside the allowed range — an end date before the start date, or an employment running longer than the mapped type allows. The wizard adjusts what it safely can (for example, dropping an invalid end date); check the corrected record in Simployer One.
• Country mismatch on employment type — see Preflight blockers and tenant setup.

Person data validation problems

• Invalid social security number, birthdate, or phone number format — corrected the format in Simployer Classic, then run the migration again.
• Gender value couldn't be mapped — correct the value in Simployer Classic, then run the migration again.
• Missing address details — left empty in Simployer One rather than blocking the record.
• Manager relationship is circular — fix the reporting chain in Simployer Classic, then run the migration again.
• Department assignment couldn't be migrated — no matching department was found in Simployer One; run the Departments step first, then this step again.

Offboarding and date problems

• Person not offboarded — employment still open in Classic, or end date in the future — offboard them in Simployer One once you confirm they've actually left.
• Person marked inactive with no end date in Classic — offboard them manually in Simployer One if they've left.
• Offboarding date corrected to match Simployer Classic — informational; no action needed unless the corrected date looks wrong.

Already-existing or nothing-to-migrate

• Record already exists in Simployer One — left as-is, not overwritten.
• This run was set to only create/update records — expected, based on how the migration run was configured.
• Absence starts and ends at the same moment — nothing to migrate.
• Vacation balance already matches, or was already migrated in a previous run — no change needed.

Anything else

If a record shows a reason not covered here, the report text itself explains what happened and, where there's a fix, what to do next. If a reason simply says the record wasn't migrated with no further detail, contact us if you need it brought across.