Migrate from Breeze ERP to Epicor Prophet 21

Breeze ERP customer records map to Epicor Kinetic Company. We extract the customer list via available CSV or HTML export, map the Breeze customer name to Company.Name, the Breeze billing address to Company.BillAddress, and the shipping address to Company.ShipAddress. If Breeze exposes a tax registration number field, it maps to Company.TaxID. We resolve the country code to the Epicor Country code table during transform. If Breeze stores multiple contacts per customer as separate rows, we create one Company and multiple Contact records linked via Company.CompanyNum.

Breeze ERP vendor records map to Epicor Kinetic Supplier. We extract the vendor list from the purchasing module, map the Breeze vendor name to Supplier.Name, payment terms to Supplier.PaymentTerms, and the GL account for AP to Supplier.APAccount. If Breeze exposes a vendor tax ID or GST registration, it maps to Supplier.TaxID. We flag any Breeze vendor that lacks a corresponding GL account in the Chart of Accounts export and escalate to the customer's Breeze administrator for resolution before migration.

Breeze ERP records that are pre-sale (quotation stage, no open orders) map to Epicor Kinetic Prospect. We identify these records by scanning the Breeze export for a status field indicating no posted invoices or open purchase orders. The Prospect object in Epicor Kinetic stores the same address and contact fields as Company, allowing the customer's sales team to convert the Prospect to a Company record upon first order.

Breeze ERP item records map to Epicor Kinetic Part. The Breeze item code maps to Part.PartNum; the item description maps to Part.SearchDescription and Part.LineDesc. Unit of measure from Breeze maps to Part.IUM (stocking UOM). We classify Breeze inventory items as Part.TypeCode = Stock or Part.TypeCode = NonStock based on the Breeze item type field. Non-inventory items (services, expenses) receive Part.TypeCode = NonStock with a warning flag for the customer to configure the procurement path in Epicor.

Breeze ERP items with alternate units of measure (case-pack, each, pallet) map to Epicor Kinetic PartUOM records. We extract the UOM conversion table from the Breeze inventory module, map each Breeze UOM code to an Epicor UOMCode in the UDTable, and create PartUOM records linking Part.PartNum to the alternate UOM with the conversion factor. If the Breeze UOM table is not exportable as a separate CSV, we infer UOMs from the item export rows and build the PartUOM set from the inference.

Breeze ERP item-warehouse assignments map to Epicor Kinetic PartPlant records. We extract the item-warehouse matrix from Breeze inventory exports, map the Breeze site or warehouse identifier to PartPlant.Plant, and copy reorder point, safety stock, and min-max fields. PartPlant.MinimumQty, PartPlant.MaximumQty, and PartPlant.MinOrderQty are populated from Breeze replenishment parameters if available in the export.

Breeze ERP BOM records map to Epicor Kinetic PartRev (BOM revision). We extract the BOM header and BOM line tables from the production or engineering module, map the Breeze BOM code to PartRev.RevisionNum, and the BOM description to PartRev.RevDescription. Each Breeze BOM line (component, quantity, scrap percent) maps to PartRev.ChildPartNum (the component Part) and PartRev.QtyPer. We align the Breeze BOM effective date to PartRev.EffectiveDate and the Breeze BOM status (active, draft, inactive) to PartRev.Approved.

Breeze ERP BOM component lines map to Epicor Kinetic PartMtl records within the PartRev. The Breeze component item code maps to PartMtl.MtlPartNum; the required quantity maps to PartMtl.QtyPer; the operation sequence number maps to PartMtl.AltMethod if the Breeze export includes routing. We flag any Breeze component that is not present in the Part import as a missing parent-record and hold those PartMtl rows for manual Part creation before resuming.

Breeze ERP work orders require a 1:N split into Epicor Kinetic Job records. Each Breeze work order header maps to a JobHead record with JobHead.JobNum, JobHead.PartNum (the manufactured part), JobHead.StartDate, JobHead.DueDate, and JobHead.JobEngineer (the assigned engineer). Breeze work order operations map to JobAsmbl records; Breeze material allocations map to JobMtl records. Open work orders receive JobHead.JobClosed = false; completed work orders receive JobHead.JobClosed = true with JobHead.JobComplete = true.

Breeze ERP production schedules map to Epicor Kinetic JobSched. We extract the schedule lines from the production module, map each scheduled date to JobSched.SchedDate, the scheduled quantity to JobSched.SchedQty, and the linked work order or job reference to JobSched.JobNum. If Breeze stores demand-driven schedules (MRP-triggered), we align the demand source to JobSched.DemandLink.

Breeze ERP Chart of Accounts entries map to Epicor Kinetic GLAccount. We extract the full account list via available exports, map the Breeze account code to GLAccount.Account, the account description to GLAccount.Description, and the account type to GLAccount.AccountType. Segment structure in Epicor GLAccount depends on the customer's Chart of Accounts configuration (1-5 segments), which we scope during discovery. We flag any Breeze account that does not map cleanly to an existing Epicor account type and deliver a GL mapping document for the customer's Epicor administrator to resolve before journal entry migration.

Open AP and AR balances at cutover migrate as APInvoice and ARInvoice records in Epicor Kinetic rather than as aged trial balances. We extract open AP from the Breeze vendor invoice list, map each open vendor invoice to APInvoice with APInvoice.VendorNum resolved to the Supplier record created in the supplier migration phase. Open AR migrates similarly to ARInvoice with CustomerNum resolved to the Company record. We preserve the original invoice date, due date, and open amount. Post-migration reconciliation compares the sum of APInvoice open amounts against the Breeze cutover AP report.

Breeze ERP project records map to Epicor Kinetic Project. We extract the project master, project assignments, and project time entries from the project management module. Project.ProjectID maps to Project.ProjectID; Project.Description maps to Project.Description; Project.Status maps to Project.Status. Project phase budgets and WBS structure map to ProjPhase and WbsPhase respectively. Time entries map to LaborDtl with LaborDtl.ProjectID and LaborDtl.JobNum linked.

Breeze ERP project labor assignments map to Epicor Kinetic LaborDtl records linked to the Project. The Breeze employee or resource assignment maps to LaborDtl.EmployeeNum; the hours worked to LaborDtl.LaborHrs; the work date to LaborDtl.PayDate. We resolve the LaborDtl.ProjectID to the Project record created in the project migration phase and LaborDtl.JobNum if the assignment is tied to a job. Project billing rates migrate to PrjProjResp if the Breeze export includes billable rate information.

Breeze ERP quality inspection results map to Epicor Kinetic QAGrp if the destination Epicor tenant includes the Quality Management module. The Breeze inspection lot or batch identifier maps to QAGrp.InspectionGRN or QAGrp.LotNum; the test result (pass/fail) maps to QAGrp.InspPlan (linked) and the individual test results to QAGrp.QACharValue. We flag any Breeze quality record that references a part not yet migrated as a missing parent-record.

Breeze ERP user or owner records map to Epicor Kinetic User. We extract the user list from the Breeze user administration module, map the Breeze username or email to User.ID, and the user's display name to User.Name. If the Breeze export includes a role or permission level, we map it to an Epicor Kinetic Plant and Company access scope. Epicor Kinetic user provisioning requires the customer's Epicor administrator to assign the appropriate license tier before migration; we provide a user-role mapping document listing each Breeze user, their Epicor role recommendation, and the corresponding license tier.

Breeze ERP extended properties or custom fields on any object map to Epicor Kinetic UDColumn (user-defined fields) on the corresponding table. We identify all non-standard Breeze fields during discovery, map each Breeze field name and data type to an Epicor UDColumn with matching data type (character, integer, decimal, date). If the Breeze custom field is a dropdown, we replicate the value set as an Epicor ComboBox or List field. Epicor UDColumn fields use a UDF-prefixed naming convention that we apply consistently across all migrated custom fields.