ERP migration
Field-level mapping, validation, and rollback between Exact Globe and Infor CloudSuite Corporate. We move data and schema; workflows are rebuilt natively in Infor CloudSuite Corporate.
Exact Globe
Source
Infor CloudSuite Corporate
Destination
Compatibility
12 of 13
objects map 1:1 between Exact Globe and Infor CloudSuite Corporate.
Complexity
BStandard
Timeline
6-9 weeks
Overview
Moving from Exact Globe to Infor CloudSuite is a cross-architecture migration from a client-server on-premise ERP to an industry-specific multi-tenant cloud suite on AWS. Exact Globe stores business data in a Microsoft SQL Server database accessed via Exact.Services.Client DLLs or REST APIs; Infor CloudSuite uses a migration database architecture that feeds a production database through sequenced import steps with strict form-dependency requirements. The mandatory end-of-life of Exact Globe Next at the end of 2026 forces the migration decision for most customers who have not already moved. We profile the Exact Globe database during discovery to determine whether the customer is on an older Exact Globe version requiring an intermediate Exact Globe Next step before CloudSuite, extract master data and transactional history via direct SQL Server queries, and map every standard object (Accounts, GL, Invoices, Items, Orders, Projects, BOMs, Fixed Assets, Contact persons) to the corresponding Infor CloudSuite table. Custom fields on Exact Globe's 14 standard tables are catalogued, type-mapped, and locked in the destination schema before extraction. Workflows, approval chains, and custom business logic do not migrate as code; we deliver a written inventory for the customer's admin to rebuild in Infor OS Process Studio. File attachments are not reliably accessible via the Exact Globe API and are handled as a manual post-migration step.
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
Exact Globe platform overview
Scorecard, SWOT, gotchas, and pricing for Exact Globe.
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 Exact Globe 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.
Exact Globe
Accounts (Debtors/Creditors)
Infor CloudSuite Corporate
Business Partner
1:1Exact Globe Accounts map to Infor CloudSuite Business Partner records with a customer/vendor type distinction applied during extraction. Debtor accounts (AR) map to Business Partner with bp_type = Customer; Creditor accounts (AP) map to bp_type = Supplier. Address book entries, payment terms, VAT codes, and credit limits transfer as BP properties. The BP code in Infor CloudSuite is generated from the Exact Globe account code; we validate uniqueness before insert.
Exact Globe
Financial entries and entry lines
Infor CloudSuite Corporate
Journal Entry / GL Entry
1:1Exact Globe stores journal entries and their line items in separate but related tables. We extract entry-level metadata (date, journal, description) and line-level data (account, debit, credit, dimension) preserving the relationship via entry number keys. Tax codes, cost center references, and dimension values from Exact Globe require field-level mapping to Infor's account structure and cost element schema. Locked or reconciled periods are handled through date-range scoping agreed upon during discovery.
Exact Globe
Invoices and invoice lines
Infor CloudSuite Corporate
AR Invoice / AP Invoice
1:1Sales and purchase invoices split into header and line tables in Exact Globe. We extract both, preserving the relationship via invoice number keys. Tax codes, payment terms, invoice status flags, and approval workflow states transfer to Infor AR/AP Invoice header properties. Line items carry item reference, quantity, unit price, and discount fields. We flag any invoices in open or partially paid status during extraction for the customer's accounting team to close or reconcile before the migration date.
Exact Globe
Items
Infor CloudSuite Corporate
Item
1:1Items (products, services, and variants) are a stable master-data object in Exact Globe. We extract item code, description, unit of measure, cost price, sales price, and item type (stock/non-stock/service). BOM associations carry forward as BOM links to product items. Warehouse-specific stock levels and bin locations are extracted for inventory initialization in Infor CloudSuite inventory tables.
Exact Globe
Bills of Materials
Infor CloudSuite Corporate
BOM / Routing
1:1BOMs define multi-level product structures with component items, quantities, and routing steps. Exporting BOMs requires recursive traversal of sub-assemblies in staged extraction passes. Each BOM level is mapped to an Infor CloudSuite BOM header with associated BOM lines, and any defined routing operations map to Infor routing steps. We preserve phantom BOM flags and BOM effectivity dates from Exact Globe.
Exact Globe
Sales orders and purchase orders
Infor CloudSuite Corporate
Sales Order / Purchase Order
1:1Sales orders and purchase orders each split into header and line rows in Exact Globe. Order status (open, processed, invoiced) and back-order relationships are preserved through ID key mapping. Partial shipment flags and delivery schedules carry forward. We extract open orders first so that in-flight orders can be acknowledged in Infor CloudSuite before closed orders are imported as history.
Exact Globe
Quotations
Infor CloudSuite Corporate
Quote
1:1Quotations are header-level documents with line items in Exact Globe. Conversion status (expired, converted to order) is stored as a flag and must map to Infor CloudSuite's quote lifecycle states. Quote validity dates and discount schedules transfer as header and line properties. We separate active/open quotations from expired quotations so that only relevant quotes are migrated as open opportunities.
Exact Globe
Projects
Infor CloudSuite Corporate
Project
1:1Project accounting is embedded throughout Exact Globe's product line. We extract project headers, cost categories, billing methods, budget data, and project types. Project status (active, completed, on hold) carries forward. Project-related time entries are a separate object; we extract them with project and employee keys for resolution during Infor CloudSuite project cost loading. Date-range scoping applies to historical project cost postings.
Exact Globe
Human Resources
Infor CloudSuite Corporate
Human Resources (Employee)
1:1HR data in Exact Globe covers employee records, compensation, and org structure. Effective-dated changes are stored transactionally, requiring careful sequencing during export to preserve historical pay rate and position changes. We extract current employee records for Infor CloudSuite HR initialization, and flag any historical compensation records that the customer wants to carry forward as HR audit history. Org structure maps to Infor's department and cost center hierarchy.
Exact Globe
Contact persons
Infor CloudSuite Corporate
Contact
1:1Contact persons are linked to Accounts but have independent records in Exact Globe. We extract name, role, email, phone, and address fields. Ownership and lifecycle-stage assignments map to custom properties in Infor CloudSuite. Contact person records are imported after Business Partner records so that the BP lookup relationship is satisfied at the moment of Contact insert.
Exact Globe
General ledger
Infor CloudSuite Corporate
Chart of Accounts
1:1The Chart of Accounts and all posted journal entries are available for export from Exact Globe. We handle account codes, descriptions, account groups, and posting history. Account type (balance sheet vs. P&L) maps to Infor account classification. Locked or reconciled periods require date-range scoping during the discovery call to manage export window sizes for high-volume GL histories.
Exact Globe
Fixed Assets
Infor CloudSuite Corporate
Fixed Asset
1:1Fixed asset records include acquisition cost, depreciation method, book value, and asset class. Depreciation schedules must be recalculated in Infor CloudSuite if the fiscal year calendar differs from Exact Globe's. We extract the current book values and accumulated depreciation as of a customer-defined cutoff date, and flag any assets with mid-period acquisitions or disposals for the customer's finance team to validate.
Exact Globe
Custom fields on standard tables
Infor CloudSuite Corporate
Custom Fields
lossyExact Globe allows custom fields (text, long, double, date, bit) on 14 standard tables including Financial entries, Accounts, Invoices, Items, Orders, Projects, HR, and Contact persons. We catalog every custom field during discovery by table, field name, and field type, confirm the final schema with the customer, and pre-create matching custom fields in Infor CloudSuite before any data extraction. Field names cannot be changed and field types cannot be edited after creation in Exact Globe; we lock the mapping before the extraction phase begins.
| Exact Globe | Infor CloudSuite Corporate | Compatibility | |
|---|---|---|---|
| Accounts (Debtors/Creditors) | Business Partner1:1 | Fully supported | |
| Financial entries and entry lines | Journal Entry / GL Entry1:1 | Mapping required | |
| Invoices and invoice lines | AR Invoice / AP Invoice1:1 | Mapping required | |
| Items | Item1:1 | Fully supported | |
| Bills of Materials | BOM / Routing1:1 | Mapping required | |
| Sales orders and purchase orders | Sales Order / Purchase Order1:1 | Fully supported | |
| Quotations | Quote1:1 | Mapping required | |
| Projects | Project1:1 | Fully supported | |
| Human Resources | Human Resources (Employee)1:1 | Mapping required | |
| Contact persons | Contact1:1 | Fully supported | |
| General ledger | Chart of Accounts1:1 | Fully supported | |
| Fixed Assets | Fixed Asset1:1 | Mapping required | |
| Custom fields on standard tables | Custom Fieldslossy | 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.
Exact Globe gotchas
Exact Globe Next end-of-support creates a hard migration deadline
Cannot run Exact Globe Next and Exact Globe+ concurrently
API rate limits on Exact Online cloud restrict bulk export speed
Custom fields on standard tables are schema-locked after creation
File attachments are not reliably accessible via standard APIs
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 version assessment
We audit the Exact Globe SQL Server database: current edition version (legacy Exact Globe, Exact Globe Next, or Exact Globe+), active modules in use (Financials, Logistics, Projects, HR), record counts per object, number of custom fields on standard tables, and open-transaction aging. We also identify any third-party add-ons integrated with Exact Globe that will need replacement in Infor CloudSuite. This determines whether an intermediate Exact Globe Next step is required and establishes the base dataset for the migration scope document and pricing proposal.
SQL Server export profiling and date-range scoping
Exact Globe stores business data in Microsoft SQL Server. We connect to the production database with read-only access, profile high-volume tables (GL entry lines, order lines, invoice lines) to identify timeout-prone queries, and chunk large exports into date-scoped batches. We agree on a transaction cutoff date with the customer's accounting team and document all open items (unpaid invoices, unmatched POs, unreconciled GL batches) that need to be resolved before extraction. Custom field inventory is finalized and locked at this stage.
Schema design and Infor dependency-order mapping
We design the Infor CloudSuite migration database schema by mapping each Exact Globe table to its Infor CloudSuite equivalent. We produce a dependency-order spreadsheet listing every target form in the sequence required by Infor CloudSuite, starting with foundational tables (cost centers, tax codes, payment terms) and progressing to dependent tables (Business Partners, Items, Projects, then transactional records). Field-level transformations (data types, length, value mappings) are defined and validated in the mapping document. We pre-create all custom fields in Infor CloudSuite before any import runs.
Data assessment and preliminary data transfer
We run the Infor CloudSuite preliminary data transfer process with the Exact Globe dataset to generate a Data Assessment Report. This report identifies transformation issues, invalid values, and data-quality problems before production migration. We review the report with the customer's team, adjust mapping rules, correct source data where feasible, and document any records that require manual entry in Infor CloudSuite forms due to missing counterparts in Exact Globe.
Sandbox migration and reconciliation
We run a full migration into the Infor CloudSuite test environment using production-like data volume. The customer's team reconciles record counts across all objects, spot-checks 25-50 records per object against the Exact Globe source, and validates the dependency chain (for example, confirming that all BP lookups on Contact and Invoice records resolve correctly). Schema corrections, mapping adjustments, and custom field additions happen in this environment. Sign-off on the sandbox migration is required before production cutover.
Production migration and cutover
We execute production migration in dependency order: foundational codes first (tax, payment terms, cost centers), then master data (Business Partners, Items, Projects, Employees), then transactional history (journal entries, invoices, orders, quotations, BOMs). Each phase emits a row-count reconciliation report before the next phase begins. On cutover day, we freeze Exact Globe writes, run a final delta migration of any records created since the freeze date, then enable Infor CloudSuite as the system of record. We deliver the attachment export checklist and the workflow and automation inventory document to the customer's admin team.
Hypercare and handoff
We support a one-week hypercare window following cutover, resolving any reconciliation issues raised by the customer's team. We do not rebuild Exact Globe workflows, approval chains, or automations as Infor OS Process Studio workflows; those are out of scope and addressed in a separate engagement or by the customer's admin team using the workflow inventory we deliver. File attachment migration remains a manual post-migration step managed by the customer's IT team using the checklist we provide.
Platform deep dives
Exact Globe
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 Exact Globe 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
Exact Globe: Not publicly documented for on-premise Exact Globe; Exact Online cloud enforces 5,000 calls/day.
Data volume sensitivity
Exact Globe 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 Exact Globe to Infor CloudSuite Corporate migration scoping. Not seeing yours? Book a call.
Walk through your Exact Globe 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 Exact Globe
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.