ERP migration

Migrate from Fraction ERP to Microsoft Dynamics 365 Business Central

Field-level mapping, validation, and rollback between Fraction ERP and Microsoft Dynamics 365 Business Central. We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Business Central.

Fraction ERP logo

Fraction ERP

Source

Microsoft Dynamics 365 Business Central

Destination

Microsoft Dynamics 365 Business Central logo

Compatibility

92%

11 of 12

objects map 1:1 between Fraction ERP 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 Fraction ERP to Microsoft Dynamics 365 is a manufacturing-ERP migration with a specific constraint: Fraction ERP has no publicly documented REST API for bulk exports, so all data extraction requires a coordinated database export or manual report generation through their implementation team before our pipeline can run. We handle that extraction dependency as the first scoping deliverable. On the destination side, Microsoft Dynamics 365 Business Central (for SMB) and Finance and Supply Chain Management (for enterprise) both expose REST APIs with batch endpoints, rate-limit handling, and integration with the Power Platform. We map Fraction ERP's Bill of Materials to D365's BOM structures, preserving multi-level component and routing data; we sequence Works Orders after BOMs to maintain operation reference integrity; and we handle BOM drawing attachments as a parallel file extraction pass. Quotations, Sales Orders, Parts, Inventory, and Purchase Orders migrate via D365's data management framework with entity-specific configuration. Workflows, automations, and custom manufacturing configurations do not migrate; we deliver a written inventory of these for the customer's D365 partner to rebuild post-migration.

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

Fraction ERP logo

Fraction ERP

What's pushing teams away

  • Customers report that the platform lacks depth in financial management modules, pushing them toward NetSuite or Sage Intacct once their business scales beyond basic job costing.
  • The limited number of reviews and small user community makes it difficult to find implementation partners or peer advice when problems arise during deployment.
  • Manufacturers with highly custom workflows or complex multi-plant operations find the platform's configurability insufficient for their needs over time.
  • Some users mention that the user interface feels less polished than competing ERPs, leading to slower user adoption on the shop floor.

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 Fraction ERP objects map to Microsoft Dynamics 365 Business Central

Each row shows how a Fraction ERP 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.

Fraction ERP

Customer

maps to

Microsoft Dynamics 365 Business Central

Customer or Vendor (split by type)

1:1
Fully supported

Fraction ERP Customers hold company name, contact details, and address fields. We map these to D365 Customer entities, creating separate Customer records for accounts-receivable relationships and Vendor records for accounts-payable relationships where the same Fraction ERP Customer also appears on Purchase Orders. The primary address migrates as the Address record with the address-purpose flags set to Invoice and Delivery; secondary addresses require manual assignment in D365 post-migration because D365 allows only one primary address per type.

Fraction ERP

Quotation

maps to

Microsoft Dynamics 365 Business Central

Sales Quote

1:1
Fully supported

Fraction ERP Quotations contain line items, pricing, quantities, validity dates, and customer references. We map them to D365 Sales Quote records, preserving Quote lines with item number, quantity, unit price, line discount, and description. Quote validity dates migrate as ValidFrom and ValidTo. Note that Fraction ERP's quotation-to-order conversion logic does not carry forward as a D365 workflow; we document the conversion pattern for the customer's admin to configure as a D365 action button.

Fraction ERP

Sales Order

maps to

Microsoft Dynamics 365 Business Central

Sales Order

1:1
Fully supported

Sales Orders are the central order record in Fraction ERP, driving Works Order creation. We map them to D365 Sales Order with customer reference, order dates, line items, and status preserved. The Fraction ERP order-number becomes the External Document Number on the D365 Sales Order for reconciliation. Open orders migrate with their full line structure; completed and invoiced orders migrate as historical records with status closed.

Fraction ERP

Part

maps to

Microsoft Dynamics 365 Business Central

Item (Product2 equivalent)

1:1
Fully supported

Fraction ERP Parts are the item master records covering part number, description, unit of measure, standard cost, and inventory valuation data. We map Parts to D365 Items with the Part number as Item Number, preserving unit of measure, cost data, and inventory posting group assignments. D365's unit of measure setup must be configured before item import to satisfy the UoM relationship constraints.

Fraction ERP

Bill of Materials

maps to

Microsoft Dynamics 365 Business Central

BOM and Production BOM

1:1
Fully supported

Fraction ERP Bills of Materials include multi-level component structures, quantities-per, and routing data. We export BOMs as structured records and reconstruct them as D365 BOM versions with line components, quantities, and scrap percentages. Multi-level BOMs (BOMs referencing sub-assemblies that are also BOMs) require a recursive BOM-level sequencing pass before any lower-level BOM is inserted at the destination. Drawing attachments stored as Fraction ERP linked files are retrieved in a parallel file extraction pass and mapped to the D365 Document Handling attachment on the corresponding Item or Production BOM record.

Fraction ERP

Works Order

maps to

Microsoft Dynamics 365 Business Central

Production Order

1:1
Fully supported

Works Orders represent production jobs linked to Sales Orders and BOMs, tracking status, scheduled dates, and assigned operations. We map them to D365 Production Order records, preserving the Works Order number as External Production ID, the linked BOM version, the status mapping (Planned to Simulated, Released to Firm Planned, Finished to Completed), and operation routing from the BOM. Because Works Order operation routing derives from the linked BOM, BOM migration must complete before Works Order import begins.

Fraction ERP

Inventory

maps to

Microsoft Dynamics 365 Business Central

Warehouse Entry and Item Ledger Entry

1:1
Mapping required

Fraction ERP Inventory tracks stock levels, locations, and valuation per Part. We migrate current stock quantities and location assignments to D365 Item Ledger Entries and Warehouse Entries. Valuation data from Fraction ERP (standard cost, average cost) maps to the corresponding D365 cost method setup on the Item; the customer's finance team validates cost layers post-migration because D365 recalculates running averages on posting.

Fraction ERP

Purchase Order

maps to

Microsoft Dynamics 365 Business Central

Purchase Order

1:1
Fully supported

Fraction ERP Purchase Orders cover procurement from vendors with line items, quantities, expected dates, and receiving status. We migrate open and historical Purchase Orders to D365 Purchase Orders with vendor reference, line items, and quantities. Purchase Order status from Fraction ERP (Open, Partially Received, Closed) maps to D365 Purchase Order status with a reconciliation flag for any receiving transactions that may not transfer fully if they were recorded outside the Fraction ERP PO record.

Fraction ERP

Non-Conformance Report

maps to

Microsoft Dynamics 365 Business Central

Quality Issue or Quality Order

1:1
Fully supported

Fraction ERP Non-Conformance Reports track quality issues against Works Orders or Parts. We map NCRs to D365 Quality Order records linked to the corresponding Production Order or Item. NCR disposition codes (Scrap, Rework, Use-As-Is) map to D365 Quality Order Disposition values. Custom quality workflows defined in Fraction ERP require reconfiguration in D365's Quality Management module and are documented as a separate configuration item for the customer's implementation partner.

Fraction ERP

User

maps to

Microsoft Dynamics 365 Business Central

User

1:1
Fully supported

Fraction ERP User accounts include name, email, role, and permissions. We migrate user records and map roles to D365's permission model. Owner references on Customer, Sales Order, Works Order, and Purchase Order records are resolved by matching the Fraction ERP user email to the D365 User record. Individual password credentials cannot be transferred; the customer's D365 admin provisions new user accounts post-migration.

Fraction ERP

Shop Floor Data Capture Log

maps to

Microsoft Dynamics 365 Business Central

Production Journal or Manufacturing Execution Record

lossy
Fully supported

Fraction ERP's shop floor data capture module produces time-series records of production activity against Works Orders: clock-in, operation start/stop, quantity reported, and labour posting. We migrate these as Production Journal lines linked to the corresponding D365 Production Order. The D365 production journal captures reported quantity, labour hours, and machine time per operation step. The customer chooses whether to post journals as posted records (full audit trail) or unposted (for further D365 configuration adjustment).

Fraction ERP

Vendor

maps to

Microsoft Dynamics 365 Business Central

Vendor

1:1
Fully supported

Fraction ERP vendors (distinct from Customers where a third party supplies both materials and services) migrate to D365 Vendor records with address, contact, payment terms, and invoice account assignments. Where a Fraction ERP Customer also functions as a Vendor, we create both a Customer record and a Vendor record with the same address and contact data, linked to the same party in D365's global address book.

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.

Fraction ERP logo

Fraction ERP gotchas

High

No publicly documented API for bulk exports

Medium

BOM drawings stored as attachments require separate file transfer

Medium

Works Order operation sequencing is BOM-dependent

Low

Tier-gated features affect module availability

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

  • Fraction ERP has no public bulk-export API

    Fraction ERP does not publish a REST API with bulk export endpoints. All data extraction requires either a direct database export coordinated through their implementation team or manual report generation from within the application. We cannot build a fully automated polling pipeline against Fraction ERP. At scoping, we request a data export package (CSV grid exports for records, file export for document attachments) from Fraction ERP's implementation team and use that as the input to our migration pipeline. If the implementation team cannot provide a structured export within the agreed timeline, the migration scope and schedule require renegotiation.

  • BOM drawings require a separate file extraction pass

    Bill of Materials records in Fraction ERP store drawing files as binary attachments linked to BOM records. These files do not appear in grid exports and must be retrieved separately through the platform's document export feature. We schedule a parallel file extraction pass, retrieve all BOM-linked drawings, and map each file to the corresponding D365 Item or Production BOM Document Handling attachment. If the drawing files are stored in a network path or SharePoint location rather than inside the Fraction ERP application, we coordinate with the customer's IT team to obtain the file share path during scoping.

  • Works Order routing is BOM-dependent; sequence matters

    Works Orders in Fraction ERP derive their operation routing from the linked Bill of Materials. If BOMs are migrated out of sequence or with a modified structure (different operation counts, changed work centres, or altered routing steps), existing Works Order history will reference non-existent operations and the import will fail or produce orphaned routing records. We enforce BOM-first sequencing in our migration pipeline: all BOMs and BOM versions are inserted and validated before any Works Order is written to D365. We also validate that the BOM version linked to each Works Order exists in the destination before closing the Works Order phase.

  • D365 entity dependencies create a strict import order

    Microsoft Dynamics 365 enforces referential integrity at the API level for most manufacturing entities. Items must exist before BOMs can reference them; BOMs must exist before Production Orders can be created; Production Orders must be in a suitable status before journal lines can post; and Vendors must exist before Purchase Orders can be confirmed. We define a 14-phase import sequence at the start of the project. Skipping phases or reordering imports without adjusting parent-record lookups causes API-level failures. We validate each phase row count against the Fraction ERP export before proceeding to the next.

  • Tier-gated Fraction ERP Advanced features may not transfer to D365 equivalents

    Fraction ERP's Advanced tier at £50/user/month includes enhanced capacity planning and advanced scheduling features. If the customer's team uses these features and they are active in the current system, we flag them during scoping and note that D365's equivalent capabilities (resource load scheduling in Business Central Production, or advanced planning in Finance and Supply Chain Management) may require a higher D365 tier or additional configuration by the customer's D365 partner. We do not configure D365 manufacturing parameters inside the migration scope; we document the existing Advanced-tier settings for the customer's implementation team.

Migration approach

Six steps for a successful Fraction ERP to Microsoft Dynamics 365 Business Central data migration

  1. Extraction coordination and data package receipt

    We initiate contact with Fraction ERP's implementation team to request a structured data export package covering Customers, Quotations, Sales Orders, Parts, BOMs, Works Orders, Inventory, Purchase Orders, Non-Conformance Reports, and Users. We also request a file export of all BOM-linked drawing attachments. While waiting for the package, we audit the Fraction ERP system to document active workflows, custom fields, and tier-gated feature usage. The extraction coordination phase typically takes one to three weeks depending on Fraction ERP's response and their team's availability to generate the exports.

  2. Discovery and D365 edition assessment

    We audit the Fraction ERP data package for record volumes, BOM nesting depth, inventory location count, and non-conformance report patterns. We pair this with a D365 edition assessment: Business Central Essentials ($70/user/month) covers standard manufacturing workflows; Business Central Premium adds service management and advanced warehousing; Finance and Supply Chain Management ($180/user/month) targets multi-plant, multi-currency operations. The discovery output is a written migration scope, a D365 edition recommendation, and a list of Fraction ERP features that require D365 partner configuration post-migration.

  3. Schema design and BOM sequencing plan

    We design the D365 destination schema: Items with unit of measure and cost method, BOM versions with component lines and routing steps, Production Order statuses and number sequences, Warehouse and Location structure, and Quality Management setup for NCR equivalents. The BOM sequencing plan defines the recursive insertion order for multi-level BOMs. We create a BOM-level dependency graph from the Fraction ERP BOM data, order the inserts from leaf-level sub-assemblies upward, and validate that each BOM-level insert resolves its parent references before the next level opens.

  4. Sandbox migration and reconciliation

    We run a full migration into a D365 Sandbox (Full Copy) using production-like data volumes from the Fraction ERP export. The customer's manufacturing operations lead and finance lead reconcile record counts across all 12 entity groups, spot-check 30-50 records against the Fraction ERP source data, and verify BOM routing on a sample of Works Orders. BOM drawing attachments are validated by filename and BOM reference. Any mapping corrections, missing field types, or entity dependency failures are resolved before the production migration scope is finalised. This phase typically runs for one to two weeks.

  5. Owner reconciliation and User provisioning

    We extract every distinct Fraction ERP user referenced as an Owner on Customers, Sales Orders, Works Orders, and Purchase Orders and match by email against the D365 User table. Fraction ERP users without a matching D365 User go to a reconciliation queue. The customer's D365 admin provisions any missing users (active or inactive depending on whether the original Fraction ERP user is still employed). Migration cannot proceed past phase five because OwnerID references are required on most manufacturing and purchasing entities.

  6. Production migration in dependency order

    We run production migration in the validated sequence: Items, BOMs (recursive levels), Locations and Warehouses, Customers and Vendors, Sales Orders, Purchase Orders, Inventory ledger entries, Production Orders, Quality Orders, Shop Floor Data Capture journals, and Non-Conformance Reports. Each phase emits a row-count reconciliation report and a sample record validation report before the next phase begins. BOM drawing attachments are loaded in parallel during the BOM phase. We use D365's data management framework with batch chunking and retry logic for all entity inserts.

  7. Cutover, validation, and configuration handoff

    We freeze writes to Fraction ERP during the cutover window, run a final delta migration of any records modified during the migration window, then enable D365 as the system of record. We deliver the Workflow and Custom Configuration Inventory document to the customer's admin and D365 implementation partner. This document covers BOM drawing attachment mapping, Quality Management NCR disposition code mapping, and any Fraction ERP advanced-tier feature flags that require D365 configuration equivalent. We support a one-week hypercare window for reconciliation issues raised by the manufacturing and finance teams. We do not configure D365 manufacturing parameters, workflows, or Power Automate flows as part of the migration scope.

Platform deep dives

Context on both ends of the pair

Fraction ERP logo

Fraction ERP

Source

Strengths

  • Integrated production-to-inventory data model designed specifically for manufacturing environments without requiring bolt-on modules.
  • Cloud-hosted accessibility means the system works from any browser, reducing on-premise infrastructure overhead for small manufacturers.
  • Native integrations with Xero, QuickBooks, and Sage provide clean handoff to established accounting platforms without manual re-entry.
  • Shop floor data capture module enables real-time production tracking without requiring separate MES investment.
  • Per-user pricing starting at £36/month makes it accessible for teams of 5–20 operators without enterprise-scale costs.

Weaknesses

  • Limited public API documentation means migration tooling must be reverse-engineered or coordinated through Fraction ERP's implementation team.
  • Small review corpus and limited third-party community make peer validation and troubleshooting support harder to find.
  • Financial management capabilities are intentionally shallow, pushing finance teams toward external accounting tools rather than centralising the ledger.
  • The platform targets SMB manufacturers exclusively and lacks the multi-plant, multi-currency, and advanced analytics features that growing companies eventually require.
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. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Fraction ERP and Microsoft Dynamics 365 Business Central.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • 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

    Fraction ERP: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Fraction ERP 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 Fraction ERP to Microsoft Dynamics 365 Business Central data migrations

Answers to the questions buyers ask most during Fraction ERP to Microsoft Dynamics 365 Business Central migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Fraction ERP 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 migrations land between six and ten weeks for accounts with fewer than 2,000 Customers, 500 Parts, and 200 BOMs and where Fraction ERP's implementation team can provide a structured data export within two weeks of request. Migrations with multi-level BOMs (five or more nesting levels), large Works Order histories (over 10,000 production orders), large drawing attachment sets, or multi-plant inventory structures move to fourteen to twenty-two weeks because of BOM sequencing validation, file extraction passes, and D365 entity dependency ordering.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Fraction ERP.
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