Migrate from mybizz erp to Epicor Prophet 21

MyBizz Customer records map to Epicor ERP Account (company level) and child Contact records. The MyBizz customer code maps to Epicor Customer.CustID, company name to Account.Name, and the primary contact fields to the Account's default Contact record. We evaluate during discovery whether the MyBizz Customer carries multiple contact persons that warrant separate Contact records under the Account. Address, phone, and email from MyBizz become the Account's Primary ShipTo and email fields. Account must be inserted before any downstream document (Invoice, Quote, Payment) that references it.

MyBizz Inventory Items map to Epicor ERP Part master with PartPlant (site-level stocking) and PartWhse (warehouse-level quantity) records. The MyBizz SKU maps to Part.Number, description to Part.Description, and unit of measure to Part.IUM. On-hand quantity from MyBizz becomes PartWhse.OnHandQty against the default site. Epicor enforces a Part Plant record for every Part-Site combination where stock is held; we create PartPlant records for each MyBizz inventory site identified during discovery. MyBizz custom fields on inventory items require explicit mapping to Epicor UD (user-defined) fields on Part, which must be configured before Part import begins.

MyBizz Vendor records map to Epicor ERP Supplier (AP Supplier) or Subcontractor records. Vendor name and code map to Supplier.VendorID and Supplier.Name respectively. Payment terms from MyBizz reconcile against Epicor's PaymentTerm lookup table, and the vendor's contact and address fields map to Supplier records. Vendor dependencies must be resolved before any Expense or AP document migration because Epicor enforces referential integrity on SupplierID for AP transactions.

MyBizz Chart of Accounts account codes and names migrate to Epicor GL Account records, preserving parent-child hierarchical structure in Epicor's account tree. The critical reconciliation point is MyBizz account type mapping to Epicor GL Account Category: MyBizz does not enforce strict account type classification, but Epicor requires a Category value (Asset, Liability, Equity, Revenue, Expense) for posting controls. We work with the customer's finance team during scoping to assign category values to each MyBizz account before migration, as this determines which accounts accept AR/AP/GL postings in Epicor.

MyBizz Sales Invoices map to Epicor ERP InvoiceHead (header) and InvoiceDtl (line) records. The MyBizz invoice number becomes InvoiceHead.InvoiceNum, customer reference resolves to InvoiceHead.CustNum (the Epicor Customer ID), and line items map to InvoiceDtl with PartNum, Quantity, UnitPrice, and Tax code. MyBizz invoice status (paid, partial, outstanding) maps to Epicor InvoiceHead.InvoiceStatus. Paid invoices receive a corresponding Cash Receipt record linked via InvoiceHead.InvoiceNum. We preserve the original MyBizz invoice date and payment date for audit trails.

MyBizz Quotes map to Epicor ERP DemandQuote with QuoteHed (header) and QuoteDtl (line) records. The MyBizz quote number maps to QuoteHed.QuoteNum, customer reference to QuoteHed.CustNum, and line items to QuoteDtl with PartNum, Quantity, UnitPrice, and expiration date. MyBizz quote status (active, expired) maps to QuoteHed.QuoteStatus values, and any custom pricing or discount fields migrate to QuoteDtl.DiscountPercent or custom QuoteDtl fields. Active quotes must migrate before any converted Sales Orders; expired quotes land in a separate QuoteStatus for reporting.

MyBizz Bookings map to Epicor ERP Job (production order) records with JobOper (operations) and ProjectMtl (material) lines as applicable. The MyBizz booking number becomes Job.JobNum, customer reference resolves to Job.QuoteNum or Job.OrderNum, and the service date maps to Job.StartDate. MyBizz resource assignments and booking details translate to JobOper records with ResourceGrp and LaborEntry flag assignments. Custom status values from MyBizz Bookings require explicit mapping to Epicor Job status values during discovery. Epicor's full job costing, scheduling, and MES depth may require tier-gated module activation before these records can be inserted; we verify edition scope during scoping.

MyBizz Customer Payments map to Epicor ERP Cash Receipt records linked to the corresponding AR Invoice. Payment date, amount, and payment method migrate to CashReceiptHead, with CashReceiptHead.InvoiceNum linking to the migrated Invoice record. Payment method from MyBizz maps to Epicor PaymentMethod. Unallocated or overpayment amounts migrate as CashReceiptHead.OverpaymentAmt. This object depends on Invoice migration being complete because Epicor requires the InvoiceNum reference for allocation.

MyBizz Expense records map to Epicor ERP AP Invoice records linked to the Vendor/Supplier, or to Expense Report records if the customer uses Epicor's expense approval workflow. The vendor reference resolves to Supplier.VendorNum, expense amount and category map to AP Invoice line amounts and the Expense Category lookup, and date preserves the original MyBizz entry date. MyBizz expense category assignments reconcile against Epicor's Expense Category list during discovery. Epicor's multi-level approval workflow and per-diem rules for expense records are not set up during migration; these are configured by the customer's Epicor admin post-migration.

MyBizz Lead records map directly to Epicor ERP Lead records with contact name, company, email, phone, and lead status preserved. The MyBizz lead status maps to Epicor LeadStatus values, and any lead score or source data migrates to custom Lead fields if the customer requests them. Destination-side status (whether the customer qualifies leads into Epicor CRM Contacts or keeps them as Leads for an SDR team) is a scoping decision made with the customer's admin before migration begins.

MyBizz ERP supports custom fields on certain objects, but the platform's export utility may not expose all custom field values in the standard export format. We perform a pre-migration field audit with the customer to identify every custom field, determine which export format includes the values, and create explicit mapping rules for each. Custom fields from MyBizz map to Epicor User-Defined (UD) fields on the equivalent Epicor object. UD fields must be configured in Epicor (via the desktop classic client per Epicor documentation) before the corresponding data import begins. This is a configuration step the customer must complete or authorize their Epicor partner to complete before migration day.

MyBizz ERP customers with inventory or multi-location data may have site or warehouse distinctions that do not have a direct Epicor equivalent until Sites and Warehouses are configured. We identify every distinct location, branch, or warehouse code in the MyBizz export and map each to an Epicor Plant/Site and associated Warehouse record. Site must be created in Epicor before PartPlant records that reference it can be inserted. This is a prerequisite configuration step that runs in parallel with the data mapping design and must be complete before inventory data migrates.

MyBizz Payment Terms (Net 30, Net 60, COD, etc.) used across Invoices, Quotes, and Vendors map to Epicor PaymentTerm records. We extract the distinct PaymentTerm values from the source export, reconcile them against the standard Epicor PaymentTerm list, and create any custom PaymentTerm records required before any document import begins. This lookup must resolve before Invoice and Expense migration because Epicor enforces referential integrity on PaymentTerm for AR and AP documents.

MyBizz User and Owner records referenced on Customers, Vendors, Invoices, and Bookings map to Epicor ERP User accounts. We resolve MyBizz owner email against the Epicor User list during migration scoping. Any MyBizz Owner without a matching Epicor User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. OwnerId references on Invoices, Quotes, and Jobs are required in Epicor, so User provisioning is a hard dependency before document migration begins.