Migrate from Breeze ERP to Infor CloudSuite Corporate

Breeze ERP Customer and Company records map to Infor CloudSuite Customer. The primary key from Breeze (customer code) maps to Infor CustomerId, and the customer name, address, contact details, and payment terms transfer to Infor's Customer form fields. We resolve any duplicate customers (same legal name, different site codes) during scoping and flatten them into a single Customer with multiple Ship-To addresses in Infor. Breeze's customer-specific pricing and discount structures become Infor Customer Price Codes requiring post-migration configuration.

Breeze ERP Vendor master records map to Infor CloudSuite Supplier. Vendor code, name, address, bank details, and payment terms transfer directly. We flag any Vendor records with active Purchase Orders at cutover because the PO header and line references must resolve to the newly created Supplier ID during import. Open PO balances carry forward as AP liability records in Infor's AP register.

Breeze ERP Items (both inventory SKUs and non-inventory products) map to Infor CloudSuite Item Master. The item code, description, unit of measure, and cost structure transfer. We handle the unit-of-measure conversion table explicitly because Breeze and Infor use different UOM naming conventions. Inventory quantities at cutover map to Infor's on-hand inventory records tied to the relevant warehouse and site.

Breeze ERP BOM records map to Infor CloudSuite Bill of Materials with component lines and routing steps. We extract the BOM header (item code, revision, effective date) and component lines (component item, quantity per, scrap percent) from Breeze exports and map them to Infor's BOM structure. Multi-level BOMs require parent-child resolution across the import sequence. The customer chooses whether to migrate BOM revision history or only the current active revision based on cutover scope.

Breeze ERP Work Orders map to Infor CloudSuite Production Orders. We extract Work Order header (WO number, item to manufacture, quantity, status, scheduled dates) and component issue and labor booking lines. Open work orders (Released, In Process status) migrate with their component allocations and operation routing. Closed work orders migrate as historical records with actuals preserved for costing audit. Work order dependencies on multi-level BOMs resolve against the BOM mapping in the preceding step.

Breeze ERP Chart of Accounts maps to Infor CloudSuite GL Account Code structure. This is the most critical mapping in the migration because every journal entry, AP invoice, AR invoice, and inventory transaction references an account code. We extract the full account hierarchy (account code, description, type, sub-type, parent account) from Breeze exports and configure the corresponding Infor account structure before any transactional records move. We flag accounts with zero balances, accounts used only in prior periods, and accounts with non-standard types for customer review before activation.

Open Accounts Payable records from Breeze ERP at cutover date map to Infor CloudSuite AP Vouchers. We extract vendor invoice number, vendor code, invoice date, due date, invoice amount, and account distribution lines. Each AP Voucher references the Supplier ID resolved from the Vendor mapping step. Prepayments and credit memos migrate as separate AP documents with their own reference chains. Post migration, the customer's AP team reconciles the Infor AP register against the Breeze AP aging report as the cutover validation step.

Open Accounts Receivable records from Breeze ERP at cutover date map to Infor CloudSuite AR Invoices. We extract customer invoice number, customer code, invoice date, due date, invoice amount, and account distribution lines. Each AR Invoice references the Customer ID resolved from the Customer mapping step. Credit memos and down payments migrate as separate AR documents with their own reference chains. Post migration, the customer's AR team reconciles the Infor AR register against the Breeze AR aging report.

Breeze ERP Project records map to Infor CloudSuite Project. We extract project header (project code, name, status, start date, end date, customer reference) and project assignments (resources, time entries, expense entries). Project-specific revenue recognition settings, billing schedules, and WBS structures require explicit scoping because they vary significantly by project type and industry. Projects with open purchase orders and subcontracts carry those references forward and resolve against the Supplier and PO mappings.

Breeze ERP inventory transaction history (receipts, issues, transfers, adjustments) maps to Infor CloudSuite inventory transaction records. We extract transaction date, item code, warehouse, quantity, cost, and reference document. Historical transactions older than 24 months may be migrated as summary records rather than line-by-line based on scoping agreement, because full transactional history migration significantly increases migration time without proportionate business value. Current on-hand quantities at cutover date are the priority migration.

Breeze ERP Users referenced on transactions, work orders, and projects map to Infor CloudSuite Users. We resolve by email match where possible. Breeze role and permission structures do not map directly to Infor's role-based security model; we deliver a role matrix document that maps each Breeze role to the nearest Infor functional role for the customer's admin to configure post-migration. Users without email matches go to a reconciliation queue for manual provisioning.