Migrate from Accolent ERP to Infor CloudSuite Corporate

Accolent Customer records include billing address, shipping addresses, contact details, account type flags, and payment terms. We extract all customer fields from the Accolent customer master table and map them to the Infor Business Partner record with role = Customer. Accolent's multiple shipping addresses per customer map to Infor's Ship-To address records linked to the Business Partner. Payment terms, credit limits, and tax exemption flags transfer as Business Partner attributes. For cloud tenants where direct database access is unavailable, we request a CSV export of the customer master through ADS Solutions, validate field counts against the Accolent schema, and transform to Infor Business Partner format before loading via ION or direct API.

Accolent Vendor records include address, payment terms, PO defaults, and the vendor type flag. We extract vendor master records and map them to Infor Business Partner with role = Vendor. Accolent's PO instruction defaults (ship-via, buyer, terms) map to vendor-level purchasing attributes in Infor. We preserve the Accolent vendor number as the primary vendor code and flag any duplicate vendor codes for manual resolution before load.

Accolent Items are the core inventory object supporting multiple warehouse locations, cost layers, reorder points, and BOM links. We extract item master records including item number, description, unit of measure, cost method, standard cost, lot/serial controls, and warehouse-specific stock levels. We map Accolent's item type (Stocked, Non-Stocked, Service, Expense) to Infor's item type flags. Cost layers transfer as landed cost components or standard cost records. For items linked to BOMs, we extract the BOM association so that the BOM mapping step can resolve the product structure post-item load.

Open and historical sales orders in Accolent carry order headers, line items, pricing, discounts, and fulfillment status. We extract SO headers with customer reference, order date, terms, and ship-via, then extract all SO lines with item, quantity, unit price, and warehouse assignment. We flag fulfilled lines versus open lines so that Infor receives open orders in an active state and closes historical orders with the original close date. Order totals and tax amounts validate against Accolent's document totals before Infor load.

Accolent PO records include vendor references, line items, quantities ordered, unit costs, and receipt status. We extract PO headers and lines, mapping to Infor Purchase Order with the vendor Business Partner resolved from the vendor mapping step. Receipt status transfers as Infor's receipt action (receive, return, or close). Lines that are fully received in Accolent are closed in Infor with the receipt date preserved. Open PO lines migrate with their original promise dates and quantities remaining.

Accolent stores a structured GL chart with account numbers, names, types (Asset, Liability, Expense, Revenue), and optional cost-center assignments. We extract the full chart and map account codes to Infor GL Account records, preserving the account type, posting restrictions, and currency. Cost-center assignments in Accolent map to Infor's cost center or department dimension. The GL chart must be loaded before any AP/AR or journal entry records because account references are required for validation.

Outstanding payables in Accolent must land as existing open balances in Infor rather than re-invoiced. We extract AP invoice headers (vendor, invoice number, invoice date, due date, total amount, terms) and credit memos with outstanding amounts. Accolent does not expose a dedicated AP aging export, so we query the AP open table directly (on-premise) or request a vendor aging report through ADS Solutions (cloud). We map invoice amounts to Infor AP open items using the vendor Business Partner lookup resolved from the vendor mapping step. We flag any invoice with original date more than 90 days past for customer review before committing to Infor.

Outstanding receivables in Accolent must land as existing open balances in Infor AR. We extract AR invoice headers (customer, invoice number, invoice date, due date, total amount, terms) and credit memos with outstanding amounts. We map to Infor AR open items using the customer Business Partner lookup resolved from the customer mapping step. We flag any invoice with original date more than 90 days past for customer review before committing. Payment terms and aging buckets transfer as aging data attributes in Infor AR.

Accolent multi-level BOMs include parent-component relationships, quantity-per, routing steps, work-center assignments, and phantom BOM flags for sub-assemblies. We extract BOM headers and all component lines, preserving the bill structure and quantity-per relationships. Accolent's BOM with more than three levels requires flattening for Infor CloudSuite SyteLine or LN, which use a different manufacturing schema with production versions. We flag any BOM with circular references (parent appearing as its own component) for manual review before loading. Phantom BOMs map to Infor's phantom BOM type flag. Routing operations transfer as Infor work-center sequences with setup and run times where available in Accolent.

Accolent supports multiple warehouse sites with bin/shelf location tracking. We extract warehouse definitions including the warehouse code, name, and address, then extract bin/shelf location codes per warehouse. Bin-level detail maps to Infor location or bin records under the warehouse parent. If Accolent tracks bin quantities, we extract bin-level stock and reconcile total stock against the item warehouse total as a pre-load validation checkpoint.

Historical GL transactions in Accolent include date, account, debit/credit amounts, source module, and document reference. We extract all posted journal entries for the period scope agreed upon during scoping (full history or rolling 13 months). Journal line debits and credits must balance in Accolent before we extract them. We map Accolent account codes to Infor GL Account numbers using the chart of accounts mapping. Source references (SO number, PO number, AP invoice, AR invoice) preserve as journal line description fields in Infor for audit trail. Infor CloudSuite SyteLine uses the FinPosting tables; M3 uses CST tables; LN uses FINMGT tables — we confirm the target edition's journal entry API or direct table load method during discovery.

Accolent fixed-asset records include acquisition cost, acquisition date, depreciation method (straight-line, declining balance, units of production), accumulated depreciation, useful life, salvage value, and asset class. We extract asset records and map them to Infor Fixed Asset records, preserving the asset class mapping to Infor's depreciation book configuration. Accumulated depreciation transfers as an opening accumulated depreciation entry in Infor's asset register. We flag any asset where the net book value calculation does not reconcile against the source Accolent figures for manual review.

Accolent tax codes define rates and applicability rules for sales and purchasing transactions. We extract the tax code master including code, description, rate percentage, and applicability (sales vs. purchasing). We map Accolent tax codes to Infor's tax code configuration, flagging any jurisdiction-specific codes (state, county, city) that require customer configuration in Infor's tax jurisdiction table. Accolent tax-exempt flags on customer or vendor records map to Infor tax exemption certificates attached to the Business Partner.

Accolent user accounts include user ID, name, email, role, and access-control assignments. We extract user records and role definitions, then map to Infor User records with the appropriate security role. Accolent's role-based permissions map to Infor's functional security roles (purchasing, sales, inventory, GL, admin). We resolve Accolent user IDs to Infor user IDs by email match during the import. Any Accolent user without an Infor account goes to a reconciliation queue for the customer's Infor admin to provision before record migration continues.