Migrate your CREST ERP data

Customer master records include contact details, addresses, credit limits, and payment terms. We map these 1:1 to the destination's customer or account object, preserving any custom properties attached at the customer level.

Vendor master records hold supplier details, bank information, and performance ratings. We migrate vendor data with all associated purchase terms, maintaining the vendor-supplied catalogue where applicable.

Item masters carry SKU, description, pricing, UOM, and optionally BOM and routing data. The manufacturing module's BOM structures require careful mapping—multi-level parent-child relationships and work-in-progress item types need explicit handling during migration scoping.

The chart of accounts maps cleanly to the destination's GL structure. We preserve account codes, names, account types, and cost center assignments. Intercompany account mappings are reviewed during the pre-migration data audit.

Open AP records migrate with vendor association, invoice number, amount, due date, and current payment status. We track which invoices remain open at migration cutover to avoid re-importing satisfied liabilities.

Open AR records preserve customer association, invoice number, amount outstanding, and aging bucket. We flag credit memos and partial payments for correct offset handling in the destination system.

Historical records span GL journal entries, inventory movements, production transactions, and time entries. Multi-year histories carry significant volume; we chunk these into manageable migration batches and validate totals against trial balance reports from both systems.

Fixed asset records include acquisition cost, depreciation schedule, asset category, location, and maintenance history. We map depreciation methods and generate asset requirement records during the migration phase to maintain asset continuity.

Employee records include personal details, job role, compensation history, PTO balances, and attendance data. Effective-dated compensation records require sequencing to preserve historical pay period accuracy at the destination.

Department structure maps to the destination's organizational hierarchy with department codes, names, and parent-child relationships. We validate that cost center assignments on GL accounts align with the migrated department tree.

HR records include leave applications, approvals, leave balances, and attendance logs. Custom leave policies and approval workflows may require field-level mapping review and manual recustomization at the destination.

Sales orders carry customer association, line items, quantities, pricing, delivery dates, and order fulfillment status. SFA pipeline stages map to the destination's opportunity or deal stages, with attention to any custom stage-specific fields.

Purchase orders include vendor linkage, line items, quantities, pricing, expected delivery dates, and receipt status. Approval workflows configured in CREST ERP require documentation review for equivalent workflow setup at the destination.

Project records contain budget, resource assignments, tasks, milestones, and time entries. CREST ERP's project management module uses configurable project templates that may require re-creation or manual mapping to the destination's project structure.