Migrate your ERPnext Enterprise - Bespoke data

Standard DocType with fields for name, territory, territory hierarchy, contact details, and tax ID. Mapped 1:1 in most migrations. We validate territory linkage to ensure downstream reporting is preserved.

Mirrors the Customer DocType structure. We migrate supplier type, payment terms, and address records. Supplier-specific tax categories are carried forward as Custom Fields on the Supplier DocType.

Items carry a large attribute set — item code, description, item group, stock uom, valuation method, and barcodes. We preserve the full item master including barcodes and custom fields at the item level.

BOMs are nested structures referencing Items with quantity ratios and operation routing. We map BOM hierarchies directly but validate that all child item codes exist in the target before committing to avoid orphan references.

Sales Orders contain line items, taxes, discounts, and shipping details. We map the document header and all child rows, preserving the qty-delta logic against Delivery Notes when migrating open orders to a new system.

Purchase Orders mirror Sales Orders in structure. We migrate PO headers and line items, flagging any advance allocation records that require separate handling as Payment Entries.

ERPNext uses a voucher-based double-entry system. We map journal entry rows to account codes but validate that the target chart of accounts has matching account numbers, which frequently requires pre-migration account mapping work.

Stock movement records link to warehouse, item, and valuation rate. We migrate SLEs as-is for open stock positions; historical movement logs require bulk CSV export and transformation as the API does not surface a bulk-read endpoint.

Projects carry a nested task hierarchy with assignees, start/end dates, and billable hours. We map the full project-task tree including custom task fields and hourly rate settings.

ERPNext user records include email, name, enabled status, and role profiles. We map enabled users and their role assignments; role permission rules are exported as configuration and reapplied on the destination.

Custom Fields attach to any DocType via the Custom Field DocType. We export all custom field definitions separately and apply them on the destination before importing data so that target fields exist at import time.

Fixed Asset records include purchase details, depreciation schedule, and current value. We map asset masters and depreciation schedules, skipping any already-depreciated-to-zero assets unless the customer specifically requests historical depreciation logs.

The HR module exposes Employee DocTypes with employment details, department, and reporting structure. We migrate active employees and current compensation records; payroll history and historical salary revisions are mapped as Compensation Structures when supported by the destination.

ERPNext stores contacts and addresses as separate DocTypes linked by Dynamic Links. We resolve these relationships during export to produce flat contact records with embedded address data compatible with most destination CRMs.