ERP migration

Migrate from FACT ERP.NG to Microsoft Dynamics 365 Business Central

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 logo

FACT ERP.NG

Source

Microsoft Dynamics 365 Business Central

Destination

Microsoft Dynamics 365 Business Central logo

Compatibility

92%

12 of 13

objects map 1:1 between FACT ERP.NG and Microsoft Dynamics 365 Business Central.

Complexity

BStandard

Timeline

6-10 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

FACT ERP.NG logo

FACT ERP.NG

What's pushing teams away

  • Slow report rendering and processing delays—users report waiting extended periods for what should be quick queries, especially on larger datasets with full period ranges.
  • Limited depth in certain functional areas—some users supplement FACT ERP.NG with separate software for tasks like advanced HR analytics or niche manufacturing scheduling that the built-in modules do not fully cover.
  • Learning curve for new users despite ease-of-use claims—while the interface is familiar to power users, employees unfamiliar with integrated ERP workflows require structured training before becoming productive.
  • Customisation constraints frustrate niche industry requirements—the Configuration Only model means businesses with highly specific workflows sometimes cannot adapt the system without workaround processes.

Choosing

Microsoft Dynamics 365 Business Central logo

Microsoft Dynamics 365 Business Central

What's pulling them in

  • Deep integration with Microsoft 365, Power BI, and Power Platform means organizations already on the Microsoft stack get identity, reporting, and workflow continuity out of the box.
  • Unified financials, sales, service, and operations replace multiple disconnected systems — users report that data entered once flows through purchase orders, invoicing, and approvals without manual re-entry.
  • Copilot AI features (predictive analytics, embedded business intelligence) are included in both Essentials and Premium tiers, addressing demand for AI without separate module purchases.
  • Named-user licensing with no concurrent model appeals to organizations that want predictable per-seat costs even if some users access the system infrequently.
  • Strong partner ecosystem with certified NAV-to-Business Central migration specialists gives mid-market companies confidence the cutover from legacy Navision can be executed reliably.

Object mapping

How FACT ERP.NG objects map to Microsoft Dynamics 365 Business Central

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

maps to

Microsoft Dynamics 365 Business Central

Customer

1:1
Fully supported

FACT 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

maps to

Microsoft Dynamics 365 Business Central

Vendor

1:1
Fully supported

FACT 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

maps to

Microsoft Dynamics 365 Business Central

Item

1:1
Fully supported

FACT 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

maps to

Microsoft Dynamics 365 Business Central

Sales Order

1:1
Fully supported

FACT 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

maps to

Microsoft Dynamics 365 Business Central

Purchase Order

1:1
Fully supported

FACT 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

maps to

Microsoft Dynamics 365 Business Central

G/L Account

1:1
Fully supported

FACT 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

maps to

Microsoft Dynamics 365 Business Central

G/L Entry

1:1
Mapping required

FACT 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

maps to

Microsoft Dynamics 365 Business Central

Employee / Worker

1:1
Fully supported

FACT 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

maps to

Microsoft Dynamics 365 Business Central

Item Ledger Entry + Warehouse

1:1
Mapping required

FACT 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

maps to

Microsoft Dynamics 365 Business Central

Fixed Asset

1:1
Mapping required

FACT 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

maps to

Microsoft Dynamics 365 Business Central

Contact / Lead

1:1
Fully supported

FACT 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

maps to

Microsoft Dynamics 365 Business Central

General Ledger Setup, Sales & Receivables Setup, Purchases & Payables Setup, Inventory Setup

lossy
Fully supported

FACT 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

maps to

Microsoft Dynamics 365 Business Central

E-Document / Electronic Document

1:1
Fully supported

FACT 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.

Gotchas + challenges

What specifically takes care here

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 logo

FACT ERP.NG gotchas

High

Configuration parameters must be mapped as first-class migration objects

High

Payroll journal entries create a mandatory sequencing dependency with the GL

Medium

Slow report rendering can extend migration validation cycles

Medium

No publicly documented API for direct programmatic extraction

Low

Dashboard configurations are not exportable data objects

Microsoft Dynamics 365 Business Central logo

Microsoft Dynamics 365 Business Central gotchas

High

Named-user licensing has no concurrent-use relief

High

API rate limits throttle large-volume migrations

Medium

Historical posted transactions require selective migration scoping

Medium

NAV-to-Business Central cloud migration requires partner coordination

Low

Custom fields and AL extensions require separate migration handling

Pair-specific challenges

  • Payroll journal entries must be loaded before general ledger transactions

    FACT ERP.NG posts payroll transactions directly to the General Ledger as journal entries at the moment of payroll run, tightly coupling the Payroll and Financials modules. We must load Payroll data first, extract the resulting GL postings as linked journal entries, and then load the Financials module in a second pass. Loading GL before Payroll would create duplicate postings or orphaned debit-credit pairs in Dynamics 365. We enforce this sequencing dependency in all migration timelines and flag any Payroll-General Journal circular references during discovery.

  • FACT ERP.NG has no public API; extraction method is confirmed during discovery

    FACT ERP.NG does not publish a public REST or GraphQL API with documented endpoints, authentication flows, or rate limits. We rely on direct database-level extraction where the customer grants database access, and on FACT export utilities (Excel, CSV) for file-based extraction. The extraction method affects the migration timeline significantly: direct-DB extraction is faster and supports referential integrity checks, while file-based extraction requires additional reconciliation work. We confirm extraction method during the discovery phase and adjust the timeline accordingly.

  • Configuration parameters are first-class migration objects that cannot be skipped

    FACT ERP.NG's Configuration Only model stores business rules, approval thresholds, inventory matrix settings, and tax configurations as platform parameters rather than user-defined fields. During migration scoping, we treat every non-default parameter as a configuration record. If parameters are skipped, Dynamics 365 will run with default values, causing incorrect pricing tiers, tax rates, and approval workflows in production. We document every active parameter during discovery and generate a configuration-replay script that populates the equivalent setup tables in the destination before transactional data is loaded.

  • CXO Control Tower dashboards and reports do not migrate

    The CXO Control Tower dashboards are built within FACT ERP.NG's proprietary visualisation layer and are not exportable as structured data. We treat dashboards as read-only references: customers use them to identify which KPIs and chart types they rely on, and we provide a rebuild guide for Power BI (the native reporting tool for Dynamics 365 Business Central and Finance) rather than a direct migration. Report definitions and scheduled report subscriptions similarly do not transfer; these are documented for manual rebuild by the destination admin.

  • E-invoicing compliance data migrates but the compliance module does not

    FACT ERP.NG's e-invoice records (Malaysian LHDN and Singapore InvoiceNow XML payloads) can be extracted as data files and delivered to the destination, but Dynamics 365 Business Central and Finance do not include native e-invoicing compliance for these jurisdictions as standard features. The destination admin must configure or procure an ISV e-invoicing add-on. We flag this during discovery, provide the e-invoice metadata as a structured dataset, and deliver a written recommendation for e-invoicing compliance configuration post-migration.

Migration approach

Six steps for a successful FACT ERP.NG to Microsoft Dynamics 365 Business Central data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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).

  5. 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.

  6. 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

Context on both ends of the pair

FACT ERP.NG logo

FACT ERP.NG

Source

Strengths

  • Configuration-only deployment with 29-day go-live and no coding required
  • 600+ updates per year included in annual subscription with zero downtime
  • Integrated e-invoicing for Malaysian (LHDN) and Singapore (InvoiceNow) compliance
  • Real-time data sharing across financials, CRM, inventory, manufacturing, and payroll
  • Fast CXO Control Tower dashboard reporting across the full data model

Weaknesses

  • Processing speed degrades on large datasets or full period-range reports
  • Configuration-only model limits adaptation for niche industry workflows
  • Limited depth in certain modules may require third-party supplementation
  • Dashboard exports and API capabilities are not publicly documented for migration tooling
  • No public pricing—quotes are custom per company size and turnover
Microsoft Dynamics 365 Business Central logo

Microsoft Dynamics 365 Business Central

Destination

Strengths

  • Tight integration with Microsoft 365 (Outlook, Teams, SharePoint) for users already in the Microsoft ecosystem.
  • Includes Copilot AI, predictive analytics, and embedded Power BI dashboards at no additional cost in both license tiers.
  • Supports multiple companies within a single tenant for holding-company or multi-entity organizational structures.
  • Open REST API v2.0 with OAuth 2.0 authentication and data entity abstraction layer for developer-friendly integrations.
  • Strong partner ecosystem specializing in NAV-to-Business Central migrations provides implementation confidence for legacy upgrades.

Weaknesses

  • Named-user licensing model means every active user account requires a paid license — no concurrent access model to reduce costs for occasional users.
  • SaaS-only deployment means no on-premises option; organizations requiring full data residency control may not have viable alternatives within Microsoft's stack.
  • Manufacturing module (Production Orders, routing, work centers) is only available on Premium tier, pushing cost-sensitive manufacturers to higher-priced plans.
  • Customization and extension development requires AL language knowledge and developer licenses, limiting what power users can do without a partner engagement.
  • Global pricing increases effective October 2024 and again October 2025 after five years of stable pricing, creating budget uncertainty for existing customers.

Complexity grading

How hard is this migration?

Standard ERP migration. All 8 core objects map 1:1 between FACT ERP.NG and Microsoft Dynamics 365 Business Central.

B

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

    A

    All 8 core objects map 1:1 between FACT ERP.NG and Microsoft Dynamics 365 Business Central.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    FACT ERP.NG: Not publicly documented.

  • Data volume sensitivity

    B

    FACT ERP.NG doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your FACT ERP.NG to Microsoft Dynamics 365 Business Central migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about FACT ERP.NG to Microsoft Dynamics 365 Business Central data migrations

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.

Can't find your answer?

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 consultation

Most FACT ERP.NG migrations land between six and ten weeks for accounts covering two to four modules (Financials plus CRM or Inventory) with under 50,000 transactional rows and direct database access for extraction. Full-ERP migrations across all FACT modules (Financials, Inventory, Manufacturing, Payroll, CRM) with high transaction counts, multi-entity structures, or file-based extraction move to fourteen to twenty-two weeks because of the Payroll-to-GL sequencing work, BOM structure extraction, and configuration-parameter replay scope.

Adjacent paths

Related migrations to explore

Ready when you are

Move from FACT ERP.NG.
Land in Microsoft Dynamics 365 Business Central, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day