Migrate from Farvision ERP to Microsoft Dynamics 365 Business Central

Farvision Projects spanning Land Acquisition, Legal and Liaison, Pre-Sales, Post-Sales, Budgeting, and Execution map to D365 Project records (Finance and Supply Chain Management) or Job records (Business Central). We preserve the project lifecycle phase as a project category and the project-specific financial segregation by mapping Farvision's project-account associations to D365 Financial Dimensions so that every transaction posts to the correct dimension rather than a flat account code. This is the highest-priority mapping because downstream billing and inventory records reference it.

Farvision Customer records from the CRM module map directly to D365 Customer records. Customer properties, addresses, and contact details transfer as Customer address and contact roles. Custom fields on Farvision Customer records map to D365 custom fields on the Customer entity. Customer is a required parent for all sales and billing records, so it is migrated second after project setup validation.

Farvision Property records tied to specific Projects represent sellable inventory units. We map these to D365 Item records with the item type set to Product. Project-to-property associations migrate as Item dimension references linking each unit to the originating Project. Booking status, floor plan details, and unit specifications transfer as custom fields on the Item record. If the customer licenses the Real Estate Management module, these map to the Property entity instead.

Farvision generates Sales Orders tied to specific Properties and Customers. These map to D365 Sales Order lines linked to the Customer and Item (Property). Booking status from Farvision becomes the Sales Order status workflow. If Farvision Sales Orders represent pre-project bookings that convert to invoiced milestones, we map them to D365 Project Sales Agreements or Contracts for chargeable project billing. The customer and property references resolve at migration time through the Customer and Item lookups.

Farvision Contracting records capture the legal booking between a buyer and a property unit with payment schedule milestones. We map these to D365 Sales Agreement (general) or Project Contract (if Project Management is licensed). Each payment milestone becomes a Sales Agreement release line or Project Contract line. The original booking date and booking amount transfer as header fields for audit.

Farvision Client Billing records with installment milestones map to D365 Sales Invoice lines or Project Invoice proposals. Payment milestone status (paid, pending, overdue) migrates as invoice status. We preserve the full billing history including partial payments and adjustments, and flag post-migration reconciliation for the accounting team because D365's posted invoice records have different numbering sequences. Installment schedules map to D365 payment terms on the Customer record.

Farvision inventory management covering materials, procurement, and stock tracking requires schema mapping because unit-of-measure conventions and custom inventory fields vary. We extract item master records with current stock levels, reorder points, and vendor associations, then map to D365 Items with the appropriate product type (Item, Service, or Bundle). Open purchase orders migrate as D365 Purchase Orders. Warehouse locations map to D365 inventory dimensions for location-specific tracking.

Farvision HR and Payroll covers the Employee Life Cycle including hiring, compensation, and benefits. These map to D365 Human Resources Worker records or Employee records (Business Central). Compensation history with effective dates migrates to D365 compensation structures, though we flag effective-dated payroll records for manual verification post-migration because D365 HR uses different benefit enrollment and payroll calculation engines. Employee照片 and documents transfer as attachments to the Worker record.

Farvision Activity records and grouping functionality document project-related tasks, site visits, and stakeholder interactions. D365 does not have a direct equivalent Activity object for ERP; project activities map to Project Journal lines or SmartList entries. We preserve the activity description, date, and group association as a project journal comment or tagged SmartList record, and flag that activity timeline is not a native D365 ERP feature (it is a CRM feature in D365 Sales and Customer Service).

Farvision Payment Types Master is a configurable entity defining how customers can pay (cheque, bank transfer, credit, installment). These map to D365 Payment Terms (due date rules) and Payment Methods (instrument types) configured in Accounts Receivable. We preserve the payment type definitions and associate them with Customer records during migration so that billing records inherit the correct payment terms automatically.

Farvision Places Management stores location data with country and state hierarchies that apply to properties, sites, and project sites. D365 stores geographic data as address records on entities (Customer, Vendor, Project). We flatten the Farvision nested location tree into D365 address format, mapping country and state to the standard address structure. Site-specific locations for inventory or project phases map to D365 warehouse or project site references.

Farvision Engineering module covers Quantity Surveying and billing calculations for real estate construction. These industry-specific data structures map to D365 Project Quotations for billable engineering work or to Item Cost records for material quantity tracking. We perform field-level mapping from Farvision QS fields to D365 project estimate line types and preserve the quantity take-off and rate data for post-migration reconciliation against D365 project cost budgets.

Farvision customization capabilities generate custom fields across objects in the CRM, Sales, and Post-Sales modules. We migrate custom field definitions and values explicitly, noting unsupported field types (Farvision-specific picklists without D365 equivalents) for manual remediation. Custom field API names in Farvision require transformation to D365 naming conventions (no spaces, alphanumeric only) during the mapping phase.