Migrate from Martian Logic to Recruit CRM & ATS

Martian Logic ATS candidates map directly to Recruit CRM candidate records. We extract full name, email, phone, location, work authorization status, status in pipeline, application date, source channel, and interview scores. The candidate status stages from Martian Logic map to Recruit CRM pipeline stages by reviewing the customer's active workflow configuration during discovery. Any rating or score field migrates as a custom numeric field in Recruit CRM.

Martian Logic Positions (job vacancies attached to the position-budget model) map to Recruit CRM Job records. We extract job title, department, location, employment type, and hiring manager from the Position object. The position hierarchy (Position-to-Position reporting chain) has no Recruit CRM equivalent, so we document reporting relationships as custom fields on the Job record rather than attempting a structural org chart migration.

Martian Logic Request-to-Recruit workflow records (requisition, approval chain, headcount approval) do not have a direct equivalent in Recruit CRM. We extract open and closed requisitions with status, requesting manager, and approved headcount as custom fields on the corresponding Job record. Approval chain logic must be rebuilt manually in Recruit CRM's workflow builder post-migration.

Martian Logic Employee records do not map to a standard Recruit CRM object because Recruit CRM is an ATS, not an HRIS. For customers using Martian Logic's ATS module who also have active employee records, we filter the Employee Database to identify individuals who are not active job applicants, then migrate them as inactive or archived candidate records in Recruit CRM with a status field indicating their employment state.

E-form payloads in Martian Logic are configuration-dependent JSON blobs with no fixed schema. Each pack configuration produces a different field name set, data types, and mandatory/optional status. We parse every distinct e-form payload individually during extraction and map each field to a Recruit CRM custom field on the Candidate record. If a candidate has completed multiple onboarding packs, we concatenate the payloads into a structured set of custom fields rather than a flat list.

The Martian Logic org chart is a derived view of the Position hierarchy rather than a standalone object. We reconstruct it by walking the Position-to-Position reporting chain. Since Recruit CRM has no org chart object, we create a department custom field on Job and a reporting_manager custom field on Candidate, populating these from the traversed position hierarchy. Archived or soft-deleted positions create orphaned nodes that we flag for cleanup before export.

Martian Logic compensation records linked to Positions (base salary, allowances, pay frequency from the Role and Remuneration Library) have no standard equivalent in Recruit CRM's ATS model. We extract the most recent compensation snapshot as a set of custom fields on the Candidate record: expected_salary, pay_frequency, and allowance fields. Compensation history is not migrated in full as Recruit CRM does not support the effective-dated compensation record model.

Martian Logic Change of Staff Conditions records (effective-dated transactions recording type of change, old value, new value, reason) do not have an equivalent in Recruit CRM. We extract the employment change log as a flat timeline stored in a custom long-text field on the Candidate record. The customer's HR admin reviews and rebuilds the active change-tracking workflow in Recruit CRM's automation builder if required.

Martian Logic Integration Connector field mappings (source-to-destination field maps for payroll push) are configuration artefacts that cannot be exported from the platform. We document every active connector's mapping during discovery, noting source fields, destination fields, and transformation rules. The customer must manually re-establish these mappings in their target payroll system post-migration. This object does not migrate — it is documented for rebuild.

Martian Logic Performance Review templates and completed reviews have no equivalent in Recruit CRM's ATS model. We extract review cycle names, template structures, ratings, and goals as a custom structured field on the Candidate or as a separate PDF document linked to the candidate record. The review rebuild falls outside Recruit CRM's ATS scope and must be handled as a separate HR tool decision post-migration.