Migrate your Pilot ERP data

Customer records in Pilot ERP map directly to the standard Customers object in most target ERPs. The CRM module stores contact details, company associations, and lifecycle information. We preserve the full contact history and ownership assignment during migration.

Vendor master data is fully structured in Pilot ERP with standard address, payment, and terms fields. We migrate all vendor records and link any outstanding Bills to the corresponding vendor at import time.

Items include part numbers, descriptions, costing methods, and current stock levels. The barcode-labelled inventory is linked to Items by part number. We verify every barcode-labelled record resolves to a valid Item before importing stock quantities to avoid orphan inventory entries.

Work Orders track manufacturing jobs from creation through completion. Each Work Order links to Items for the finished good and optionally to associated Purchase Orders for raw materials. We preserve the full parent-child chain during migration.

Purchase Orders are created against Vendors and Items. We capture open PO status and flag any Work Orders still referencing closed or partially received Purchase Orders so the customer can resolve the link before go-live.

Invoices are linked to Customers and Items. We import open invoices with their payment status and remaining balance. Historical paid invoices are migrated with full line-item detail for audit trail completeness.

Bills from Vendors are imported with outstanding balance and payment terms. We maintain the relationship to the originating Vendor record and preserve any partial-payment history.

Pilot ERP's Job Costing module tracks material, labor, and overhead per job or Work Order. Target systems may represent job cost components differently — as line items, as separate cost objects, or as custom fields. We map the cost breakdown into the destination's equivalent structure and flag any costing categories that require custom field creation.

Pilot ERP maintains a chart of accounts used across all financial modules. We extract the full account structure and map it to the destination's chart, flagging accounts with transactions that do not exist in the target template.

Pilot ERP's user manual references document attachment capability but does not expose a documented public API endpoint for binary file export. We cannot programmatically extract attachments without a private API or direct database access, which is outside the standard migration scope.

Pilot ERP supports user-defined custom fields on standard objects, but there is no documented schema for custom field definitions in public-facing API documentation. We inventory custom fields during discovery and create corresponding custom properties in the target system before importing data.