Migrate from Asanify to BambooHR

Asanify Employee records map directly to BambooHR Employee records. We extract name fields, contact information, employment dates, department, job title, employment status, and reporting manager. Custom employee properties on Asanify (including any India-specific fields not covered by statutory export) map to BambooHR custom fields created during schema design. EOR-flagged employees receive an additional custom field label_eor__c and country_of_employment__c to preserve the employer-of-record relationship for compliance review.

Asanify's org chart and department hierarchy map to BambooHR Departments and the reporting manager reference on each Employee record. We export the full org tree as a parent-child department list and resolve each employee's department and manager assignment during the employee import phase. BambooHR's native organizational chart feature renders this data post-migration without additional configuration.

Asanify salary revision history (effective date, previous salary, new salary, revision reason) maps to a combination of BambooHR's standard pay fields and a custom compensation_history__c text field storing the revision log as JSON. Current salary components (base, allowances, deductions) map to BambooHR pay fields or custom pay component fields depending on plan tier. We do not replicate Asanify's payroll run engine; historical pay data serves as a record, not a live payroll feed.

Asanify leave types and current accrual balances map to BambooHR Time Off types and balances. We extract accrual rates, carry-forward amounts, and leave policy rules from Asanify and configure equivalent BambooHR Time Off policies before balance import. Asanify's India-specific leave types (for example, sick leave under state-specific rules) map to the closest BambooHR equivalent or a custom leave type. BambooHR's separate payroll module does not share leave balance data, so no payroll-side reconciliation is required at this layer.

Asanify attendance logs (punch records with timestamps and geo-coordinates) map to BambooHR Time Tracking if the customer purchases the Time Tracking module, or to a custom text field storing punch-in and punch-out timestamps. BambooHR has no native geo-tracking field. We export geo-coordinates from Asanify as a custom location__c text field and flag any records where coordinates are absent due to mobile app non-use. Biometric device flags (VIP-only in Asanify) do not map to any BambooHR native field and are flagged for manual review.

Asanify payroll runs and payslip records (earnings breakdown, TDS deduction, PF deduction, ESIC deduction, Professional Tax, net pay) cannot migrate into BambooHR's standard payroll module because BambooHR Payroll is a separate product. We export payslip records as a structured dataset and store the last 12 months of pay data as a custom payslip_history__c JSON field per employee. India statutory deductions (TDS, PF, ESIC, PT) are preserved as labeled line items within this field. The customer must configure BambooHR Payroll separately or continue payroll in another India-compliant tool.

Asanify performance review cycles, ratings, and free-text feedback (VIP-tier) map to BambooHR's Performance Management module if the customer is on Pro or Elite, or to a set of custom fields (review_cycle__c, rating__c, feedback__c) if on Core. Custom question banks require manual field mapping during schema design. We export the review cycle name, reviewer, reviewee, rating score, and full text feedback and map them to the corresponding BambooHR structure. If the destination BambooHR plan does not include Performance Management, we flag this gap during scoping.

Asanify OKR records (company-level objectives, individual key results, progress percentages, status) are VIP-tier and do not have a native BambooHR equivalent. We flatten each OKR into a custom key_result__c text field storing the objective, key results list, current progress percentage, and status label. BambooHR's Performance Management module on Pro and Elite includes a goal-tracking feature; if the customer activates this, we map the flattened records to the native goal structure. Otherwise they remain in custom fields as a historical record.

Asanify contractor records are stored in a separate module with contract terms, invoicing details, multi-currency payout rates, and contractor status. BambooHR has no separate contractor module. We split each Asanify contractor into a BambooHR Employee record with a custom field contractor__c set to true and contract_terms__c storing the contract duration and rate. Multi-currency invoicing data does not map to any BambooHR field and is preserved in a custom text field for the customer's accounting team to reconcile.

Asanify EOR records represent employees legally employed by Asanify's employer-of-record entity in a specific country, not by the customer's company directly. BambooHR has no native EOR function. We migrate each EOR employee as a BambooHR Employee record with three custom fields: label_eor__c (true), eor_employer_entity__c (the Asanify legal entity name), and country_of_employment__c (ISO country code). These fields preserve the employer-of-record relationship so the customer's legal and HR teams can audit the data post-migration and determine whether to maintain EOR status through a new provider or establish a direct legal entity.

Asanify expense reimbursement records (amount, category, approval status, submission date) map to BambooHR's Expense module on Pro and Elite plans. Pending reimbursements require explicit customer action before the final export because deprovisioning Asanify may orphan unresolved requests. We export pending reimbursements as a separate reconciliation report during the pre-migration review meeting and recommend resolving all open requests (approve or reject) before the cutover date. Approved reimbursements migrate to BambooHR Expense records; rejected requests are logged in the reconciliation report without import.

Asanify employment documents (offer letters, contracts, ID copies, certificates) stored on VIP and Enterprise tiers migrate to BambooHR Employee Files if the destination plan includes document storage, or to a separate document archive provided by FlitStack AI for records that cannot attach to BambooHR's employee file system. Document file types are mapped to BambooHR file categories during export. We export what the UI exposes; password-protected or encrypted documents that cannot be read by the export process are flagged and handed off as a separate file inventory.