ERP migration
Field-level mapping, validation, and rollback between Manu Online and Infor CloudSuite Corporate. We move data and schema; workflows are rebuilt natively in Infor CloudSuite Corporate.
Manu Online
Source
Infor CloudSuite Corporate
Destination
Compatibility
10 of 11
objects map 1:1 between Manu Online and Infor CloudSuite Corporate.
Complexity
BStandard
Timeline
5-8 weeks
Overview
Moving from Manu Online to Infor CloudSuite Industrial is a structured ERP migration that routes entirely through Manu Online's Azure-hosted DataWarehouse SQL export, since no public REST or bulk API exists. We scope the migration against the manuonline_-prefixed DataWarehouse schema, coordinate with the Manu Online team to verify DataWarehouse licensing, and map FIFO cost layers to Infor's applicable cost method during transformation. Serial and lot traceability chains transfer if they were recorded at goods receipt; we surface any gaps before migration begins. Open sales orders, purchase orders, and works orders carry forward with their dispatch or production state to avoid duplicate creation in Infor. We do not migrate reports, workflows, or automations; Infor CloudSuite's report library and production scheduling rules require rebuild by the customer's implementation team or an Infor partner.
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
Manu Online platform overview
Scorecard, SWOT, gotchas, and pricing for Manu Online.
Destination platform
Infor CloudSuite Corporate platform overview
Scorecard, SWOT, gotchas, and pricing for Infor CloudSuite Corporate.
Data migration guide
The complete Infor CloudSuite migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Infor CloudSuite migration checklist
Pre- and post-cutover tasks for moving onto Infor CloudSuite Corporate.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Manu Online object lands in Infor CloudSuite Corporate, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Manu Online
Product
Infor CloudSuite Corporate
Item Master
1:1Manu Online Products (manufactured, resold, and purchased variants) map to Infor CloudSuite Industrial Item Master records. The DataWarehouse manuonline_product table provides the cost layers, default warehouse, unit of measure, and stock settings. We map FIFO unit costs to Infor's Item Standard Cost or Moving Average Cost depending on the destination cost method selected during scoping. Serial and lot tracking flags transfer to Infor's Item Lot Control and Serial Number Control flags.
Manu Online
Bill of Materials
Infor CloudSuite Corporate
Bill of Material / Recipe
1:manyManu Online BOMs define ingredient lists and quantities per finished good. Multi-level BOMs are supported in Enterprise Edition. We map sub-assembly structures to Infor CloudSuite BOMs, collapsing or expanding levels depending on whether the destination usesIndented BOM or Flat BOM structure. Mini Enterprise customers migrating from single-level BOMs will have a simpler mapping; Enterprise customers with multi-level BOMs require a recursive expansion step before Infor import.
Manu Online
Stock / Inventory
Infor CloudSuite Corporate
Item Stock
1:1Stock exists per product per warehouse with on-hand, allocated, and ordered quantities in Manu Online. We map to Infor CloudSuite Item Stock records per warehouse, preserving on-hand quantities, allocated stock, and open purchase receipt lines. Serial numbers and lot numbers attach to the stock records at the transaction level and transfer as traceability entries in Infor's lot and serial number registers.
Manu Online
Customer
Infor CloudSuite Corporate
Business Partner (Customer Role)
1:1Manu Online Customers carry address, contact, tax registration, and price list assignment. We map to Infor CloudSuite Business Partner records with the Customer role. Credit limits, price group assignments, and open sales order references transfer as additional fields. Open sales orders carry forward with their line-level dispatch state so that partially despatched lines do not re-trigger picking or delivery in Infor.
Manu Online
Supplier
Infor CloudSuite Corporate
Business Partner (Supplier Role)
1:1Manu Online Suppliers hold the same address and contact fields as customers, plus lead time and preferred units of purchase. We map to Infor CloudSuite Business Partner with the Supplier role. Purchase order history and outstanding open POs transfer with their receipt state to prevent duplicate ordering in Infor.
Manu Online
Sales Order
Infor CloudSuite Corporate
Sales Order
1:1Manu Online Sales Orders include line items, pricing, dispatch instructions, and status. Partially despatched lines are common in manufacturing environments and map to Infor Sales Order lines with the same dispatched versus ordered quantities preserved. We map order status to Infor's Sales Order status codes, and pricing adjusts if Infor uses a different price list structure (Infor typically uses Price Book and Price Lists rather than per-customer price groups).
Manu Online
Purchase Order
Infor CloudSuite Corporate
Purchase Order
1:1Purchase Orders link to suppliers and specify expected delivery dates and received-versus-ordered quantities. We map open POs with their receipt state so that partially received lines are not re-requested in Infor. Closed POs transfer as historical records. Any POs already received in full and posted in Manu Online are marked as complete in Infor without re-triggering the procurement workflow.
Manu Online
Works Order
Infor CloudSuite Corporate
Production Order
1:1Manu Online Works Orders drive production: they reference a BOM, allocate stock, and record labour time and completed quantities. We map works order stages and any unfinished progress (materials allocated, operations started but not complete) to Infor CloudSuite Production Orders. Parallel production order handling from Enterprise Edition maps to Infor's multi-run production capability. Any in-progress operations transfer with their actual labour entries so that production reporting continuity is preserved.
Manu Online
Invoice and Credit Note
Infor CloudSuite Corporate
AR Invoice / AP Invoice / Credit Note
1:1Posted invoices and credit notes in Manu Online carry accounting implications, especially when Xero has already received the data via the native push. We coordinate with the customer to determine whether posted invoices migrate as open items, closed items, or are excluded from migration if already in Xero. Open AR and AP invoices map to Infor CloudSuite Receivables and Payables documents with payment terms and tax codes translated.
Manu Online
Serial and Lot Number
Infor CloudSuite Corporate
Lot / Serial Number Register
1:1Traceability records link serial or lot numbers to stock transactions, works orders, and delivery documents in Manu Online. We preserve the full traceability chain including supplier lot origin, production run association, and customer delivery. Infor CloudSuite Industrial receives the traceability data into its lot and serial number registers. We include a pre-migration data quality check reporting the percentage of lines with complete traceability and flag any gaps at goods-receipt time for customer review.
Manu Online
User
Infor CloudSuite Corporate
User
1:1Manu Online user accounts carry login, email, and role-based permissions. We map active users to Infor CloudSuite User records. Elevated admin privileges and role assignments flag for explicit re-creation in Infor's role management. Infor CloudSuite role-based access control uses Responsibility and Security Groups that map from Manu Online role definitions during scoping.
| Manu Online | Infor CloudSuite Corporate | Compatibility | |
|---|---|---|---|
| Product | Item Master1:1 | Fully supported | |
| Bill of Materials | Bill of Material / Recipe1:many | Fully supported | |
| Stock / Inventory | Item Stock1:1 | Fully supported | |
| Customer | Business Partner (Customer Role)1:1 | Fully supported | |
| Supplier | Business Partner (Supplier Role)1:1 | Fully supported | |
| Sales Order | Sales Order1:1 | Fully supported | |
| Purchase Order | Purchase Order1:1 | Fully supported | |
| Works Order | Production Order1:1 | Fully supported | |
| Invoice and Credit Note | AR Invoice / AP Invoice / Credit Note1:1 | Fully supported | |
| Serial and Lot Number | Lot / Serial Number Register1:1 | Fully supported | |
| User | User1: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.
Manu Online gotchas
DataWarehouse SQL export is the only bulk data path
Xero integration can duplicate posted invoices
FIFO cost layers do not translate directly to average-cost ERPs
Serial and lot traceability is source-system-gated
Enterprise-tier features may not appear in Mini Enterprise data
Infor CloudSuite Corporate gotchas
Infor OS tier-based usage limits gate API and BaaS capabilities
Custom Fields use inconsistent naming across Infor editions
SQL migration utility requires source database access
Multi-site and multi-currency data require separate period closure sequencing
REST API payload and timeout limits restrict bulk migration throughput
Pair-specific challenges
Migration approach
Discovery and DataWarehouse access verification
We audit the Manu Online DataWarehouse schema across tables prefixed manuonline_, identify the licensed modules (Mini Enterprise vs Enterprise Edition), and verify DataWarehouse extension status. We inventory all objects in scope: Products, BOMs, Stock, Customers, Suppliers, open Sales Orders, open Purchase Orders, open Works Orders, posted Invoices, Serial/Lot registers, and Users. We also map the Xero integration status to determine which invoices have already been pushed to Xero and must be excluded or flagged as historical. The discovery output is a written migration scope with a DataWarehouse access plan.
Data quality assessment and traceability audit
We run a pre-migration data quality check against the DataWarehouse, reporting completeness rates for serial and lot numbers at goods receipt, customer and supplier address completeness, and open order state consistency. Any gaps are surfaced before migration begins so the customer can decide whether to backfill historical records or accept the gap in Infor. We also compute FIFO cost layers per product and prepare the cost-layer transformation logic for the destination cost method.
Infor CloudSuite target schema preparation
We work with the customer and their Infor implementation team to verify the Infor CloudSuite Industrial configuration: cost method per item or site, warehouse structure, Business Partner number ranges, Item Master code structure, and BOM explosion settings. We generate the dependency-ordered import sequence (master data codes before transactional records) and document any manual-entry prerequisites such as tax codes, payment terms, and unit of measure conversions. The sequence is validated against the Infor CloudSuite Migration Utility's Import Steps form.
Sandbox migration and reconciliation
We run a full migration into the Infor CloudSuite Sandbox or migration database using the DataWarehouse SQL export. The customer reconciles record counts and spot-checks 25-50 records per object type against the Manu Online source. Any mapping corrections — field type mismatches, length constraints, picklist value gaps — are resolved here. The preliminary data transfer step in the Infor Migration Utility identifies any transformation rules that must be added via the Import Rule Definition form before the final transfer proceeds.
Production migration in dependency order
We run production migration in the validated dependency order: Item Masters and Business Partners first, then BOMs, then Stock balances, then open Sales Orders and Purchase Orders, then open Works Orders, then posted Invoices (excluding any Xero-synced documents), then Serial and Lot registers, then Users. Each phase emits a row-count reconciliation report. Any records rejected during import are logged via the Infor Data Transfer Log and corrected before the next phase begins.
Cutover, delta sync, and rebuild handoff
We freeze Manu Online writes during cutover, run a final delta migration of any records modified during the migration window, then enable Infor CloudSuite as the system of record. We deliver a written inventory of any Manu Online workflows, alerts, or reporting exports that require rebuild in Infor CloudSuite's report library and production scheduling tools. We do not rebuild automations or custom reports; those are handed to the customer's Infor implementation partner or admin team.
Platform deep dives
Manu Online
Source
Strengths
Weaknesses
Infor CloudSuite Corporate
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Manu Online and Infor CloudSuite Corporate.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
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
Manu Online: Not publicly documented.
Data volume sensitivity
Manu Online 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 Manu Online to Infor CloudSuite Corporate migration scoping. Not seeing yours? Book a call.
Walk through your Manu Online to Infor CloudSuite Corporate migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Manu Online
Other ways to arrive at Infor CloudSuite Corporate
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.