Before importing, map each workbook column to a record, a relationship or a review queue. Approve the migration only after reconciling the sample results and having a second consultant complete a handover in the new system.
Preserve the file and describe the workbook
Keep an untouched copy with its tabs, formulas and row counts. Record which tab is authoritative for people, clients, jobs, contact history and status. Identify duplicate rows, combined fields, color-coded meanings and columns that only one person understands. A spreadsheet’s visual conventions are data too, but they need to be written down before they can be mapped.
A representative field mapping sample
| Spreadsheet column | Target record or field | Review question |
|---|---|---|
| Candidate full name | Candidate: name | Are preferred and legal names mixed? |
| Email / mobile | Candidate: contact details | Is the value current, shared or unverified? |
| Company / job code | Company and job relationship | Can the relationship be resolved to one record? |
| Stage / status | Job-specific pipeline stage | Which mandate does this stage refer to? |
| Last call notes | Activity or candidate note | Are source, date and author retained? |
| Owner initials | Assigned user or review field | Does the user still exist and own this work? |
The table is a mapping exercise, not a claim that every system has fields with these exact labels. Resolve any one-to-many relationships before importing: a candidate who appears in three role tabs may be one person associated with three jobs, not three independent people.
Test ordinary rows and exceptions
- Select ordinary, incomplete, duplicated and conflicting examples from each important tab.
- Map columns in the product’s import review and record any fields that cannot be represented directly.
- Check potential identity matches manually; a same-name result is not enough to merge.
- Hold unresolved identity conflicts outside the upload. Import the cleared sample and reconcile created, merged and skipped outcomes against its source rows.
- Open linked candidates, companies and jobs; test whether a second consultant can understand the status and next action.
- Repeat with a revised map, then approve the wider import only when the exception list has an owner.
Yena’s guide describes uploading spreadsheets, mapping fields, reviewing and importing, with companies, jobs and candidates handled in a deliberate order. Import History records created, merged and skipped results. Basic contact and record imports are distinct from full pipeline, placement and activity history, which may require managed migration. No blanket history import or automatic rollback promise follows from the guide. Read Yena’s migration guide (English) and ask for the exact scope relevant to your workbook.
Choose the cutover only after a readiness check
Keep the original workbook accessible as a read-only reference during the validation period you set. Choose one current mandate and have a consultant perform the routine lookup, update and handover in the new system. Compare the result to the agreed source data, record exceptions and decide which system is authoritative for new work. Avoid parallel edits in both places once the team approves a cutover; otherwise the same conflicts return.
A migration is ready when the team can find a candidate using the criteria it actually relies on, distinguish person-level facts from job-specific status, trace the source of important notes and explain unresolved rows. The team should also know how to request help for records outside self-service import. If those conditions are not met, narrow the first migration or revise the mapping before moving more data.
This process creates a migration decision based on your own records rather than an assumed duration or cost. For related procurement criteria, use the CRM data-model acceptance test.
Worked example: map one workbook before a go/no-go decision
This fictional sample follows one candidate row linked to two mandates. It separates fields that can be mapped directly from relationships and history that need review; it does not assume every column or activity imports.
On a small screen, scroll the table horizontally.
| Workbook field | Target / treatment | Sample check | Decision signal |
|---|---|---|---|
| Candidate name, email, phone | Candidate identity and contact fields | Check one representative and one conflicting identity row | Go only when unresolved matches are held for review |
| Client name | Company record | Confirm spelling resolves to one intended company | Hold aliases that could create duplicate companies |
| Job code and client | Job record linked to company | Open the job and verify the company relationship | No-go if the relationship cannot be resolved |
| Candidate + job + stage | Job-specific pipeline relationship | Check the same person across both mandates | No-go if one stage would overwrite another role's context |
| Last call / owner initials | Dated note or activity; owner needs mapping | Check source, date, author and meaning | Agree a manual treatment if history or user mapping is unclear |
After the sample import, compare the recorded import outcome with your source sample and inspect the linked company, job and candidate records. Give unresolved exceptions an owner and agree which system holds new work before proceeding. Confirm separately whether pipeline, placement or activity history is included.
Yena: spreadsheet migration sequence · Yena: import matching and managed migration
FAQ
Should we clean every spreadsheet before testing an ATS import?
First preserve a read-only original and create a representative copy. Map known fields, isolate ambiguous columns and test typical and exception rows. You can clean in stages after learning how the target handles relationships and conflicts.
Does a candidate CSV import include full pipeline history?
Not necessarily. Candidate, company and job records may have self-service import paths, while full pipeline, placement or activity history may require a managed migration. Confirm scope and test sample records before relying on it.
How do we know whether the new ATS is ready to replace Excel?
Run the same live search and handover in both systems, reconcile import outcomes and confirm that the second user can find the correct records and next steps. Keep the prior file read-only until your team approves the new workflow.
Can a successful sample import prove that all spreadsheet history will transfer?
No. A sample tests the fields and relationships included in that sample. Confirm the scope of pipeline, placement and activity history separately before treating the workbook migration as complete.
Some of our customers
Try it with your team
Prepare a role for a post-import search check
The search setup shows role, region and criteria. After validating the import, check whether your team can find the records it needs for a representative role.
- Set the role
- Choose region
- Review criteria





