Migrate your mybizz erp data

MyBizz ERP exposes a built-in Inventory Items export accessible via Dashboard > Menu > Inventory > Items > Export. We pull this as the primary dataset for stock migrations and map SKU, description, unit cost, and quantity fields to the destination Items or Products object.

Customer records include contact name, company, email, and phone. We map these to the destination Customers or Contacts object, flagging any custom fields that do not have a direct equivalent in the target schema.

Vendor data is migrated as a distinct entity in MyBizz ERP. We map vendor name, contact details, and payment terms to the destination Vendors or Suppliers object, reconciling naming differences between systems.

Account codes and names are migrated to the destination Chart of Accounts. We handle hierarchical account structures by preserving parent-child relationships during the import sequence.

Invoice records include line items, amounts, dates, and customer references. We map these to the destination Invoices or Bills object, preserving status (paid/unpaid) and linking to the correct customer record.

Quotes are migrated as standalone documents with line items and expiration dates. We map them to the destination Quotes or Estimates object and flag any status fields that may not transfer automatically.

Payment transactions are linked to invoices and customers. We map payment date, amount, and payment method to the destination Payments or Bank Transactions object, reconciling against the corresponding invoice.

Booking records from MyBizz ERP include service date, customer reference, and booking status. We map these to the destination Bookings or Jobs object, flagging any custom status values that require explicit mapping.

Expense records include vendor, amount, category, and date. We map these to the destination Expenses or Bills object, preserving expense category assignments.

Lead records include contact information and lead status. We map these to the destination Leads or Contacts object depending on the destination system's object model.