Migrate from Sympa to Recruit CRM & ATS

Sympa's recruitment module stores applicants as Employee records with a recruitment-specific status field. We map these to Recruit CRM Candidate records, preserving name fields, contact information, email, phone, current title, and source attribution. Active versus terminated status on the Sympa Employee record maps to Candidate status values in Recruit CRM. If Sympa stores candidates with an application history tied to specific job requisitions, we map those to Recruit CRM Job records and track the application against the correct pipeline stage.

Sympa Employee records that represent external candidates, contractors, or alumni of the client's organization map to Recruit CRM Contact records. Contact type and relationship fields in Recruit CRM distinguish these from direct candidate applications. This mapping applies when Sympa is used for talent pipelining beyond active recruitment.

Sympa organizational units that represent client organizations map to Recruit CRM Company records. We preserve company name, website, industry, address, and size information where present. Parent-child relationships in Sympa's org structure that represent client hierarchies map to Recruit CRM's Company hierarchy if the customer's Recruit CRM plan supports it.

Sympa's recruitment module stores open positions as Job Requisition or Vacancy records. We map these to Recruit CRM Job records, preserving job title, department, location, employment type (full-time, contract, part-time), and job description. Active versus closed status on the Sympa requisition maps to Job status in Recruit CRM.

Sympa records of successful placements or hires map to Recruit CRM Deal records. The placement fee or margin stored in Sympa maps to Deal value in Recruit CRM. Placement status (candidate accepted, start date confirmed) maps to Deal stage. If Sympa tracks client invoice lines attached to a placement, those map to Deal products or line items in Recruit CRM.

Sympa custom fields on Employee records (which may include skills, certifications, clearance levels, source channels, or screening results) require a pre-migration audit during scoping because Sympa does not publish a standard field catalog. We extract the full custom field inventory from the customer's Sympa instance, cross-reference each against Recruit CRM's available custom field types (text, number, date, picklist, checkbox, multi-select), and apply explicit transformations for any that lack a direct equivalent. Recruit CRM supports custom fields via its Custom Fields API endpoint, so we provision these before data import.

Sympa stores org units with parent-child relationships representing reporting lines, departments, and cost centers. Recruit CRM has no organizational hierarchy or reporting structure object. We cannot migrate the org chart as structured data. We offer two options: document the hierarchy as a CSV for the customer's HR team to re-enter manually, or export the data into a separate HR reporting tool post-migration. We flag this gap during scoping and confirm the customer's preference before production migration.

Sympa tracks effective-dated salary, bonus, commission, and equity entries per Employee. Recruit CRM has no compensation object and does not store historical salary data. We export compensation records as a dated CSV with employee identifier, effective date, compensation type, and amount for the customer's HR team or payroll admin to handle separately. We do not attempt to map compensation data into a Recruit CRM field because no equivalent exists.

Sympa tracks accrued leave balances and leave request history by type (annual, sick, parental). Recruit CRM has no leave management or PTO tracking capability. Time-off data does not migrate. We export current balance snapshots as a CSV for the customer's HR team to re-enter into their chosen HR system post-migration. We flag during scoping whether the customer needs a parallel HR platform to replace Sympa's leave management.

Sympa stores effective-dated employment events including job title changes, department transfers, manager updates, and promotion records. Recruit CRM has no employment history object. We export the full employment event timeline as a dated CSV with employee identifier, event date, event type, and affected fields for the customer's records. We flag this during scoping and confirm whether the customer's HR team needs this data re-entered into a replacement HR system.

Sympa Employee records may have attached documents such as signed contracts, compliance certifications, or onboarding paperwork. We map these file attachments to Recruit CRM Files linked to the corresponding Candidate or Job record. We preserve the original filename, file type, and upload date. Recruit CRM stores files via its Files API and attaches them via ContentDocumentLink. We confirm file size limits with the customer's Recruit CRM plan before migrating large document archives.