Migrate from mybizz erp to Infor CloudSuite Corporate

MyBizz ERP Chart of Accounts records with account code, name, and type map to Infor CloudSuite Financial Management account structures. We preserve the hierarchical parent-child relationships that MyBizz ERP supports and reconstruct them in Infor using the account code pattern. This must be the first object loaded because Invoices, Payments, and Expenses all reference account codes; the import sequence matters here.

MyBizz ERP Inventory Items export via Dashboard > Menu > Inventory > Items > Export maps to Infor CloudSuite Item master with SKU, description, unit of measure, cost, and stock levels. We transform the export into Infor's Item staging table format, resolving UOM mappings and any multi-site warehouse assignments. Inventory valuation method from MyBizz (standard cost, FIFO, etc.) maps to Infor's item costing configuration.

MyBizz ERP Customer records map to Infor CloudSuite Business Partner with type = Customer. Contact name, company, email, phone, billing address, and payment terms transfer to the BP contact and address forms. We create the BP header before any related transaction records (Invoices, Quotes, Payments) so that the Business Partner lookup is satisfied at load time.

MyBizz ERP Vendor records map to Infor CloudSuite Business Partner with type = Supplier. Vendor name, contact details, payment terms, and bank information transfer. Vendor records must load before any Expenses or Payments referencing them, maintaining the same dependency discipline as Customer records before Invoices.

MyBizz ERP Invoice records with line items, amounts, dates, customer reference, and paid/unpaid status map to Infor CloudSuite Accounts Receivable invoice documents. We preserve the invoice status, payment terms, and link each invoice to the resolved Business Partner record. Closed invoices (paid) land as posted transactions; open invoices land with the correct balance due.

MyBizz ERP Quotes map to Infor CloudSuite Quotations with line items, quantities, pricing, and expiration dates preserved. Status fields (Draft, Sent, Accepted, Lost) from MyBizz transfer to Infor quotation status, and any custom status values become free-text notes. Quotations do not auto-convert to orders in Infor; the customer decides whether to convert manually post-migration.

MyBizz ERP Payment records linked to invoices map to Infor CloudSuite payment documents. We reconcile payment date, amount, payment method, and the linked invoice reference. Payments applied against invoices reconcile the AR balance in Infor, producing a consistent open-invoice aging report post-migration.

MyBizz ERP Booking records with service date, customer reference, and status map to Infor CloudSuite Service Management bookings or jobs depending on the CloudSuite edition deployed. Custom status values from MyBizz do not have direct Infor equivalents; we document each custom status and recommend the Infor status that best matches the operational intent, with manual review before the final load.

MyBizz ERP Expense records with vendor, amount, category, and date map to Infor CloudSuite expense or AP bill documents. We preserve the expense category assignment and link the expense to the resolved Vendor Business Partner. If MyBizz ERP uses expense categories not present in Infor's standard list, we document them for the customer's admin to configure post-migration.

MyBizz ERP Lead records map to Infor CloudSuite Lead or Prospect depending on the CloudSuite edition's sales management module. Contact name, email, phone, lead source, and any lead score from MyBizz transfer to corresponding Infor fields. We flag any custom lead status values that require mapping to Infor's status picklist before the load proceeds.

MyBizz ERP custom fields for Customers, Vendors, Inventory Items, and other objects may not be exposed in the standard export format. We perform a pre-migration field audit with the customer to identify all custom fields, determine which MyBizz export format includes them (standard export vs extended JSON), and create explicit mapping rules for each. Custom fields that have no direct Infor equivalent are documented with recommended Infor field types and noted as requiring manual post-load validation.