Migrate from Infor CloudSuite Corporate to Microsoft Dynamics 365 Business Central

Infor CloudSuite hierarchical Chart of Accounts with cost center and department rollups maps to Dynamics 365 Finance and Operations Main Account structure with Financial Dimensions (such as Department, Cost Center, Business Unit). We extract the full account hierarchy including parent-child relationships and map each Infor account code to a corresponding Main Account with the appropriate dimension values populated. Department and cost center rollup accounts become Financial Dimension default templates in D365.

Infor Customer master records (address books, payment terms, credit limits, and tax registration codes) map to D365 Customer records. Address book entries in Infor with multiple address purposes (invoice, delivery, primary) must be restructured because D365 Finance and Operations allows only one primary address per Customer. We map the primary address to the Customer address and store additional address roles as purpose-coded address records. Payment terms and credit limits migrate to the Customer record directly.

Infor Vendor master records map to D365 Vendor records with the same address restructuring logic as Customer. Tax registration codes from Infor (including VAT, GST, and country-specific identifiers) map to the D365 Tax Registration field on Vendor. We extract vendor payment terms and import them as Vendor payment schedules. W-9 and withholding tax groups migrate to the corresponding D365 tax setup tables.

Infor Item records carry unit of measure conversions, costing method (FIFO, standard, moving average), BOM linkages, and warehouse-specific stocking data. We map the core item record 1:1 to D365 Released Product. UOM conversion tables require mapping from Infor UOM codes to D365 unit of measure definitions. BOM and routing links migrate to D365 Bill of Materials and Route records respectively. Costing method maps to the D365 costing version and inventory model group configuration.

Open payables in Infor CloudSuite (invoice headers, lines, and distribution records) map to D365 pending vendor invoices or vendor invoice journals depending on the posting profile. We extract open invoice balances, payment terms, and aging buckets and import them as open invoices in D365. Infor distribution records (the account, dimension, and amount per line) map to D365 invoice line distributions. Open AP must reconcile to the penny at cutover; any discrepancy blocks period closure in D365.

Open receivables follow the same reconciliation requirement as open AP. Infor CloudSuite invoice headers and lines with payment terms and aging buckets migrate to D365 customer invoices or free text invoices depending on the invoice type used in Infor. Customer payment terms and discount terms are preserved. Credit limit utilization in D365 is recalculated from migrated open AR to ensure the customer's credit exposure is accurate at cutover.

Infor Purchase Agreements include header fields (vendor, terms, expiration) and line-level pricing, quantities, and UOM. Header fields migrate 1:1 to D365 Purchase Agreements. Line-level pricing conditions require mapping to D365 Purchase Agreement line pricing, with UOM matched to the unit of measure definition created during item migration. Agreement expiration dates are preserved; the customer decides whether to activate or leave agreements dormant at cutover.

Infor Work Orders carry routing steps, material allocations, and status (open vs closed). We preserve the work order header, component lines, and routing sequences. Open work orders with status in progress migrate as D365 Production Orders with the corresponding production status. Closed work orders migrate as historical records in a reporting entity. Routing steps map to D365 production route operations, and material allocations map to BOM lines. We flag any Infor work order status values that do not have a direct D365 production order status equivalent for the customer's admin to resolve.

Infor CloudSuite allows user-defined alphanumeric, numeric, and date fields attached to items, suppliers, and purchase agreements. Custom field groups are defined per item group or supplier group. We extract the custom field group definitions first, create equivalent extension fields in D365, then load the field values. Note that custom date fields in Infor cannot be queried via Infor Enterprise Search, so we use direct SQL extraction for these fields rather than the API layer. The custom field group assignments are replicated as D365 product attribute groups or vendor attribute groups depending on the entity.

Infor Document Management stores attachments against customer orders, purchase orders, and work orders as configurable widgets. We migrate the association metadata (which document is attached to which record) and the file references, but binary file content may require a separate file migration step depending on the Infor edition's document storage architecture. We map the document associations to D365 SharePoint document handling or Azure Blob storage depending on the destination configuration. Document content is not transformed; it moves as-is.

Infor user accounts, role assignments, and permission groups require mapping to D365 User records and Security Roles. We extract Infor role profiles and map them to equivalent D365 Security Roles by comparing functional capabilities (finance posting, purchasing, inventory, production). The customer provisions D365 User accounts before migration, and we match Infor user IDs to D365 User IDs by email or by explicit user mapping provided during scoping. Role mapping is documented but may require the customer's security admin to finalize post-migration.

Infor CloudSuite journal entries (general ledger transactions) migrate to D365 General Journal lines. We extract the journal header (journal number, date, description, source system) and the journal lines (account, dimension, debit, credit, currency, amount in transaction and accounting currency). We do not post historical closed periods; we deliver a reference archive of the closed period balances and map open period journal entries. Year-end close entries require coordination with the customer's finance team to ensure the D365 year is opened at the correct point.

Infor CloudSuite organizations running across multiple sites with separate fiscal calendars and currencies require mapping each Infor company to a D365 Legal Entity. We extract open balances and period statuses per Infor company and import them into the corresponding D365 legal entity. Multi-currency open transactions require mapping from Infor currency codes to D365 exchange rate pairs, with the functional and reporting currencies set per legal entity. Period closure sequencing is enforced: source company periods close in the correct order before destination legal entities open their corresponding fiscal periods.

Infor Fixed Asset records with depreciation methods, asset groups, and acquisition histories map to D365 Fixed Assets. Acquisition cost, accumulated depreciation, and book value migrate to the corresponding D365 fixed asset records. Depreciation conventions and methods (straight-line, declining balance, units of production) are mapped to D365 depreciation books. Open depreciation proposals in Infor are either closed before cutover or recreated as D365 depreciation proposals post-migration.