ERP migration

Migrate from De Facto ERP to Infor CloudSuite Corporate

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 logo

De Facto ERP

Source

Infor CloudSuite Corporate

Destination

Infor CloudSuite Corporate logo

Compatibility

75%

9 of 12

objects map 1:1 between De Facto ERP and Infor CloudSuite Corporate.

Complexity

BStandard

Timeline

6-10 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

De Facto ERP logo

De Facto ERP

What's pushing teams away

  • Very few verified reviews exist publicly, making independent evaluation difficult and suggesting a small customer base or low market visibility for a product in this category.
  • Pricing is not publicly transparent — all tiers require direct contact with sales, which creates friction for prospects evaluating cost against alternatives like Odoo or NetSuite.
  • Ease of use scores are notably low (1.5/5 on Capterra) compared to competitors, indicating the steep customization capability comes at the cost of usability for some users.
  • Support ratings are also low (1.0/5 on Capterra), suggesting that post-implementation support may not match the strong implementation partnership experience.

Choosing

Infor CloudSuite Corporate logo

Infor CloudSuite Corporate

What's pulling them in

  • Infor CloudSuite is industry-specific out of the box — manufacturing, distribution, healthcare, and food & beverage editions ship with preconfigured workflows that reduce the need for extensive customization and accelerate time to value for operations-heavy organizations.
  • The platform's deep integration with Excel for financial reporting is frequently cited as a key productivity feature, allowing finance teams to pull data directly and make changes without leaving familiar tooling.
  • AWS-hosted multi-tenant deployment eliminates data center management for IT teams, and Infor OS provides a unified integration layer (ION) that connects the CloudSuite to third-party applications without point-to-point middleware.
  • Organizations with multi-site or multi-country operations choose Infor for its multicurrency, multilanguage, and local regulatory compliance capabilities across 175+ countries, which simplifies consolidation for global CFOs.
  • The two-tier ERP strategy positioning lets corporate headquarters run CloudSuite while subsidiaries run lighter instances, which appeals to complex organizational structures that want standardization without full replacement.

Object mapping

How De Facto ERP objects map to Infor CloudSuite Corporate

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

maps to

Infor CloudSuite Corporate

Customer / Business Partner

1:1
Fully supported

De 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

maps to

Infor CloudSuite Corporate

Supplier / Business Partner

1:1
Fully supported

Vendor 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

maps to

Infor CloudSuite Corporate

Item / Product

1:1
Fully supported

De 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)

maps to

Infor CloudSuite Corporate

BOM / Formula

1:1
Fully supported

De 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

maps to

Infor CloudSuite Corporate

Landed Cost / Landed Cost Element

lossy
Fully supported

De 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

maps to

Infor CloudSuite Corporate

AP Invoice / Voucher

1:1
Fully supported

Open 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

maps to

Infor CloudSuite Corporate

AR Invoice / Invoice

1:1
Fully supported

Open 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

maps to

Infor CloudSuite Corporate

Chart of Accounts / Account Master

1:1
Fully supported

De 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

maps to

Infor CloudSuite Corporate

Person / User

1:1
Fully supported

De 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)

maps to

Infor CloudSuite Corporate

Purchase Order, Sales Order, Inventory Transactions

1:many
Fully supported

De 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

maps to

Infor CloudSuite Corporate

Fixed Asset Register

1:1
Mapping required

De 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

maps to

Infor CloudSuite Corporate

Document Management / Content

lossy
Mapping required

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

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.

De Facto ERP logo

De Facto ERP gotchas

High

No documented public API for programmatic extraction

High

Highly customized deployments resist template migrations

Medium

Pricing is opaque — all tiers require sales contact

Medium

Limited public review volume and low category ratings

Infor CloudSuite Corporate logo

Infor CloudSuite Corporate gotchas

High

Infor OS tier-based usage limits gate API and BaaS capabilities

Medium

Custom Fields use inconsistent naming across Infor editions

Medium

SQL migration utility requires source database access

Medium

Multi-site and multi-currency data require separate period closure sequencing

Low

REST API payload and timeout limits restrict bulk migration throughput

Pair-specific challenges

  • No De Facto API — TSQL extraction is custom per deployment

    De Facto ERP does not have a documented public API. All data export requires TSQL script development against the proprietary EDP database. Every De Facto deployment is unique, so extraction scripts must be written from scratch during the discovery phase. This extends scoping timelines by two to four weeks and means that migration feasibility cannot be confirmed without direct database access and schema review. We scope extraction script development as a separate line item in discovery before committing to the full migration timeline.

  • Landed cost components require explicit preservation or they are lost

    De Facto's landed cost tracking for importers (freight, insurance, duty, tax per item) is a core differentiator of the platform. If these components are not explicitly mapped as separate cost elements in Infor CloudSuite, they collapse into the item's standard cost and cannot be recovered post-migration. We treat landed cost as a first-class migration object, extract each component type separately from De Facto, and configure Infor Landed Cost elements with matching allocation methods before any item data loads.

  • BOM structures and multi-level routing require parent-child resolution

    De Facto BOM structures for manufactured items can span multiple levels with component substitutions, phantom BOMs, and co-product routes. Infor CloudSuite BOM configuration uses a different hierarchy model. We must resolve the parent-item reference at migration time before inserting child items, and we validate that the Infor BOM supports the same routing steps and work center assignments. BOMs that use De Facto-specific features not available in Infor (such as certain costing methods) are flagged during scoping and mapped to the nearest Infor equivalent.

  • User roles do not map 1:1 between De Facto and Infor OS

    De Facto role definitions are customer-specific and often deeply integrated with business rules. Infor CloudSuite uses Infor Ming.le for identity management with BOD-synchronized user and role provisioning. We extract all De Facto roles with their associated permissions and deliver a role-mapping matrix to the customer's Infor admin. The admin rebuilds equivalent role definitions in Infor Ming.le using Infor OS role management. This is a manual rebuild step that we document but do not execute.

  • Infor CloudSuite form entry order matters for master data

    Infor CloudSuite requires users to complete and post all transactions in sequential order to ensure accurate master data and proper management of data dependencies. Before migrating transactional data, all master data (Customers, Vendors, Items, Chart of Accounts) must be fully loaded and validated in Infor. Skipping this validation results in orphaned transactions, rejected record inserts, or incorrect cost calculations. We sequence the migration in strict dependency order with a master data freeze checkpoint before any transactional data loads.

Migration approach

Six steps for a successful De Facto ERP to Infor CloudSuite Corporate data migration

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

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

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

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

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

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

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

Context on both ends of the pair

De Facto ERP logo

De Facto ERP

Source

Strengths

  • Highly customizable ERP that adapts to company-specific processes rather than forcing standard templates
  • Proprietary EDP (Enterprise Data Platform) architecture designed for flexible, scalable deployment
  • Strong long-term customer partnerships with some clients using the system for decades
  • Handles complex supply chain scenarios including landed costs, landed-cost tracking for importers, and warranty stock management
  • Active implementation support that helps customers migrate existing processes while identifying improvements

Weaknesses

  • Very few publicly verified reviews, making independent evaluation challenging
  • All pricing requires direct sales contact, creating evaluation friction
  • Low ease-of-use scores compared to category alternatives
  • Support quality ratings are inconsistent based on available reviews
  • No documented public API for programmatic data extraction or integration
Infor CloudSuite Corporate logo

Infor CloudSuite Corporate

Destination

Strengths

  • Industry-specific preconfiguration across manufacturing, distribution, healthcare, and food & beverage reduces post-implementation customization effort.
  • Deep Excel integration for financial reporting allows finance teams to export, manipulate, and push data back without leaving a familiar environment.
  • Multi-tenant AWS deployment with Infor OS provides a unified integration layer that simplifies connecting to third-party applications and legacy systems.
  • Strong multicurrency, multilanguage, and regulatory localization capabilities support organizations operating across 175+ countries from a single platform.
  • Modular architecture allows organizations to deploy core financials, supply chain, or manufacturing modules independently and expand over time.

Weaknesses

  • Opaque pricing model with no public per-user rates and deployments commonly ranging from $500K to $5M creates significant budget uncertainty for prospective buyers.
  • Implementation complexity and timeline (commonly 2+ years for large deployments) leads to extended periods of reduced productivity and elevated project risk.
  • Steep learning curve with hidden options and a lack of public setup guidance makes self-service onboarding difficult compared to competitors with richer documentation communities.
  • Manufacturing module functionality is perceived by some users as outdated relative to modern ERP platforms, with reported bug issues that require workarounds.
  • Tight coupling between modules and environment-specific configurations makes migration to non-Infor systems labor-intensive, increasing switching costs.

Complexity grading

How hard is this migration?

Standard ERP migration. 1 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 De Facto ERP and Infor CloudSuite Corporate.

  • Object compatibility

    B

    1 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

    De Facto ERP: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your De Facto ERP to Infor CloudSuite Corporate 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 De Facto ERP to Infor CloudSuite Corporate data migrations

Answers to the questions buyers ask most during De Facto ERP to Infor CloudSuite Corporate migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Migrations under 5,000 items with straightforward landed cost structures and under 100,000 transaction records typically land between six and ten weeks. Migrations with multi-level BOM structures, multi-country landed cost scenarios, large open AP/AR volumes (over 1,000 invoices), or extensive historical transaction sets (over 500,000 records) extend to fourteen to twenty-two weeks because of TSQL extraction script development, BOM-level item mapping, landed cost component preservation, and Infor schema configuration. The discovery phase alone adds two to four weeks because there is no API to query the De Facto database programmatically.

Adjacent paths

Related migrations to explore

Ready when you are

Move from De Facto ERP.
Land in Infor CloudSuite Corporate, 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