By HireHint
Last updated October 18, 2026On this page
A migration is a controlled transfer of information and responsibility. Start by deciding which records you need and how you will verify them after import.
This guide is a planning method. It does not promise a particular HireHint import format or the transfer of every historical field.
Create a small source inventory
List the systems and files holding jobs, candidates, applications, documents and team feedback. Identify who owns each source and which records can be transferred.
- Separate candidate profiles from applications to particular jobs.
- Record whether attachments, messages, consent records and activity history are required.
- Identify duplicate profiles and fields whose meaning differs between systems.
Review a redacted mapping example
Use a small redacted sample to agree the mapping with the receiving vendor before preparing a full export. Include at least one candidate with two applications, one attachment and one missing optional field.
| Source concept | Mapping question | Acceptance check |
|---|---|---|
| Candidate identity | How are duplicate people matched? | Two applications retain the intended single candidate identity |
| Application and stage | Which job and stage receive each application? | The expected job, stage and owner are visible |
| Documents | Which file types and sizes are accepted? | The intended authorized reviewer can open the correct file |
| History | Which events and messages can be transferred? | Supported history is present; excluded history is documented |
| Dates and owners | How are time zones and authors represented? | Dates and ownership match the agreed interpretation |
Rehearse before the final transfer
Agree how failures, duplicate records and retries will be handled. Use an authorized test environment or a deliberately scoped rehearsal so the team can inspect the result without confusing it with normal recruiting work.
- Compare expected and resulting counts by record type.
- Check a sample of individual records and their relationships.
- Verify permissions with each intended role.
- Document excluded fields and a recovery or rollback approach.
Agree the handover and exit plan
Choose who signs off the result and when the old source stops receiving changes. Keep the reconciliation record with the migration instructions.
When evaluating HireHint, ask the team to confirm the supported transfer method for your specific source. Request a clear answer for attachments, history, ownership, duplicate handling and later export rather than assuming that one import supports every field.