Migrate from iGEO ERP to Infor CloudSuite Corporate

iGEO Client records hold both customer contact details and supplier contact details in a single object with a type flag. During migration we split by client_type: customers map to Infor Cloudsuite Customer records with party_type = Customer, and suppliers map to Infor Supplier records with party_type = Supplier. Address hierarchy, service locations, and contact associations preserve through Infor's address book model. Any iGEO Clients flagged as both customer and supplier receive both party records with a shared address book entry.

iGEO Contracts define service agreements with scope, frequency, pricing, and associated work-order templates. We map contract headers to Infor Contract Management (if Infor FSM is deployed) or to Purchase Order headers for recurring service agreements. Frequency patterns from iGEO (weekly, monthly, quarterly) map to contract line scheduling rules in Infor. Contract status (active, expired, cancelled) preserves in Infor's contract lifecycle fields.

iGEO Service Types represent the pest control service catalog (insect treatment, rodent control, water quality inspection, etc.) with associated pricing. We map service type codes and descriptions to Infor Item records with item_type = Service. Unit of measure, pricing structure, and any pesticide codes from iGEO custom fields map to Infor Item cost and price fields. If Infor's industry edition includes a compliance module, pesticide codes are stored as custom fields on the Item record.

Work orders are the operational core of iGEO, tying a Client, Service Type, Technician, scheduled date, status, and location. We map active and historical work orders to Infor Service Orders (Infor FSM) or Production Orders depending on which Cloudsuite edition the customer deploys. iGEO work_order_status maps to Infor Order Status, and the original service location maps to Infor's address assignment on the order. Work order notes and photos migrate as order attachments.

iGEO Routes represent AI-generated daily technician schedules with visit sequence, estimated times, and geographic waypoints. We extract route assignments as scheduling records linked to the assigned Technician (User) and the scheduled Work Orders. Infor does not replicate iGEO's AI routing engine natively; route data migrates as scheduling context for the customer's Infor FSM or third-party scheduling implementation team to consume. We preserve stop sequence and estimated arrival times as custom scheduling fields.

iGEO Technician records include contact details, assigned territories, availability, and mobile app credentials. We map these to Infor User accounts with the appropriate role (Technician, Field Service Representative, or Resource). Territory assignments from iGEO map to Infor's resource territory configuration. Active/inactive status and availability windows preserve in Infor's resource management module. Mobile app credentials do not migrate; technicians must be provisioned with Infor OS mobile access during go-live.

iGEO Supplier records hold vendor contact details and associated product or service offerings. We map suppliers to Infor Supplier records, preserving catalog associations and contact information. Supplier part numbers and product associations migrate as Infor Item Supplier records linked to the relevant Items. If iGEO stores supplier-specific pricing for stock items, that migrates to Infor's Supplier Price Catalog.

iGEO Stock entries track inventory items, quantities, reorder points, and supplier associations. We map stock records to Infor Inventory Management with current quantities and reorder thresholds. Units of measure convert to Infor's unit of measure schema. Any pesticide or chemical stock items from iGEO receive custom fields in Infor to carry regulatory tracking codes. Warehouse location codes from iGEO map to Infor's warehouse and bin structure.

iGEO Invoice records include line items, taxes, totals, payment status, and any pesticide usage or compliance codes. We migrate invoice headers and line items to Infor Accounts Receivable. Compliance codes from iGEO custom fields carry into Infor's invoice line custom fields for regulatory audit purposes. Payment status (paid, outstanding, overdue) maps to Infor's invoice status. Historical invoices preserve the original invoice date and due date for financial reporting continuity.

iGEO Quotes and Estimates are proposals sent to clients before service commitment, including line items, totals, and status (sent, accepted, rejected). We map these to Infor Quotations with the same line structure and pricing. Quote status from iGEO maps to Infor Quotation Status. If the customer uses Infor CPQ (Configure, Price, Quote), quotes migrate as CPQ Quote records; otherwise they land in Infor's standard quotation module.

iGEO custom fields, particularly pesticide tracking codes, regulatory compliance statuses, and service activity logs, require explicit mapping to Infor custom fields or extended attributes. During discovery we document every iGEO custom field definition per object and map each to an Infor field of equivalent type (text, picklist, date, number). Compliance-specific custom fields receive a naming convention that flags them as regulatory data requiring audit preservation. We do not create new Infor compliance modules as part of the migration; we map into whatever compliance structures the customer has configured in their Infor environment.

iGEO Employee records include staff beyond field technicians: office staff, admins, and managers. We map these to Infor HCM Worker records with role assignments and department associations. If the customer does not deploy Infor HCM, employees map to Infor User accounts with the appropriate organizational role. Active/inactive employment status, hire date, and department assignments preserve in Infor's organizational management module.