Migrate from Flectra to Epicor Prophet 21

Flectra's res.partner records flagged is_company=true map to Epicor Customer. The Flectra partner name becomes Customer.CustID (short code) and Customer.Name. We resolve the parent-child relationship so that Flectra child contacts under a company map to Epicor Contact records linked to the Customer via CustomerNum. VAT number from Flectra's vat field maps to Customer.TaxPayerID. Website maps to CustomerTerritory reference if Territory management is active.

Flectra contacts flagged is_company=false map to Epicor Contact. Name, email, phone, street, city, state, zip, country map to Contact fields. The parent_id relationship to the company res.partner resolves to the Epicor CustomerNum linkage. Multiple addresses per Flectra contact map to ContactAddress records. If Flectra contact has no email, we set Contact.PerConOK=false per Epicor validation.

Flectra sale.order maps to Epicor OrderHed. Order date, customer reference, and fiscal position carry across. The Flectra sale.order.state (draft/confirmed/done/cancel) maps to Epicor OrderHed.OpenLine and OpenRelease flags; confirmed orders set OrderHeld=false. The currency_id maps to OrderHed.CurrencyCode, and the Flectra pricelist_id determines the Epicor PriceLstCode for line pricing.

Flectra sale.order.line maps to Epicor OrderDtl. Product, quantity, unit of measure, unit price, and tax map across. The Flectra product.product variant ID resolves via SKU to Epicor PartNum. If Flectra used product.template (master product) with no variant, we look up the default variant in Epicor or create a PartMaster placeholder during migration. Discount percent and amount map to OrderDtl.DiscountPercent and DiscountAmount.

Flectra account.move with move_type=out_invoice maps to Epicor InvcHead. Invoice number, date, due date, partner, and amount transfer. Flectra's payment_state (posted/pending) maps to InvcHead.InvoiceType and InvcHead.Settled=false. Line items map to InvcDtl with PartNum resolved via SKU lookup. Flectra's analytic tag lines (account AnalyticAccount mapping) translate to Epicor InvcDtl.ExtMtlUnitCost for cost-accounting visibility if the target Epicor org uses Project Costing.

Flectra product.template maps to Epicor Part (the product master). The Flectra product_type (consumable/storable/service) maps to Part.TypeCode. Default code, sales description, list price, standard cost, and the template's product_category map to Part.ClassID via a PartClass pre-created in Epicor. The x_ prefixed custom fields on product.template migrate as Part UD (User Defined) fields we pre-create in Epicor UD Column Map.

Flectra product.product variants under a product.template split into multiple Epicor PartPlant records (one per Flectra variant). The variant attributes (size, colour, dimension) from Flectra attribute_line_value map to Epicor PartDim dimensions if PartDim tracking is enabled, or to Part character UD fields. The template's standard price and cost inherit to each PartPlant row, overridable per site. We resolve the Flectra template-to-variant relationship during the split so that no variant is orphaned.

Flectra purchase.order maps to Epicor POHeader. Vendor partner (supplier), order date, and payment terms map across. The Flectra purchase.order.state maps to Epicor POLine.OpenRelease flags. Vendor part number from Flectra purchase.order.line.vendor_part_number maps to PODetail.VendorPN if present.

Flectra purchase.order.line maps to Epicor PODetail. Product, ordered quantity, unit of measure, and unit cost transfer. The Flectra product SKU resolves to Epicor PartNum. Receipt status flags from Flectra (from done state) map to PODetail.ReceivedQty tracking. Line taxes map to PODetail.TaxExempt and TaxCatID.

Flectra project.project maps to Epicor Project (ProjectMgmt module or PSA depending on Epicor edition). Project name, date, and stage status transfer. The Flectra analytic_account_id links to Epicor's Project Phase and WBS structure. If the customer uses Epicor's Project Billing module, Flectra's project billing rules map to Epicor billings groups. We note that Flectra's project.timesheet and project.milestone are not native Epicor Project objects and require manual rebuild or Project BPA configuration.

Flectra project.task maps to Epicor Task linked to the Project. Task name, planned hours, effective hours, stage, and user_id (assignee) transfer. Sub-tasks nested via Flectra's child_ids relation map to Epicor Task.ParentTaskNum. Task state maps to Epicor Task.TaskStatus. Assignee resolves via email match to Epicor User.

Flectra hr.employee maps to Epicor Employee. Name, department, job title, work email, and phone transfer. Flectra's department_id resolves to Epicor Employee.Dept if the target Epicor company has HRM module active. Bank account and salary history remain in Flectra's payroll module and do not migrate; we flag these as HR module objects requiring manual payroll rebuild in Epicor HCM.

Flectra binary attachments in ir.attachment export as base64-encoded files. We re-attach in Epicor as DocumentRef records linked to the parent entity (OrderHed, InvcHead, Part) via DocType and DocKey. If the Epicor org uses Epicor Docs (formerly EDMS), attachments link via DocType and the corresponding DocLink. We flag any attachment exceeding Epicor's maximum file size and deliver those as a separate archive package.

Flectra custom fields defined via ir.model.fields with state='manual' enumerate during discovery and pre-create in Epicor UD Column Map (UD01-UD10 or table-specific UD columns). We map each x_ prefixed field to the equivalent Epicor UD column, apply the same data type (character, date, decimal, integer, checkbox), and flag any Flectra custom field with no clear Epicor UD analog as requiring a gap analysis before migration load.