Migrate from Asanify to Recruit CRM & ATS

Asanify Employee records are the primary migration object when re-purposing the ATS module for recruitment use. Core fields (name, email, phone, department, employment status, start date) map to Recruit CRM Candidate fields. Employment dates become work history start and end dates. Salary revision history becomes a Compensation sub-record on the candidate, though Recruit CRM does not natively support structured compensation history, so we map the most recent salary to a custom field and flag salary ranges that require manual entry. Active vs inactive employment status maps to Candidate status in Recruit CRM. Employees with no recruitment-relevant history (pure payroll records) are excluded from the ATS migration scope and inventoried separately.

Asanify department assignments and org chart hierarchy map to Recruit CRM Organizations. The full org tree is preserved as a parent-child organization hierarchy in Recruit CRM. Department head names and reporting relationships map to Organization contact roles rather than as standalone fields. If the org structure is deep (more than 4 levels), we flatten it to a two-level hierarchy in Recruit CRM and note the full depth in a custom field for admin reference.

If Asanify's ATS module exposes job posting records, they map directly to Recruit CRM Job records. Job title, description, requirements, location, employment type, and salary range migrate to the equivalent Recruit CRM fields. Job status (open, closed, on hold) maps to Recruit CRM Job status. Any custom job fields from Asanify map to Recruit CRM Job custom fields. If Asanify's ATS module does not expose a standalone Job object, we create Job records from the context of active candidate application records.

Asanify candidate-to-job application records map to Recruit CRM Application records linked to the Candidate and Job. Application stage, submission date, source, and referred-by fields migrate to the equivalent Recruit CRM Application fields. Stage history (application moving through interview rounds) maps to Recruit CRM application stage values, and the stage transition timestamps are preserved. Multiple applications per candidate (re-applications or cross-job submissions) are migrated as separate Application records.

Asanify Contractor records (billed at $18/contractor/month separately) map to Recruit CRM Candidates with a contractor_type or engagement_type custom field set to indicate the contractor relationship. Contract terms, invoicing frequency, and multi-currency payment details migrate to custom fields on the Candidate record. Ongoing active contracts are flagged as open assignments in Recruit CRM. Contractor records do not become Employees in Recruit CRM because Recruit CRM has no HRMS payroll layer.

Asanify payroll runs, payslip records, TDS deductions, PF contributions, ESIC deductions, and professional tax deductions have no equivalent schema in Recruit CRM. These records are inventoried as a CSV export during the pre-migration review and handed off to the customer for retention in Asanify or archival storage. We do not load payroll or statutory deduction data into Recruit CRM because there is no payroll module, no payslip object, and no TDS/PF/ESIC field structure in the destination platform.

Leave balances, accrual states, attendance logs with geo-tracking coordinates, and shift schedules from Asanify do not map to any Recruit CRM object. Recruit CRM has no leave management, attendance tracking, or shift scheduling module. These records are excluded from the migration scope and inventoried separately as a structured CSV export. We recommend the customer retains Asanify access or exports these records to a dedicated HRMS for ongoing compliance needs.

Performance review cycles, 360-degree feedback ratings, OKR goal records, key results, progress percentages, and KPI tracker values are not available in Recruit CRM. These VIP-tier objects are excluded from migration and inventoried as a written handoff. Candidates with performance history in Asanify can have a free-text summary note added to their Recruit CRM Candidate record as a custom field, but structured review data, ratings, and OKR progress cannot be preserved as records in the destination platform.

Asanify EOR records represent employees legally employed through an Asanify-owned entity in a specific country. Migrating these records to Recruit CRM—which has no EOR module and no employer-of-record schema—would strip the EOR relationship and create compliance risk. Every EOR assignment is flagged during scoping, labeled with the employer entity and country of legal employment, and excluded from the migration scope. The customer should retain Asanify for EOR employee management or engage a dedicated EOR provider post-migration.

Employee documents (offer letters, contracts, identification records) accessible via the Asanify UI migrate as file attachments linked to the corresponding Candidate record in Recruit CRM. We export the file and map the file type to a Recruit CRM document category. Documents tied to payroll compliance (Form 16, pay-slips, statutory certificates) are excluded because Recruit CRM has no payroll document schema. Document access requires an active Asanify account at the VIP tier where document storage is available.