Migrate from Simplicant to Recruit CRM & ATS

Simplicant Job records map to Recruit CRM Job records with title, description, department, location, and current pipeline stage preserved. We extract the job's published status to set the initial Active/Draft state in Recruit CRM. Department and location metadata transfer as linked records, not flat text fields, so that Recruit CRM's filter and grouping features work immediately after migration.

Simplicant Candidate records map 1:1 to Recruit CRM Candidate profiles, preserving contact details, source attribution, and application date. Stage history from Simplicant's application record migrates as a log of previous pipeline stages on the Candidate timeline. We resolve duplicate candidates by email address before insert to avoid creating duplicate profiles in Recruit CRM.

Simplicant's application (Candidate applied to Job) maps to the Candidate's association with a specific Job in Recruit CRM. Application date, current stage, and stage-entry timestamps preserve on the association record. If a Candidate has applied to multiple Jobs in Simplicant, each application migrates as a separate Candidate-Job association in Recruit CRM.

Simplicant Department records transfer as Department lookup values in Recruit CRM. We map by department name with the original Simplicant department ID preserved in a reference field for reconciliation. This prevents Recruit CRM from creating duplicate departments during job import.

Simplicant Location records attached to Jobs transfer as Location metadata in Recruit CRM. If Simplicant stores address components (city, state, country) as structured fields, we map them to Recruit CRM's location format. Plain-text location strings migrate as-is with a flag for admin review post-migration.

Simplicant's structured interview evaluation forms have varying field names and scoring conventions per organization. We export completed evaluation responses as score records attached to the Candidate. The form schema (field names, weightings, rating scales) migrates as a written field map; Recruit CRM's evaluation setup is manual post-migration. Score data migrates fully; form builder configuration does not.

Simplicant Offer records containing salary, start date, terms, and e-signature status migrate to Recruit CRM Offer records. E-signature audit trails are linked records and may require additional extraction handling depending on whether Simplicant's export includes the signature image or audit metadata. We preserve the offer status (pending, accepted, declined, withdrawn) and attach the offer to the corresponding Candidate-Job association.

Simplicant pipeline stage names and sequences map to Recruit CRM pipeline stages. We extract the stage count and names from Simplicant and configure matching stage values in Recruit CRM before job migration begins. Stage probability percentages and automation rules (auto-advance, rejection triggers) do not migrate as configuration; these require manual rebuild in Recruit CRM's pipeline settings.

Simplicant user accounts (recruiters, hiring managers, interviewers) map to Recruit CRM User records by email address. Role-based access control settings migrate as a written map of role assignments; Recruit CRM's permission groups and access levels are reconfigured manually post-migration since role semantics differ between platforms.

Simplicant onboarding workflow step completion status and assigned task lists migrate as task records attached to the Candidate. Completed onboarding records preserve the status and task list state at time of migration. Active onboarding automation sequences with branching logic do not migrate as workflow code; we deliver a written inventory of the automation logic for the customer's admin to rebuild in Recruit CRM's task management.

Simplicant screening scores and evaluation ratings stored per Candidate per stage migrate to Recruit CRM custom numeric fields on the Candidate profile. Score ranges and weighting logic vary by organization; we export raw score values and map them to a normalized custom field in Recruit CRM. The form or rule that produced the score is documented separately for rebuild.

Simplicant custom fields added to Jobs and Candidate profiles by the organization migrate as Recruit CRM custom fields. We infer field definitions and data types from export results during discovery. Custom field definitions and their associated values transfer; display labels may require minor adjustment to match Recruit CRM's field editor conventions. Any field that references a Simplicant-only picklist value gets a manual value map created during scoping.