Migrate from Maximum Software to Infor CloudSuite Corporate

Maximum Software Customer records map to Infor CloudSuite Customer (or Business Partner depending on the specific CloudSuite edition). The customer name, address, phone, and email fields transfer directly. We require a Payment Terms code assignment on the Infor side, which we either map from a Maximum Software payment terms field or flag for manual assignment before migration completes. Customer credit limits and tax exemption flags map to Infor Customer credit and tax fields respectively.

Maximum Software Vendor records map to Infor CloudSuite Supplier. Address, contact, and banking details transfer directly. Like Customer, Supplier requires a Payment Terms assignment in Infor. We also flag any Vendor records that share an address or contact person with a Customer record, as Infor's Business Partner model may represent the same entity in both roles.

Maximum Software Chart of Accounts records map to Infor CloudSuite GL Account. The account code, description, account type (asset, liability, expense, revenue), and posting level transfer. We flag any inactive accounts that should be archived rather than imported as active. Multi-segment account structures (division-department-expense code) in Maximum Software map to Infor's account segment configuration.

Maximum Software Item records map to Infor CloudSuite Item with Unit of Measure as a required Infor field. If Maximum Software stores items without a defined UOM, we flag the records and assign the customer's default UOM from Infor during import. Cost fields (standard cost, average cost, last cost) map to Infor's item cost schema. Serial number and lot tracking flags transfer if Infor's warehouse module is in scope.

Maximum Software Open Invoices (Accounts Receivable) map to Infor CloudSuite AR Invoice records. Invoice number, customer reference, invoice date, due date, and open amount transfer. We verify that the customer lookup is resolved in Infor before inserting invoice records, as Infor enforces referential integrity on Customer. Paid invoices are not migrated by default; we migrate open invoices only and flag the customer's preference on historical invoice reporting.

Maximum Software Open AP Invoices map to Infor CloudSuite AP Invoice records. Vendor reference, invoice date, due date, and open amount transfer. Vendor lookup must be resolved in Infor before AP invoice insertion. Prepayments and credit memos in the AP file migrate as separate document types in Infor.

Maximum Software User records map to Infor CloudSuite User accounts. We resolve users by email address match against the Infor destination tenant. Any Maximum Software user without an Infor counterpart is held in a provisioning queue for the customer's admin to create before the migration continues. Role and permission mapping is out of scope for the data migration; we deliver a written role mapping inventory for the customer's implementation team.

Maximum Software location or site records map to Infor CloudSuite Warehouse. We flag any location with active inventory or open orders as a required warehouse in Infor. Locations without active data migrate as inactive sites. Multi-warehouse configurations require warehouse codes in Infor that match the source location identifiers for downstream inventory and order processing.

Maximum Software Open Sales Orders map to Infor CloudSuite Sales Order. We require Customer, Ship-to address, and Payment Terms to be resolved in Infor before order import. Line items require Item and UOM resolved. Order dates, quantities, and pricing transfer. Orders in Maximum Software with a status of Confirmed or Planned map to the equivalent Infor order status. Historical closed orders migrate selectively based on reporting needs, not by default.

Maximum Software Open Purchase Orders map to Infor CloudSuite Purchase Order. Supplier, ship-to location, and Payment Terms must be resolved in Infor before PO import. Line items require Item and UOM resolved. Expected receipt dates and quantities transfer. Purchase orders with expected receipts already posted in Maximum Software are flagged for partial receipt handling in Infor.

Maximum Software Bill of Materials records map to Infor CloudSuite BOM (or Recipe depending on the CloudSuite edition). Parent item, component items, quantities per, and BOM effective dates transfer. We flag BOMs with inactive component items for the customer's engineering team to clean up before import. BOMs with multiple routing versions map to Infor's BOM revision structure.

Maximum Software custom fields are inferred from the discovered table schema during the discovery phase. We map alphanumeric Maximum Software custom fields to Infor Custom Fields defined via CMS470 (Custom Field. Open) with field type A, numeric fields to type N, and date fields to type D. Custom Field Groups are created in CMS471 and linked via CMS472 to the relevant Infor objects. Maximum field lengths in Infor are 40 characters for alphanumeric and 15 for numeric; longer Maximum Software fields are truncated with a warning flag.