Migrate your FACT ERP.NG data

Customer records in FACT ERP.NG carry addresses, contact details, GST/Tax IDs, credit limits, and payment terms. All standard fields are stable and we migrate them 1:1. We preserve Customer-to-Sales-Order and Customer-to-AR-invoice linkages during the load sequence.

Supplier master records include bank details, tax registration, and payment terms. We map them to the destination's Vendor or Supplier object. We retain Supplier-to-Purchase-Order and Supplier-to-AP-invoice linkages as cross-object references.

Items carry pricing, BOM (Bill of Materials) links, serial number flags, and barcode data. For manufacturing configurations we also capture multi-level BOM structures. We chunk BOM rows individually and reassemble them at the destination.

Sales Orders carry customer references, line items, pricing, taxes, and fulfillment status. We map each order header and its lines as a single transactional unit so that partial fulfillments are correctly represented at the destination.

Purchase Orders carry supplier references, line items, expected delivery dates, and GRN (Goods Received Note) linkages. We preserve the header-to-line structure and flag any open versus closed PO status at migration time.

FACT ERP.NG uses a standard COA structure with account codes, descriptions, and account types. We map account codes directly and flag any account that carries a balance so that opening balances are posted correctly at the destination.

FACT ERP.NG posts payroll, AR, and AP directly to the GL via journal entries. These are date-stamped, source-referenced records. We extract them in date-range batches and map them to the destination's GL journal or transaction object, handling currency and tax code differences during transformation.

Inventory balances are maintained per warehouse per item. We migrate current stock positions, reorder levels, and warehouse assignments. Serial and batch tracking fields require value-level mapping since destination systems use different naming conventions for tracking attributes.

Fixed Asset records include acquisition cost, depreciation method, accumulated depreciation, and asset location. Depreciation schedules are generated per accounting period. We map asset registers and capture the depreciation method as a configuration field so the destination can regenerate schedules.

Employee records include salary components, tax deductions, EPF/CPF contributions, and leave balances. Payroll in FACT ERP.NG posts directly to the GL, creating a dependency chain we must resolve before loading GL data. We extract employees, salary history, and payroll journal postings as a single migration package.

The CRM module holds Leads, Contacts, Opportunities, and Activities. We migrate all four as linked objects preserving the contact-to-opportunity relationship. Opportunity stage and owner assignment are carried across as custom properties if the destination uses a different pipeline model.

FACT ERP.NG supports Malaysian e-invoicing (IRB/LHDN) and Singapore InvoiceNow. We migrate e-invoice metadata and XML payloads. The destination system must have an equivalent compliance module or the records will be stored as attachments.

The CXO Control Tower dashboards are visual configurations built within FACT ERP.NG's proprietary layer. These are not exportable as structured data. We do not migrate dashboards. Customers should treat dashboards as read-only references and rebuild them in the destination BI tool.

FACT ERP.NG's Configuration Only model means many settings are stored as parameters rather than custom fields. We extract parameter values and map them to equivalent configuration fields or custom fields at the destination, documenting every parameter that has no direct equivalent.