Migrate from Farvision ERP to Epicor Prophet 21

Farvision's Project records span Land Acquisition, Legal and Liaison, Pre-Sales, Post-Sales, Budgeting, and Execution phases. We map these to Epicor Job records with a Project Code cross-walk stored in a custom UD field (ud_project_code__c) and the project phase mapped to JobHead.JobType or a UD field. The Farvision project hierarchy (parent project with sub-projects) maps to Epicor Job records with a ParentJob field. Each phase in Farvision becomes a separate Epicor Job or Job Detail record linked to the parent project identifier.

Farvision Customer records in the CRM module map to Epicor Customer records. The customer name, address, contact details, and any custom fields migrate directly. Farvision's customer type classification (individual buyer, corporate buyer, investor) maps to Epicor's CustomerType field or a UD field. Customer is created before any related Property, Sales Order, or Invoice records so that the CustomerID reference is satisfied at insert time.

Farvision Property records representing sellable inventory units (apartments, plots, villas) map to Epicor Part records with the Part.TypeCode set to Stocked. The Farvision project association (which project the unit belongs to) becomes a UD field on Part linked to the Job record representing that project. Unit status (Available, Booked, Sold, Registered) maps to Part.SalesUM or a UD field for status tracking.

Farvision generates sales orders tied to specific properties and buyers. We map these to Epicor Order records with OrderHed and OrderDtl entries. The Farvision booking status (Token, Agreement, Registration) maps to Epicor OrderHed.OrderStatus. The linked Property Part number becomes the OrderDtl.OrderLine linked to the Part mapping. Buyer details link to the Customer record created from Farvision Customer.

Farvision Client Billing records including payment milestones and installment tracking map to Epicor AR Invoice records (InvcHead and InvcDtl). The billing history migrates with open and historical invoices separated: open invoices become Epicor InvcHead with InvoiceVendor references; historical invoices are migrated as closed records. The payment milestone structure (installment number, due date, amount) migrates to InvcDtl lines with a custom UD field for installment tracking.

Farvision Activities and Activity Groups map to Epicor Activity records. The activity type (Call, Meeting, Task, Note) maps to Epicor Activity.TypeCode or a UD field. Activity groups in Farvision map to Epicor Activity.ActivitySchedulerID for grouping. Owner assignment migrates by resolving Farvision Owner to Epicor User by email match. We use Farvision's YouTube-documented import/export functionality to extract these records.

Farvision's Places Management stores location data with country and state hierarchy. We extract the full location tree and map it to Epicor's Country and State/Province records in the basic geography tables. The Farvision location code becomes the Epicor geographic reference. We preserve the full hierarchy for address validation and reporting.

Farvision's Payment Types Master is a configurable entity defining how buyers can pay (cheque, bank transfer, demand draft, online). We extract the configured payment types and map them to Epicor Payment Methods in the Cash Desk and AR modules. Custom payment type codes in Farvision map to Epicor PaymentMethod field on AR Invoice records.

Farvision inventory management covers materials, procurement, and stock tracking used in construction and facilities management. We map Farvision stock items to Epicor Part records with inventory tracked via PartWhse records. Unit-of-measure conventions in Farvision (sq ft, units, lots) map to Epicor UOM classes. The Farvision store location maps to Epicor Warehouse records. We flag any non-standard UOM conversions for manual verification.

Farvision's HR and Payroll module covers Employee Life Cycle Management. We migrate employee master records and basic compensation history to Epicor Employee and HR modules. Effective-dated payroll records are migrated as historical data with a flag for manual reconciliation by the accounting team against Epicor's payroll configuration. Farvision payroll calculations do not map to Epicor payroll as functional equivalents due to different compliance and tax frameworks.

Farvision's Engineering module covers Quantity Surveying and billing records specific to real estate construction cost tracking. These do not map directly to Epicor's BOM and Engineering Workbench designed for manufacturing bill of materials. We extract QS records as reference data in a custom UD table or CSV archive, and flag the engineering rebuild scope for the customer's Epicor admin. Epicor's BOM and MES modules are available in the destination for the admin to configure from scratch.

Farvision offers customization capabilities that generate custom fields across objects. We migrate custom field definitions and values explicitly as Epicor UD (User-Defined) fields. Each Farvision custom field type is mapped to the closest Epicor UD field type (UD01, UD02, string, number, date). We document unsupported field types for manual remediation if the field type has no Epicor equivalent.

Farvision's Budgeting module tracks project budgets by phase and cost head. We map these to Epicor JobPtn (Job Parts) and JobEstimates records for project cost tracking. The budget-to-actual comparison logic that Farvision handles natively requires Epicor Job Cost configuration. We deliver a budget mapping specification for the customer's Epicor admin to configure the Job Cost segment structure matching the Farvision budget heads.