Migrate from BizAutomation Cloud ERP to Infor CloudSuite Corporate

BizAutomation Organizations map to Infor CloudSuite Customer records at the header level, with the organization's name, type, address, and payment terms carried forward. Each Organization's linked Contacts export as separate Infor Contact records linked to the Customer via CustomerId. We use the organization's primary email domain as a dedupe key during import. Multi-entity Organizations in BizAutomation map to parent-child Customer structures in Infor CloudSuite using the same hierarchy. This mapping requires BizAutomation database credentials scoped to the Organizations and Contacts tables, and we resolve the Contact-Organization relationship at migration time using the BizAutomation contact.organization_id foreign key.

BizAutomation Contacts map directly to Infor CloudSuite Contact records. Standard fields (name, email, phone, address, title) migrate cleanly. Custom contact properties and lifecycle stage fields require field-level mapping review against the Infor CloudSuite Contact schema because BizAutomation supports user-defined contact fields that may not have a direct Infor equivalent. We flag any unmapped custom properties as fields requiring Infor administrator configuration before the Contact phase begins.

BizAutomation's GL Chart of Accounts is the first object exported because all financial modules depend on it. Account number, name, type (asset, liability, equity, revenue, expense), and parent hierarchy migrate to Infor CloudSuite GL Account records. We use Infor's recommended account-number format and preserve the account-type classification used in BizAutomation. Inter-company account structures in BizAutomation multi-entity configurations map to Infor CloudSuite's inter-company account structure. This phase must complete before any Vendor, Customer, or Order imports because Infor validates account references on transactional records.

BizAutomation Vendor records map to Infor CloudSuite Vendor. Each Vendor carries company name, contact information, payment terms, and address data that maps directly. We resolve the default expense account reference from the BizAutomation vendor.default_expense_account field to the corresponding Infor GL Account during import. PO-linked Vendors must import before Purchase Order records so that VendorId references are satisfied at the time of PO insertion.

BizAutomation Inventory Items map to Infor CloudSuite Item Master records. Standard item attributes (SKU, description, cost, price, warehouse location, quantity-on-hand) migrate to Infor item fields. However, BizAutomation custom item properties require field-level mapping against the Infor CloudSuite Item schema. Matrix items are the most complex mapping: BizAutomation matrix items generate child SKU records dynamically from parent attribute definitions. We export the parent item template first, then reconstruct each child SKU as a separate Infor Item record with the correct attribute assignment based on the BizAutomation matrix_child_items table. This transformation is scripted and validated against a sample before bulk import.

BizAutomation Sales Orders map to Infor CloudSuite Sales Order records. Each order links a Customer (from the Organizations export), line items (from the Inventory Items export), pricing, and shipping rules. We export open and historical orders, but document the status mapping from BizAutomation order states to Infor Sales Order statuses during scoping. Line item taxes, discounts, and freight charges require field-level mapping because BizAutomation stores these as separate fields while Infor may store them in distinct invoice-breaking structures. We flag custom order workflow statuses as requiring value-mapping configuration in Infor before the migration phase.

BizAutomation Purchase Orders map to Infor CloudSuite Purchase Order records. They mirror the Sales Order mapping structure but against Vendors instead of Customers. Historical PO records carry financial obligations that must land with matching Vendor accounts in Infor CloudSuite. We preserve PO status (open, received, closed, cancelled) from BizAutomation and map to the corresponding Infor Purchase Order status values. PO approvals and custom workflow statuses require configuration in Infor before import.

BizAutomation Shipment records represent fulfillment events tied to Sales Orders, carrying shipment date, carrier, tracking number, and linked order reference. We export these as Infor Shipment records linked to the corresponding Infor Sales Order. Where Infor CloudSuite uses a different fulfillment object name (varies by industry suite), we configure the mapping during scoping. Tracking numbers and carrier data migrate as text fields on the shipment record.

BizAutomation Projects (from the PSA module) span tasks, time entries, and contract billing. Project status, start and end dates, and assignee references migrate to Infor CloudSuite Project records. Custom project fields, milestone definitions, and project-specific billing rules require field-level mapping because BizAutomation's PSA schema varies significantly from Infor's project management module. We flag any BizAutomation project-level custom fields as requiring Infor Project administrator configuration before migration.

Billable time contracts in BizAutomation track sold hours against project tasks and activities. Contract type, value, remaining hours, and linked project references export to Infor CloudSuite Contract or Service Contract records depending on the CloudSuite suite in use. Contract line items with rate schedules require mapping to Infor's billing line structure. We flag rate-schedule discrepancies during scoping because BizAutomation and Infor handle tiered billing rates differently.

BizAutomation Activities (calls, emails, tasks, meetings) represent engagement history on Organizations and Contacts. Activity type, date, owner, and linked record reference migrate to Infor CloudSuite Activity or CRM Activity records. Custom activity types and notes require mapping review because BizAutomation supports user-defined activity classifications that may not match Infor's activity schema. We resolve the activity owner by matching the BizAutomation owner email to the corresponding Infor User record.

BizAutomation Opportunities track pipeline deals against Organizations. Stage, amount, probability, close date, and owner export to Infor CloudSuite CRM Opportunity records. Custom pipeline stages in BizAutomation require mapping to Infor's Sales Process stages because the stage value sets differ between platforms. We build the stage mapping table during scoping and configure the Infor Sales Process stages before Opportunity migration begins. Probability percentages round to Infor's supported granularity.