Migrate from Martian Logic to Crelate

Martian Logic Employee records map to Crelate Contact records. All personal details (name, email, phone, address, date of birth, emergency contacts), employment history, and ESS access levels migrate as standard and custom Contact fields. We extract the full employee record including effective-dated changes and custom folder contents stored against each employee. Martian Logic custom folder fields (image uploads, file attachments, dropdown selections) that have no direct Crelate equivalent are stored as text values or file-attachment notes linked to the Contact.

Martian Logic Positions have no Crelate equivalent, so we walk the Position hierarchy during extraction and encode the reporting chain as custom fields on the Contact. The direct manager's name becomes a custom Contact field (manager_name__c), the job title from Position becomes the Contact's jobtitle field, and the full position chain (head of department, division head) is stored as a pipe-delimited custom field (position_chain__c). Archived or soft-deleted Positions that create orphaned nodes in the hierarchy are flagged during extraction and presented to the customer for resolution before migration.

Martian Logic ATS Candidates map to Crelate Contact records using the candidate's application data. We extract the full pipeline including status history, application dates, interview scores, and conversion events. If a Martian Logic Candidate has been converted to an Employee, we map the record to the same Contact that received the Employee data and preserve both the pre-hire candidate timeline and the post-hire employment data on one record.

Martian Logic Recruitment Requisitions (hiring requests before a candidate is assigned) map to Crelate Opportunity records. Requesting manager, approved headcount, requisition status, and job description migrate to Opportunity fields. Open requisitions become Open Opportunities; closed filled positions become Closed Won; closed cancelled requisitions become Closed Lost. Crelate's Opportunity record type provides a natural home for the requisition lifecycle.

Onboarding e-form payloads in Martian Logic are stored as JSON per employee, with field names and structure varying by pack configuration. We parse each pack payload individually during extraction and build a custom field mapping per pack rather than applying a universal transform. In Crelate, we create custom fields on Contact matching the parsed e-form fields and use Crelate's Activity Forms feature with field mappings to copy form answers to the Contact record. This preserves the data in the format Crelate expects while honouring the configuration-dependent nature of the source e-forms.

Change of Staff Conditions records in Martian Logic are effective-dated transactions (change type, old value, new value, reason, effective date). We flatten these into a per-employee change log stored as a text custom field on the Contact (employment_changes__c) in chronological order. Crelate's Activity timeline can be used to represent individual change events as Tasks with descriptions, but the change log approach preserves the full audit trail in a single field for reference.

Compensation data in Martian Logic is stored within or linked to Positions via the Role and Remuneration Library (base salary, allowances, pay frequency, award coverage, enterprise agreement data). We extract the current compensation values and map them to Crelate Contact custom fields: base_salary__c, pay_frequency__c, allowances__c. APAC-specific fields like award classification and enterprise agreement terms are stored as text fields if the customer's Crelate instance does not have equivalent structured fields. Note that Crelate does not have a native payroll module; compensation data migrates for reference and reporting purposes only.

Martian Logic's org chart is a derived view of Position relationships rather than a standalone object. We reconstruct the hierarchy by walking the Position-to-Position reporting chain and encode it as custom fields on Contact. The department and cost centre come from the Position record. The customer receives a written org chart inventory documenting every Position, its reporting parent, and its assigned Employee so that the Crelate admin can build the equivalent structure using custom fields, tags, or a third-party org chart integration if needed.

Integration Connectors in Martian Logic push employee data to third-party payroll systems and store field-to-field mapping configurations that do not export from the platform. We document every active connector's source fields, destination system, and mapping during discovery. Crelate has no native payroll push feature; the documented mappings are handed to the customer as a configuration guide so that the equivalent can be rebuilt in the destination payroll system or flagged for a separate integration setup.

Performance Review templates and completed reviews in Martian Logic reference the Performance module which has no equivalent in Crelate's ATS model. We export the review cycle name, template structure, ratings, and goals as a written inventory document. Crelate's Activity Forms can be used to recreate a basic review form, but the full review workflow (goal setting, multi-rater feedback, calibration) requires a purpose-built performance management tool and is documented for the customer to address separately.

Compliance modules in Martian Logic track regulatory requirements and attestations per employee (certifications, police checks, regulatory licences, mandatory training expiry dates). We export compliance status and expiry dates as custom fields on the Crelate Contact (certification_name__c, certification_expiry__c, compliance_status__c). Compliance enforcement logic does not migrate; Crelate has no native compliance automation, so these fields serve as reference data for the customer's admin to manage manually or integrate with a dedicated compliance tool.

Employee Self-Service access levels and role permissions in Martian Logic are stored per employee or per role. We export these as custom text fields on the Crelate Contact (ess_access_level__c, role_name__c). Crelate does not have an ESS module; these fields are migrated for record completeness and do not activate any Crelate access control since Crelate's permission model is role-based at the recruiting workflow level, not the employee self-service level.