Migrate your BizAutomation Cloud ERP data

Organizations represent the customer/company records in BizAutomation's CRM layer. Standard fields map cleanly to Accounts in most destination CRMs. We export Organization name, type, address, and associated Contacts as a grouped record set to preserve the parent-child relationship during migration.

Contacts link to Organizations and carry standard fields: name, email, phone, address, and lifecycle stage. We map these directly to Contacts or Leads in the destination system and flag any custom Contact properties for field-level mapping review.

The GL Chart of Accounts defines the complete account structure for all financial modules. We export the full account list including account type, number, name, and parent hierarchy. This must be imported before any transactional data so destination GL references are valid.

Vendor records include company name, contact info, payment terms, and address. We export all vendor data before purchase orders to maintain referential integrity. Vendors map to the equivalent object in most destination ERP systems.

Inventory Items include SKU, description, cost, price, warehouse location, and quantity-on-hand. Custom item properties and matrix items with variant attributes require field-level mapping. We flag serial/lot number tracking settings that may not exist in the destination system.

Sales Orders link Customers, Inventory Items, pricing, and shipping rules. We export open and historical orders, but document states and custom workflow statuses often require value mapping. Line item detail is preserved but custom order-level fields need review.

Purchase Orders map similarly to Sales Orders but against Vendors. Historical PO records carry financial obligations that must land with matching vendor accounts in the destination. We preserve PO status and expected delivery dates as metadata fields.

Shipment records represent fulfillment events tied to Sales Orders. We export shipment date, carrier, tracking number, and linked order. Where the destination system uses a different fulfillment object model, we map Shipment details into the corresponding order's shipping fields.

Projects in BizAutomation span the PSA module and cover tasks, time entries, and contract billing. Project status, start/end dates, and assignees export cleanly, but custom project fields and milestone definitions require value-level mapping to the destination schema.

Billable time contracts track sold hours against project tasks and activities. We export contract type, value, remaining hours, and linked project references. Contract line items with rate schedules need field-level review as destination PSA systems vary in how they model contract billing.

Activities represent the engagement history on Organizations and Contacts — calls, emails, tasks. We export activity type, date, owner, and linked record. Custom activity types and notes require mapping to the destination's engagement object model.

Opportunities in BizAutomation track pipeline deals against Organizations. Stage, amount, probability, close date, and owner export cleanly. Custom pipeline stages in BizAutomation may not map 1:1 to destination pipeline stages, requiring stage-name mapping during import.

Orders originating from Shopify, BigCommerce, WooCommerce, Magento, or EDI marketplaces flow into BizAutomation via the multi-channel integration. These carry the same structure as standard Sales Orders but with an additional channel source field. We preserve the channel attribution in a custom field on the destination order.