Switching
Switch systems without handing over the keys to your business.
Your history comes across. Your data stays yours. The export that would let you leave again exists from your first day.
| From your system | Into Recruited | What happens |
|---|---|---|
| Candidates | Candidates | Matched on email, then phone. Anything softer is queued for review rather than merged. |
| Companies | Clients | With the contacts attached to them. |
| Contacts | Contacts | Kept distinct from candidates. A person can be both. |
| Jobs | Opportunities | Open, filled and closed, with their dates. |
| Applications | Candidacies | Including the stage each one reached. |
| Placements | Placements | Fees and guarantee dates where the export includes them. |
| Notes and activities | Timeline | Chronology preserved, author preserved where the source records one. |
| Tags and lists | Tags and pools | Mapped to the controlled vocabulary, with the unmapped ones shown to you. |
| Users and owners | Members | Owner assignment survives; logins do not migrate. |
| Attachments | Documents | Only where your source export actually contains the files. |
Dry run, then reconciliation
- Exceptions Every row that could not be mapped, with the reason. The rows, not a count.
- Totals Records in the export against records created, side by side, per category.
- Sampling Records you pick, opened next to their source, before you approve anything.
- Re-runnable Fix the mapping and run it again. Rows update rather than duplicate.
The trust statement
What we do with your data during a migration, and what we do not.
-
Used only to deliver your migration
Nothing about your database informs our own commercial activity.
-
Isolated from agency operations
Migration staging is separate from every workspace, including LINK’s. LINK is an ordinary customer with no privileged access to anything.
-
Not used to train shared models
Your records do not train a model that serves another customer.
-
Deleted, with evidence
Staging files expire on an agreed schedule, and you get evidence of the deletion.
Two pathways
Do it yourself, or have us do it with you.
Both use the same importer. The difference is who does the mapping and who chases the exceptions.
Guided self-serve import
Included on every plan. Export from your current system, upload, map the columns, run a dry run, review the exceptions and run it again until it is right. Suited to a single clean source and a database you know well.
Confidential managed migration
We scope it, run the mapping, chase the exceptions and produce the reconciliation with you. Suited to multiple sources, years of history, or a database nobody has audited since the last system change. Quoted against scope; included in Enterprise onboarding.
The process
Six steps, and no cutover you have not approved.
-
Confidential discovery and scope
What you hold, where it lives, how clean it is, and what your current system’s export produces. Under confidentiality, before any data moves.
-
Export from your current system
Written instructions for your source, and a list of the objects we expect to see. We do not ask for your login.
-
Secure staging and mapping
Files are uploaded to isolated staging with an expiry. Rows land in a staging table before anything is created, and you see the field-by-field mapping before you approve it.
-
Dry run and exception review
Every row that could not be mapped, with the reason. Fix the mapping and run it again; rows update rather than duplicate.
-
Reconciliation and approval
Records in the export against records created, per category, side by side. You pick samples and open them next to their source. Nothing goes live until you approve those numbers.
-
Cutover, then deletion evidence
You go live on an agreed date. Staging files are deleted on the agreed schedule and you receive evidence of it.
Sources
Where we import from.
Each of these works from that system’s own documented export.
-
JobAdder export
ConnectedImported from the source system’s own export files. What comes across depends on what that export contains, and the mapping is published before you commit to it.
-
Bullhorn export
ConnectedAs above. Attachments and full email bodies are migrated where the source export includes them.
-
Vincere export
ConnectedAs above.
-
Recruit CRM export
ConnectedAs above.
-
CSV and Excel
ConnectedThe general path, and the one every other preset falls back to. Rows are staged, mapped, dry-run and re-runnable before anything is created.
Categories
What we map.
- Candidates
- Clients
- Contacts
- Opportunities and jobs
- Applications and submissions
- Placements
- Notes and activities
- Tags and lists
- Users and owners
- Communications metadata
- Attachments, where the source export includes them
Every importable record carries the source system and source id it came from, with a unique index on the pair. That is what makes “import, look at it, fix the mapping, import again” a safe loop rather than a duplication event.
The exit
The export that lets you leave.
Every plan can export the whole workspace in an open format, at any time, without asking. It is the same mechanism whether you are taking a backup, moving to a warehouse, or moving to another system.
Rollback and recovery
A cutover that goes wrong is recoverable: your source system is untouched, the import is re-runnable, and staged data is retained until you confirm the cutover succeeded.
Questions
Will you look at our data?
Only to deliver the migration you asked for. Migration data is isolated from Recruited’s own agency operations, is not used to train models across customers, and is deleted from staging on an agreed schedule with evidence of deletion.
Does LINK, or any other customer, get access to our records?
No. LINK is an ordinary customer workspace with no privileged access to any other workspace. The tenant boundary is enforced in code, in one place, and tested.
How long does a migration take?
It depends on the source system and the state of the data, so we scope it before quoting a date. A clean single-source migration is usually a matter of days between the export and the cutover. A merge of several systems with duplicate records takes longer.
Will our attachments and email history come across?
Where your current system’s export includes them. Some exports contain CVs and full message bodies; some contain only metadata. We tell you which yours is before you commit.
What if the dry run looks wrong?
That is what it is for. The dry run produces an exception report and reconciliation totals before anything is committed. You fix the mapping and run it again. Nothing goes live until you approve the numbers.
Can we get our data back out afterwards?
Yes. At any time, on every plan, in an open format, including the day you decide to leave.
Switching
Find out what your data would look like here.
A migration assessment is a conversation about your sources and their exports, under confidentiality, with no obligation and no request for your database.
We reply within one Australian business day.