Switching from your current HR system
Switching is a plan, not a leap.
Most of the risk in changing HR systems is in the data and the payroll. The plan takes both off the critical path: your people come across with a preview you check row by row, and your payroll keeps running until your payroll team has signed off the parallel runs.
Step 1
We bring your people across.
Import people, positions, pay history and leave balances from your current system's files, with a row-by-row preview and 30 days to undo. Where your current HR system stays in place for part of the group, andteam syncs from it, or connects through the API.
Step 2
Keep running your current payroll while you switch.
Your payroll keeps running where it runs today, untouched. When you are ready, move to Deel Local Payroll, powered by PaySpace, after parallel runs that your payroll team signs off.
Step 3
Live in about 12 weeks, run with you.
Kick-off, people data, setup, documents and signing, testing and training, then go-live and hypercare. Real dates are set from your go-live date.
Step 4
Everyone is on their phone from day one.
At go-live every employee signs in to the portal at your own andteam address. No app to install.
A typical plan
All staff live in week 12.
Typical plan in weeks from kick-off. Real dates are set at kick-off from your go-live date. The phases overlap: configuration and documents are built while the people data is being reconciled.
- 1Kick-off and setupWeeks 1 to 2
- 2People dataWeeks 2 to 6
- 3Module configurationWeeks 3 to 9
- 4Documents and signingWeeks 3 to 9
- 5Testing and trainingWeeks 9 to 11
- 6Go-liveWeek 12
- 7HypercareWeeks 12 to 15
Your people, brought across
Import people, positions, pay history, leave opening balances and training records from CSV or Excel exports of your current system. Column mappings are saved per source, so the same export maps the same way next time. Each import shows a row-by-row preview (new, changed, unchanged or error), then applies every valid row, and any import can be undone within 30 days, field by field.
andteam connects to your current HR and payroll systems through import, scheduled sync and the API. Where part of the group stays on its current HR system, andteam syncs from it on a schedule. A field supplied by that system is read-only in andteam and corrected at the source; someone missing from the feed is flagged, never terminated by the sync.
Payroll on its own track
Your payroll keeps running where it runs today while you switch. When you are ready to move to Deel Local Payroll, powered by PaySpace, andteam runs PaySpace in parallel with your current payroll, comparing inputs and then results, and your payroll team signs off each parallel run. In a typical plan the switch is in about week 25.
Going live in waves
You can go live with one division first and bring the rest live once it is settled. The plan then adds the extra waves from week 12 onward.
Day one
At go-live every employee signs in to the portal at your own andteam address, with your single sign-on or a one-time code to their work email. There is no app to install. A sandbox tenant with a copy of your settings and sample people is where HR, managers and administrators train before they work in the live one.