Migrate your Apollo ERP data

Employee records in Apollo ERP include standard fields (name, department, designation, joining date) and effective-dated changes. We export the full employment history including role transitions and compensation changes. Standard CSV/API extraction supported on most plans.

Payroll runs are stored as separate transactions linked to employee records. We extract earnings, deductions, taxes, and net pay across all pay periods. Historical payroll is migration-critical for audit and compliance purposes — we preserve the full run detail rather than summary balances.

Leave balances, accrual rules, and transaction history vary significantly by customer configuration. Some deployments use custom leave types or non-standard accrual formulas. We map the leave type names and balance values but flag custom accrual logic for manual review before import to avoid carry-forward errors.

Customer records include contact details, addresses, and classification fields used across CRM and FSM modules. The schema is stable and well-documented in the standard export. We preserve customer-to-work-order associations during migration.

Work orders capture the core FSM workflow: asset details, service type, scheduling, technician assignment, and status. We extract open and closed work orders including line items, parts used, and labor entries. Closed work orders migrate as historical records.

Apollo ERP uses a hierarchical chart of accounts for financial management. Account codes and parent-child relationships must be mapped to the destination system's structure. Custom account types and non-standard numbering schemes require field-level mapping work per the customer's chart design.

Vendor master data includes contact information, payment terms, and tax registration details. We extract the full vendor list and map to the destination's vendor or supplier object. Historical purchase transactions are handled separately as AP records.

Outstanding payables and receivables must be migrated as open items with original invoice dates, amounts, and due dates. We extract the aging detail and map to the destination's AP or AR register. Closed items migrate as historical transactions.

Apollo ERP supports custom fields on most core objects. Custom field definitions and their values require explicit extraction and mapping to destination equivalents. We flag any custom fields that have no matching target and offer a holding-area migration for orphaned values.

Document storage in Apollo ERP is not exposed via a standard exportable API on all plans. We extract metadata (filename, linked object, upload date) but file binary extraction requires a separate technical assessment. Attachments are migrated where direct file access is available.