ERP migration
Field-level mapping, validation, and rollback between De Facto ERP and Infor CloudSuite Corporate. We move data and schema; workflows are rebuilt natively in Infor CloudSuite Corporate.
De Facto ERP
Source
Infor CloudSuite Corporate
Destination
Compatibility
9 of 12
objects map 1:1 between De Facto ERP and Infor CloudSuite Corporate.
Complexity
BStandard
Timeline
6-10 weeks
Overview
Moving from De Facto ERP to Infor CloudSuite is a structural migration from a highly customized single-tenant UK platform to an industry-specific multi-tenant cloud ERP. De Facto's proprietary EDP architecture means every export requires TSQL script work and custom mapping; there is no API. We handle landed-cost components (freight, insurance, duty, tax), BOM structures, and landed-cost tracking for importers as a first-class migration concern. Infor CloudSuite uses ION middleware and BOD (Business Object Document) messaging for integrations, which requires structuring the destination schema to accept the migrated data in a way that aligns with Infor's data model. Users and roles synchronize through Infor Ming.le with BOD-based provisioning. We do not migrate custom workflows, SSRS reports, or document-to-record linkages from De Facto; these require admin rebuild in Infor.
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
De Facto ERP platform overview
Scorecard, SWOT, gotchas, and pricing for De Facto ERP.
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 De Facto ERP 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.
De Facto ERP
Customer / Account
Infor CloudSuite Corporate
Customer / Business Partner
1:1De Facto Customer records map to Infor CloudSuite Business Partner (Customer) records. We map customer name, contact details, addresses, and account balances directly. Payment terms from De Facto map to Infor's Payment Terms configuration. The customer type (individual vs corporate) maps to Infor's Business Partner type classification. Currency and tax code assignments are preserved during migration. De Facto CRM opportunity associations map to Infor Distribution CRM opportunities attached to the Business Partner.
De Facto ERP
Vendor / Supplier
Infor CloudSuite Corporate
Supplier / Business Partner
1:1Vendor master records from De Facto map to Infor CloudSuite Business Partner (Supplier) records. We preserve address, payment terms, bank details, and multi-country supplier management settings including currency and tax code assignments. De Facto's supplier-specific landed cost assignments for imported goods migrate to Infor's supplier setup with landed cost allocation rules.
De Facto ERP
Item / Stock Item
Infor CloudSuite Corporate
Item / Product
1:1De Facto stock items map to Infor CloudSuite Item records. This is the most complex mapping in the migration because De Facto items may have variable landed cost components (freight, insurance, duty, tax) per item, multi-UOM support, and BOM structures. We preserve each landed cost component as a separate cost element on the Infor item. Multi-consumer group order processes map to Infor's item stocking and warehouse assignment configuration.
De Facto ERP
Bill of Materials (BOM)
Infor CloudSuite Corporate
BOM / Formula
1:1De Facto BOM structures (bill of materials) for manufactured items map to Infor CloudSuite BOM records. Multi-level BOM hierarchies migrate as parent-child BOM structures. We preserve component quantities, unit of measure conversions, and routing steps. Warranty stock management for importers maps to Infor's warranty tracking configuration on the item record.
De Facto ERP
Landed Cost Components
Infor CloudSuite Corporate
Landed Cost / Landed Cost Element
lossyDe Facto's landed cost tracking (freight, insurance, duty, tax) per imported item migrates as Infor Landed Cost elements. Each De Facto landed cost type becomes a separate Landed Cost Element in Infor. We preserve the allocation method (by quantity, value, weight) and the cost amount. Multi-country landed cost computation scenarios require country-specific tax code mapping in Infor's tax configuration.
De Facto ERP
Open AP / Accounts Payable
Infor CloudSuite Corporate
AP Invoice / Voucher
1:1Open AP invoices from De Facto migrate to Infor CloudSuite AP Voucher records. We preserve invoice number, vendor reference, invoice date, due date, amount, currency, and payment status. Outstanding balance amounts must be verified post-migration to avoid double-payment risk. Credit notes migrate as negative vouchers with the original invoice reference preserved.
De Facto ERP
Open AR / Accounts Receivable
Infor CloudSuite Corporate
AR Invoice / Invoice
1:1Open AR invoices from De Facto migrate to Infor CloudSuite AR Invoice records. Customer reference, invoice date, due date, amount, currency, and payment status migrate with the open balance intact. We flag any invoices with partial payments for reconciliation. Collection status and aging buckets are preserved as custom fields in Infor if the destination does not have equivalent aging reporting.
De Facto ERP
Chart of Accounts
Infor CloudSuite Corporate
Chart of Accounts / Account Master
1:1De Facto's chart of accounts exports via TSQL scripts in structured CSV or XML format and maps directly to Infor CloudSuite Account Master. Account code, description, type (asset, liability, equity, revenue, expense), and posting control are preserved. De Facto's TSQL-generated output is the cleanest export in the migration because account structures follow a standard template.
De Facto ERP
User / Employee
Infor CloudSuite Corporate
Person / User
1:1De Facto User records map to Infor CloudSuite Person records with Infor OS User provisioning. Role definitions in De Facto are often highly custom and do not map 1:1 to Infor's permission model. We extract all users with their role assignments and create a role-mapping matrix. The customer's Infor admin rebuilds role definitions in Infor Ming.le. Inactive De Facto users migrate as inactive Infor persons with a flag for admin review.
De Facto ERP
Historical Transactions (PO, SO, Warehouse Movements)
Infor CloudSuite Corporate
Purchase Order, Sales Order, Inventory Transactions
1:manyDe Facto's full transaction history (purchase orders, sales orders, warehouse movements) via TSQL export maps to Infor CloudSuite transactional records. Large transaction volumes require chunked extraction and batched import. Purchase orders and sales orders import with header-detail structure preserved. Warehouse movements map to Infor inventory transaction records with date, warehouse, quantity, and reason code. Transaction dates and timestamps are preserved for historical reporting.
De Facto ERP
Fixed Assets
Infor CloudSuite Corporate
Fixed Asset Register
1:1De Facto fixed asset records including acquisition cost, depreciation schedules, and asset locations migrate to Infor CloudSuite Fixed Asset management. Depreciation method (straight-line, declining balance, units of production) maps directly. De Facto's landed cost tracking for imported assets overlaps with fixed asset landed cost in Infor; we consolidate these into a single acquisition cost on the Infor asset record.
De Facto ERP
Documents / Attachments
Infor CloudSuite Corporate
Document Management / Content
lossyDe Facto documents linked to data records (customer, vendor, item, transaction) are extracted as files and attached to the corresponding Infor record via Infor's document management. OCR-linked records from De Facto's inbound document processing do not migrate with their OCR associations intact. We extract the document files and deliver them with a linkage manifest for manual re-linkage in Infor or for a post-migration OCR re-processing workflow.
| De Facto ERP | Infor CloudSuite Corporate | Compatibility | |
|---|---|---|---|
| Customer / Account | Customer / Business Partner1:1 | Fully supported | |
| Vendor / Supplier | Supplier / Business Partner1:1 | Fully supported | |
| Item / Stock Item | Item / Product1:1 | Fully supported | |
| Bill of Materials (BOM) | BOM / Formula1:1 | Fully supported | |
| Landed Cost Components | Landed Cost / Landed Cost Elementlossy | Fully supported | |
| Open AP / Accounts Payable | AP Invoice / Voucher1:1 | Fully supported | |
| Open AR / Accounts Receivable | AR Invoice / Invoice1:1 | Fully supported | |
| Chart of Accounts | Chart of Accounts / Account Master1:1 | Fully supported | |
| User / Employee | Person / User1:1 | Fully supported | |
| Historical Transactions (PO, SO, Warehouse Movements) | Purchase Order, Sales Order, Inventory Transactions1:many | Fully supported | |
| Fixed Assets | Fixed Asset Register1:1 | Mapping required | |
| Documents / Attachments | Document Management / Contentlossy | Mapping required |
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.
De Facto ERP gotchas
No documented public API for programmatic extraction
Highly customized deployments resist template migrations
Pricing is opaque — all tiers require sales contact
Limited public review volume and low category ratings
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 extraction architecture
We audit the De Facto EDP database schema, identifying every table and column relevant to the migration scope. We review TSQL script capabilities for each object (master data, transactions, landed cost, BOM, documents) and design a custom extraction approach per object type. We also confirm Infor CloudSuite edition and module availability (Industrial, Distribution, Food & Beverage) and identify the target BOD schema for each migrated entity. Discovery produces a written extraction plan, a preliminary object mapping document, and a dependency graph for sequencing.
Infor schema design and landed cost configuration
We design the destination schema in Infor CloudSuite. This includes configuring Business Partner types (Customer vs Supplier), Item costing with Landed Cost elements, BOM structures, Chart of Accounts with posting controls, and fixed asset depreciation methods. For landed cost scenarios, we set up Landed Cost Elements in Infor matching each De Facto cost type (freight, insurance, duty, tax) with allocation methods preserved from De Facto. Schema is designed in Infor OS before any data loads.
TSQL extraction script development and validation
We develop and test TSQL extraction scripts against a read-only copy of the De Facto database. Each script outputs structured CSV or JSON for a specific object type. We validate extraction completeness against record counts from De Facto's native reports and reconcile totals before staging for migration. Extraction scripts for landed cost components run as separate extracts from the main item export to preserve per-component granularity.
Sandbox migration and reconciliation
We run a full migration into a test environment in Infor CloudSuite using production-like data volume. The customer reconciles record counts (Customers, Vendors, Items, AP/AR, Chart of Accounts, Transactions, Assets), spot-checks landed cost allocations on 25-50 random items, validates BOM structures, and confirms user-role mapping. We address any mapping corrections before production migration. This step validates the extraction scripts, the transformation logic, and the Infor schema configuration.
Master data migration in dependency order
We migrate in strict dependency order: Users and Persons (first, to establish Owner references), Chart of Accounts (no dependencies), Business Partners (Customers and Vendors), Items with Landed Cost Elements (with BOM structures resolved), Fixed Assets, then Open AP and AR (with payment status verified). Each phase emits a row-count reconciliation report. Master data must be fully validated and posted in Infor before any transactional migration begins.
Transactional migration and document handoff
We migrate historical purchase orders, sales orders, and warehouse movements in date-range batches. Documents and attachments are extracted and delivered as a file manifest with linkage mapping to Infor records for manual re-linkage. We deliver the document manifest, the SSRS report list (for admin reference to rebuild in Infor Birst BI), and the De Facto workflow inventory (for admin to rebuild in Infor OS) as written documents. We do not rebuild these in Infor.
Cutover, validation, and go-live support
We freeze De Facto writes during cutover, run a final delta migration of any records modified during the migration window, validate open AP/AR balances in Infor against De Facto's trial balance, then enable Infor CloudSuite as the system of record. We support a one-week hypercare window to resolve reconciliation issues. Infor CloudSuite licensing, implementation consulting, and post-go-live admin training are outside our scope and handled by Infor or an Infor implementation partner.
Platform deep dives
De Facto ERP
Source
Strengths
Weaknesses
Infor CloudSuite Corporate
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 1 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 De Facto ERP and Infor CloudSuite Corporate.
Object compatibility
1 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
De Facto ERP: Not publicly documented.
Data volume sensitivity
De Facto ERP 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 De Facto ERP to Infor CloudSuite Corporate migration scoping. Not seeing yours? Book a call.
Walk through your De Facto ERP 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 De Facto ERP
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.