ERP migration
Field-level mapping, validation, and rollback between FACT ERP.NG and Microsoft Dynamics 365 Business Central. We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Business Central.
FACT ERP.NG
Source
Microsoft Dynamics 365 Business Central
Destination
Compatibility
12 of 13
objects map 1:1 between FACT ERP.NG and Microsoft Dynamics 365 Business Central.
Complexity
BStandard
Timeline
6-10 weeks
Overview
Moving from FACT ERP.NG to Microsoft Dynamics 365 is a full-ERP migration with a mandatory Payroll-to-General-Ledger sequencing dependency. FACT ERP.NG posts payroll journal entries directly to the GL at the moment of payroll run, which means we must load Payroll first, extract the resulting GL journal postings, and then load the Financials module in a second pass. Loading GL before Payroll creates duplicate postings or orphaned debit-credit pairs in the destination. FACT ERP.NG's Configuration Only model stores pricing tiers, tax rates, approval thresholds, and inventory matrix settings as platform parameters rather than custom fields — we treat every non-default parameter as a configuration record that must be extracted, mapped, and replayed in the destination. The platform has no publicly documented REST or GraphQL API, so extraction relies on direct database access where available and on FACT export utilities for file-based approaches. We do not migrate workflows, automations, e-invoice compliance payloads as executable records, or the CXO Control Tower dashboard configurations. These are delivered as written rebuild guides for the destination admin.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Source platform
FACT ERP.NG platform overview
Scorecard, SWOT, gotchas, and pricing for FACT ERP.NG.
Destination platform
Microsoft Dynamics 365 Business Central platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Business Central.
Data migration guide
The complete Dynamics 365 Business Central migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Dynamics 365 Business Central migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Business Central.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a FACT ERP.NG object lands in Microsoft Dynamics 365 Business Central, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
FACT ERP.NG
Customer
Microsoft Dynamics 365 Business Central
Customer
1:1FACT ERP.NG Customer records (addresses, contact details, GST/Tax IDs, credit limits, payment terms) map directly to Dynamics 365 Business Central Customer or Dynamics 365 Finance Customer. The Customer Posting Group from FACT maps to the Customer Posting Group in Dynamics 365. We preserve Customer-to-Sales-Order linkage as a lookback reference. Currency and payment term codes are mapped to their Dynamics 365 equivalents during the transform phase.
FACT ERP.NG
Supplier
Microsoft Dynamics 365 Business Central
Vendor
1:1FACT ERP.NG Supplier records (bank details, tax registration, payment terms, GL vendor codes) map to Dynamics 365 Vendor. Supplier Posting Group, Payment Terms, and Vendor Invoice Portal settings migrate as configuration fields. We retain Supplier-to-Purchase-Order and Supplier-to-AP-invoice linkages as reconciliation references.
FACT ERP.NG
Item / Product
Microsoft Dynamics 365 Business Central
Item
1:1FACT ERP.NG Items carry pricing, BOM links, serial number flags, and barcode data. We map Items to Dynamics 365 Item records with the appropriate Item Type (Inventory, Service, Non-Inventory). Multi-level BOM structures are extracted as a tree and replayed as Dynamics 365 Manufacturing BOM and Routing records if the destination is Business Central Premium or Dynamics 365 Supply Chain Management. Serial and batch number flags map to Item Tracking Code configurations in the destination.
FACT ERP.NG
Sales Order
Microsoft Dynamics 365 Business Central
Sales Order
1:1FACT ERP.NG Sales Orders carry customer references, line items, pricing, taxes, and fulfillment status. We preserve each order header and its lines as a single transactional unit so that partial fulfillments are correctly represented. Sales Order status (open, shipped, invoiced, cancelled) maps to the corresponding Microsoft Dynamics 365 Sales Order status. Header discount and line discount values transfer to Dynamics 365's discount mechanism.
FACT ERP.NG
Purchase Order
Microsoft Dynamics 365 Business Central
Purchase Order
1:1FACT ERP.NG Purchase Orders carry supplier references, line items, expected delivery dates, and GRN linkages. We preserve header-to-line structure and flag open versus closed PO status. GRN (Goods Received Note) linkages map to Dynamics 365 Item Receipt records linked to the Purchase Order. Purchase Order status migrates to the Dynamics 365 corresponding status value.
FACT ERP.NG
GL Account / Chart of Accounts
Microsoft Dynamics 365 Business Central
G/L Account
1:1FACT ERP.NG COA account codes, descriptions, and account types map to Dynamics 365 G/L Account. Account codes that carry a balance (trial balance accounts) are identified during discovery and their opening balances are posted to the destination as General Journal lines before transactional migration begins. We flag any account that has been deactivated in FACT to prevent re-activation in Dynamics 365 without admin confirmation.
FACT ERP.NG
Journal Entries / Transactions
Microsoft Dynamics 365 Business Central
G/L Entry
1:1FACT ERP.NG posts journal entries from AR, AP, and Payroll directly to the GL as dated, source-referenced records. We extract journal entries in date-range batches, map them to Dynamics 365 G/L Entry records, and load them after the Chart of Accounts and Opening Balances are confirmed. We preserve the source document reference (document number and source application) as the G/L Entry's External Document No. for audit traceability.
FACT ERP.NG
Payroll / Employee
Microsoft Dynamics 365 Business Central
Employee / Worker
1:1FACT ERP.NG Employee records include salary components, tax deductions, EPF/CPF contributions, and leave balances. These map to Dynamics 365 Human Resources Employee or Business Central Worker records. EPF/CPF deduction codes map to the destination's Statutory Deduction configurations. We note that Payroll-to-GL sequencing is mandatory: Payroll must be loaded before GL journal entries that reference payroll postings are loaded.
FACT ERP.NG
Inventory / Warehouse
Microsoft Dynamics 365 Business Central
Item Ledger Entry + Warehouse
1:1FACT ERP.NG inventory balances are maintained per warehouse per item. We migrate current stock positions, reorder levels, and warehouse assignments as Item Ledger Entry open quantities and Warehouse entries. Serial and batch tracking values require value-level mapping because Dynamics 365 stores item tracking at the transaction level. We flag any negative inventory positions for admin review before loading.
FACT ERP.NG
Fixed Assets
Microsoft Dynamics 365 Business Central
Fixed Asset
1:1FACT ERP.NG Fixed Asset records include acquisition cost, depreciation method, accumulated depreciation, and asset location. Depreciation schedules are extracted and replayed as Dynamics 365 Fixed Asset Depreciation Books with the corresponding method (Straight-Line, Declining Balance, Unit-of-Production). Asset-to-GL account linkage is preserved through the Fixed Asset G/L Account mapping.
FACT ERP.NG
CRM / Leads / Contacts
Microsoft Dynamics 365 Business Central
Contact / Lead
1:1FACT ERP.NG CRM holds Leads, Contacts, Opportunities, and Activities. We migrate Leads to Dynamics 365 Lead, Contacts to Contact (attached to an Account), and Opportunities to Opportunity with stage and owner assignment preserved. The contact-to-opportunity relationship is maintained by resolving Account lookups at migration time. Opportunity stage values map to the destination Sales Process stage whitelist configured during schema setup.
FACT ERP.NG
Configuration Parameters
Microsoft Dynamics 365 Business Central
General Ledger Setup, Sales & Receivables Setup, Purchases & Payables Setup, Inventory Setup
lossyFACT ERP.NG's Configuration Only model means pricing tiers, tax rates, approval workflow thresholds, inventory matrix settings, and currency precision are stored as platform parameters rather than user-defined fields. We extract every non-default parameter during discovery, map each to its equivalent setup table in Dynamics 365 (e.g., Sales & Receivables Setup, General Ledger Setup), and generate a configuration-replay script as part of the migration package. If parameters are skipped, the destination system runs with default values, causing incorrect pricing tiers, tax rates, and approval workflows in production.
FACT ERP.NG
E-Invoice Records
Microsoft Dynamics 365 Business Central
E-Document / Electronic Document
1:1FACT ERP.NG supports Malaysian e-invoicing (LHDN/IRB) and Singapore InvoiceNow. We migrate e-invoice metadata (invoice number, timestamp, tax values, buyer-seller details) and XML payloads where the source format is accessible. Dynamics 365 Business Central and Finance do not include native e-invoicing for Malaysia or Singapore as standard features; this requires an ISV add-on or separate compliance configuration post-migration. We flag this as a rebuild item for the destination admin and provide the e-invoice metadata as a reference dataset for the compliance module configuration.
| FACT ERP.NG | Microsoft Dynamics 365 Business Central | Compatibility | |
|---|---|---|---|
| Customer | Customer1:1 | Fully supported | |
| Supplier | Vendor1:1 | Fully supported | |
| Item / Product | Item1:1 | Fully supported | |
| Sales Order | Sales Order1:1 | Fully supported | |
| Purchase Order | Purchase Order1:1 | Fully supported | |
| GL Account / Chart of Accounts | G/L Account1:1 | Fully supported | |
| Journal Entries / Transactions | G/L Entry1:1 | Mapping required | |
| Payroll / Employee | Employee / Worker1:1 | Fully supported | |
| Inventory / Warehouse | Item Ledger Entry + Warehouse1:1 | Mapping required | |
| Fixed Assets | Fixed Asset1:1 | Mapping required | |
| CRM / Leads / Contacts | Contact / Lead1:1 | Fully supported | |
| Configuration Parameters | General Ledger Setup, Sales & Receivables Setup, Purchases & Payables Setup, Inventory Setuplossy | Fully supported | |
| E-Invoice Records | E-Document / Electronic Document1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
FACT ERP.NG gotchas
Configuration parameters must be mapped as first-class migration objects
Payroll journal entries create a mandatory sequencing dependency with the GL
Slow report rendering can extend migration validation cycles
No publicly documented API for direct programmatic extraction
Dashboard configurations are not exportable data objects
Microsoft Dynamics 365 Business Central gotchas
Named-user licensing has no concurrent-use relief
API rate limits throttle large-volume migrations
Historical posted transactions require selective migration scoping
NAV-to-Business Central cloud migration requires partner coordination
Custom fields and AL extensions require separate migration handling
Pair-specific challenges
Migration approach
Discovery and extraction method confirmation
We audit FACT ERP.NG across all active modules (Financials, CRM, Inventory, Payroll, Manufacturing, Fixed Assets) and confirm whether direct database access is available or whether extraction relies on FACT export utilities. We document every active non-default configuration parameter, inter-module dependency chain (particularly the Payroll-to-GL linkage), active e-invoice compliance records, and the full COA structure including accounts with balances. We pair this with a Dynamics 365 edition recommendation: Business Central Essentials ($80/user/mo) covers financial and basic supply chain scope; Business Central Premium adds manufacturing; Dynamics 365 Finance addresses larger financial management requirements with deeper dimensional reporting.
Source schema extraction and transformation design
We extract the FACT ERP.NG schema including all master data tables, transaction tables, parameter settings, and configuration values. We design the transformation scripts that map FACT field names and data types to Dynamics 365 equivalents. This includes the Chart of Accounts structure (flat numeric codes in FACT to structured G/L Account format in Dynamics 365), the Payroll-to-GL sequencing rule, the configuration-parameter-to-setup-table mapping, and the BOM hierarchy flattening for multi-level manufacturing records.
Destination schema provisioning in Sandbox
We provision the target Dynamics 365 environment (Sandbox first, Full Copy or Partial Copy depending on data volume) and configure the COA, Posting Groups, Number Series, and setup tables to match the migrated configuration parameters. We create the Customer and Vendor posting groups, the Inventory posting group, and the Fixed Asset depreciation book before any transactional data is loaded. If e-invoicing is in scope, we flag the ISV add-on requirement here.
Opening balance migration and GL seeding
We post opening balances to the destination GL as General Journal entries before transactional data. This includes all G/L accounts with balances, accounts receivable and accounts payable open items, inventory current stock positions, and Fixed Asset opening book values. Opening balance confirmation by the customer's finance team is a gate before we proceed to transactional migration. Payroll records are held at this stage and will be loaded after Payroll module migration (maintaining the Payroll-to-GL sequencing dependency).
Transactional migration in dependency order
We load master data (Customers, Vendors, Items, Employees) first, then transactional data in the following order: Sales Orders, Purchase Orders, Inventory transactions, Fixed Asset transactions, CRM Leads and Contacts, CRM Opportunities, and Activity history. Journal entries from AR and AP are loaded after the COA and opening balances are confirmed. Payroll is loaded last before the Payroll-sourced GL journal entries, preserving the Payroll-to-GL sequencing dependency throughout. Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, delta migration, and configuration replay
We freeze FACT ERP.NG writes during the cutover window, run a final delta migration of any records modified during the migration window, then replay the configuration parameter script into the destination setup tables. We deliver a written inventory of all FACT workflows, automations, e-invoice compliance configuration requirements, and CXO Control Tower KPIs with Power BI rebuild guidance. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's team. We do not rebuild FACT workflows as Power Automate flows or as Dynamics 365 business events inside the migration scope.
Platform deep dives
FACT ERP.NG
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Business Central
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. All 8 core objects map 1:1 between FACT ERP.NG and Microsoft Dynamics 365 Business Central.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across FACT ERP.NG and Microsoft Dynamics 365 Business Central.
Object compatibility
All 8 core objects map 1:1 between FACT ERP.NG and Microsoft Dynamics 365 Business Central.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
FACT ERP.NG: Not publicly documented.
Data volume sensitivity
FACT ERP.NG doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during FACT ERP.NG to Microsoft Dynamics 365 Business Central migration scoping. Not seeing yours? Book a call.
Walk through your FACT ERP.NG to Microsoft Dynamics 365 Business Central migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave FACT ERP.NG
Other ways to arrive at Microsoft Dynamics 365 Business Central
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.