Migrate from Farvision ERP to Infor CloudSuite Corporate

Farvision Projects spanning Land Acquisition through Post-Sales map to Infor Cloudsuite Industrial Business Units and Cost Centers. The project lifecycle stages (Land, Legal, Pre-Sales, Post-Sales, Budget, Execution) map to Cost Center hierarchies within the Business Unit. We extract the project-to-account-code crosswalk from Farvision's MongoDB documents and translate it into Infor's Cost Center structure during the discovery phase. Project milestones map to Milestone or Task records in Infor Cloudsuite Industrial with project-wise status tracking preserved.

Farvision CRM module Customers map to Infor Cloudsuite Industrial Business Partner records with role = Customer. We preserve all customer properties, contact details, and custom fields extracted from MongoDB, using email and phone as dedupe keys during import. Farvision's customer-specific pricing agreements map to Infor's Customer Price Agreement or Trade Agreement records. Customer financial standing and credit limits transfer to the Business Partner credit management fields.

Farvision Property records tied to specific Projects map to Infor Cloudsuite Industrial Item or Asset records. Project-to-property associations migrate as Item Warehouse records or Asset Project Links. We preserve unit type (apartment, villa, plot), floor, wing, area in sq ft, facing, and property status fields as custom fields on the Item or Asset record. Farvision's sold/unsold/blocked status maps to Infor's Item or Asset status field.

Farvision Sales Orders tied to Properties and Customers map to Infor Cloudsuite Industrial Sales Order or Agreement records. Farvision payment schedules (booking amount, installment milestones, possession-linked payments) require transformation into Infor Sales Order line schedules or separate Agreement milestone records, since Infor Cloudsuite Industrial's standard sales order uses different milestone semantics than Farvision's real estate payment structures.

Farvision Client Billing records map to Infor Cloudsuite Industrial Accounts Receivable Invoice records. We preserve billing history including payment milestones, installment tracking, and payment status from Farvision's Post-Sales module. Invoices are linked to the corresponding Customer Business Partner and Project Cost Center for project-wise financial reporting. Closed invoices carry their original billing dates; pending installments are flagged for reconciliation in the customer's accounting team post-migration.

Farvision Stores and Procurement inventory records map to Infor Cloudsuite Industrial Item and Warehouse records. Farvision's materials, stock tracking, and unit-of-measure conventions require explicit mapping to Infor's unit-of-measure system. Inventory valuation methods (FIFO, average cost) in Farvision map to Infor's costing method configuration. Procurement records and supplier information map to Business Partner records with role = Supplier.

Farvision HR and Payroll module Employee Life Cycle records map to Infor Cloudsuite HCM or HR tables. We migrate employee records and compensation history including salary components, deduction preferences, and leave balances. Farvision's payroll effective-dated records require careful mapping to Infor's effective-dated HR structure, and we flag these records for manual verification by the customer's HR team post-migration to confirm benefit enrollment, tax jurisdiction, and compliance settings are accurate.

Farvision Activity records and Activity Group associations map to Infor Cloudsuite Industrial Activity or Workflow Activity records. We extract activities from Farvision's YouTube-documented import/export format and translate group associations into Infor's activity grouping structure. Farvision's custom activity types and status values map to Infor's configurable activity categories. Activity timestamps and owner assignments migrate directly with owner resolved via User mapping.

Farvision Payment Types Master configuration maps to Infor Cloudsuite Industrial Payment Term records. We preserve the configured payment type structure including installment frequency, due date rules, and applicable property types. Farvision custom payment types (advance, milestone-linked, post-dated cheque, online) map to Infor's Payment Term or Method with the corresponding due date calculation logic maintained. Payment Type Group associations transfer as Payment Term Group assignments.

Farvision Places Management stores country and state hierarchies with project-specific location trees. We preserve the full location hierarchy including project sites, wing/block assignments, and regional groupings. Geographic levels (country, state, city, project site, building, floor) map to Infor Cloudsuite Industrial's location or address structure with the same parent-child relationship intact. Regional and zone configurations from Farvision map to Infor's geographic classification fields.

Farvision Engineering module covers Quantity Surveying and billing records with industry-specific structures unique to real estate and infrastructure cost management. We extract these records from MongoDB and map them to Infor Cloudsuite Industrial's Engineering or QS data structures with field-level mapping to standard ERP formats. Farvision's project-specific cost codes, rate analysis, and bill of quantities entries are preserved as Engineering records linked to the corresponding project Cost Center. These records are flagged for customer review due to the industry-specific nature of the data structures.

Farvision's customization capabilities generate custom fields across objects that we migrate with explicit field-to-field mapping. We extract custom field definitions from Farvision's MongoDB document schemas and translate them to Infor Cloudsuite Industrial custom field configurations. Unsupported field types (Farvision-specific picklists, calculated fields, document attachments) are flagged in the migration inventory for manual configuration in Infor CloudSuite Industrial's form designer post-migration. Custom field values migrate as data values only; the customer configures the destination field definition before or immediately after data load.