Migrate your Fraction ERP data
Cloud-based manufacturing ERP for small-to-mid-size shops that connects sales, production, inventory, and purchasing in one system with shop floor data capture.
In its favor
Why people choose Fraction ERP
The signal that keeps Fraction ERP on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Manufacturers choose Fraction ERP for its integrated shop floor data capture that connects production directly to sales and inventory without requiring third-party MES tools.
Small and mid-size manufacturing companies adopt it because the £36/user/month starting price is accessible compared to enterprise-tier ERP systems while covering core production workflows.
The platform appeals to job shops and discrete manufacturers who need real-time Works Order tracking with capacity scheduling but do not require the full complexity of SAP or Oracle.
Teams migrating from spreadsheets or legacy systems select Fraction ERP because it handles BOMs with drawings and multi-level routing out of the box without heavy customisation.
Manufacturers with existing Xero, QuickBooks, or Sage accounting stacks choose Fraction ERP for its native accounting integrations that avoid re-entry of financial data.
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.
Reasons to switch
Why people leave Fraction ERP
The recurring reasons buyers give for replacing Fraction ERP. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Fraction ERP fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Fraction ERP pricing overview
Fraction ERP charges per user per month with two documented tiers: Basic at £36 and Advanced at £50. The Basic tier covers core manufacturing workflows including BOMs, Works Orders, purchasing, and shop floor data capture.
Basic
Tier 1 of 2
£36.00 per user, per month
What's included
Need help selecting your ERP?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Fraction ERP's schedule — see our quote-based pricing →
What gets migrated
Fraction ERP object support
Object-by-object support for Fraction ERP migrations. Per-pair details surface during scoping.
Customers
Fully supportedCustomers are the primary entity in Fraction ERP, holding company name, contact details, and address information. We migrate Customers as standard Company/Account records, preserving all contact fields and converting to the destination's account object format.
Quotations
Mapping requiredQuotations contain pricing, line items, and validity dates tied to specific Customers. We map quotation line items to the destination's quote or sales order objects, noting that quote-to-order conversion rules vary by destination platform.
Sales Orders
Fully supportedSales Orders are the central order record that triggers Works Order creation. We preserve the full Sales Order structure including status, dates, line items, and linked customer references during migration.
Parts
Fully supportedParts are the item master records covering part numbers, descriptions, unit of measure, and cost data. We migrate the Parts catalog as Items or Products depending on destination terminology, preserving cost and stocking attributes.
Bills of Materials
Mapping requiredBills of Materials include multi-level component structures and drawings. We export BOMs as structured objects and reconstruct them at the destination, noting that drawing attachments require separate file transfer handling.
Works Orders
Fully supportedWorks Orders represent production jobs linked to Sales Orders and BOMs, tracking status, scheduled dates, and assigned operations. We preserve the full Works Order history and operation sequencing during migration.
Inventory
Mapping requiredInventory tracks stock levels, locations, and valuation per Part. We migrate current stock quantities and location assignments, noting that valuation methods may require adjustment at the destination.
Purchase Orders
Mapping requiredPurchase Orders cover procurement from vendors with line items, quantities, and expected dates. We migrate open and historical Purchase Orders, flagging any linked receiving records that may not transfer directly.
Non-Conformance Reports
Mapping requiredNon-Conformance Reports track quality issues against Works Orders or Parts. We map NCRs to the destination's quality or defect object, noting that custom quality workflows may require reconfiguration.
Users
Fully supportedUser accounts include name, email, role, and permissions. We migrate user records and map roles to the destination's permission model, though individual password credentials cannot be transferred.
| Object | Support | Notes |
|---|---|---|
| Customers | Fully supported | Customers are the primary entity in Fraction ERP, holding company name, contact details, and address information. We migrate Customers as standard Company/Account records, preserving all contact fields and converting to the destination's account object format. |
| Quotations | Mapping required | Quotations contain pricing, line items, and validity dates tied to specific Customers. We map quotation line items to the destination's quote or sales order objects, noting that quote-to-order conversion rules vary by destination platform. |
| Sales Orders | Fully supported | Sales Orders are the central order record that triggers Works Order creation. We preserve the full Sales Order structure including status, dates, line items, and linked customer references during migration. |
| Parts | Fully supported | Parts are the item master records covering part numbers, descriptions, unit of measure, and cost data. We migrate the Parts catalog as Items or Products depending on destination terminology, preserving cost and stocking attributes. |
| Bills of Materials | Mapping required | Bills of Materials include multi-level component structures and drawings. We export BOMs as structured objects and reconstruct them at the destination, noting that drawing attachments require separate file transfer handling. |
| Works Orders | Fully supported | Works Orders represent production jobs linked to Sales Orders and BOMs, tracking status, scheduled dates, and assigned operations. We preserve the full Works Order history and operation sequencing during migration. |
| Inventory | Mapping required | Inventory tracks stock levels, locations, and valuation per Part. We migrate current stock quantities and location assignments, noting that valuation methods may require adjustment at the destination. |
| Purchase Orders | Mapping required | Purchase Orders cover procurement from vendors with line items, quantities, and expected dates. We migrate open and historical Purchase Orders, flagging any linked receiving records that may not transfer directly. |
| Non-Conformance Reports | Mapping required | Non-Conformance Reports track quality issues against Works Orders or Parts. We map NCRs to the destination's quality or defect object, noting that custom quality workflows may require reconfiguration. |
| Users | Fully supported | User accounts include name, email, role, and permissions. We migrate user records and map roles to the destination's permission model, though individual password credentials cannot be transferred. |
Gotchas
What to watch for in Fraction ERP migrations
Issues we've hit on past Fraction ERP migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No publicly documented API for bulk exports
BOM drawings stored as attachments require separate file transfer
Works Order operation sequencing is BOM-dependent
Tier-gated features affect module availability
| Severity | Issue |
|---|---|
| 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 |
Leaving Fraction ERP?
Where Fraction ERP customers move next
6 destinations Fraction ERP can migrate to.
How a Fraction ERP migration works
Four steps, Fraction ERP-specific
Connect
Not publicly documented into Fraction ERP. Scopes limited to read-only on the data we move.
Map
We translate Fraction ERP-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Fraction ERP quirks before production.
Migrate
Full migration with Fraction ERP rate-limit handling. Rollback available throughout.
FAQ
Fraction ERP migration FAQ
Answers to the questions buyers ask most during Fraction ERP migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Fraction ERP migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Fraction ERP.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Fraction ERP setup and destination — written quote back within a business day.