This article is not available in Swedish, view it in English
What happens
You land on Map employment types. Match each Simployer Classic employment type to the corresponding Simployer One type, so employments are created correctly during migration. Rows the wizard recognizes are marked Suggested; you can accept the suggestion, pick a different Simployer One type, or select Ignore this type to deliberately skip it.
Note: These mappings apply when employments are created during migration — you can still change an individual employment's type in Simployer One afterwards.
Save your mapping, then select Continue to move to Review.
If you run into a problem
- Could not load employment types — select Retry, or contact us with the reference shown if it persists.
- Some employment types aren't mapped — a warning shows how many Classic types have no Simployer One match; employments using them are skipped during migration until mapped.
- "Save your mapping before continuing" — Continue stays disabled until your mapping (even the auto-suggested default) is explicitly saved.
- You have unsaved mapping changes — the same save gate applies to any change you make after the initial save.
- No employment types found in the snapshot for this tenant — expected if your Classic tenant has none; there's nothing to map.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article