Migrate from iGEO ERP to Microsoft Dynamics 365 Business Central

iGEO Client records hold contact details, service addresses, and associated contract links. We map them to Business Central Contact and Customer records (using the Customer card to capture billing and payment terms) or Finance and Operations DirParty/CustTable depending on the destination tier. Address hierarchy (service location vs. billing address) is preserved by splitting iGEO's single address block into Business Central Address and Remit-To fields, or Finance and Operations LogisticsPostalAddress roles.

iGEO Contracts define service agreements with scope, frequency, pricing, and work-order templates. We migrate contract headers and line items, mapping frequency patterns (weekly, biweekly, monthly, quarterly) to Business Central Job Task Lines or Finance and Operations周期性 agreement lines. Contract start and end dates migrate to Job/Project start and deadline fields, and contract value maps to Budget Amount. If iGEO stores contract templates, we document them separately for rebuild as Business Central Jobs or Finance and Operations Projects.

iGEO Service Types represent the catalog of offerings — insect treatment, rodent control, water quality inspection, pool care. We preserve service type codes and descriptions, mapping them to Business Central Item records with Type = Service, or Finance and Operations EcoResProduct entries. Pest control-specific codes (pesticide product codes, application method codes) migrate as custom fields on the Item or Product record. Service frequency templates migrate as recurring general journal lines in Business Central Jobs.

Work Orders are the operational center of iGEO — each ties a Client, a Service Type, a Technician, a scheduled date, a status, and a location. We migrate all open and historical Work Orders, mapping iGEO's status codes to Business Central Service Order status values or Finance and Operations custom status enum. This is the highest-risk object in the migration because pesticide application records, regulatory compliance fields, and country-specific service codes live here and must be mapped explicitly as custom fields on the destination entity before any records load.

iGEO Routes are daily technician schedules generated by AI planning. We extract route assignments including visit sequence, estimated times, and geographic waypoints, mapping them to Business Central Service Zones (territory assignments on Resource records) or Finance and Operations WrkCtrTable planning groups. The AI-generated sequence itself is a routing algorithm output with no direct Dynamics 365 equivalent — we preserve the route-to-technician assignment and stop order as custom fields on the Service Order or Work Order, and document the scheduling dependency for rebuild in Dynamics 365 Field Service's Schedule Board.

iGEO Technician records include contact information, assigned territories, availability, and mobile app credentials. We migrate these as Business Central Resource records (linked to the Jobs module for service capacity planning) or Finance and Operations HcmWorker records. Territory assignments migrate as Resource Service Zone memberships or Worker warehouse/location assignments. Mobile app credentials do not migrate; the customer's admin provisions Microsoft Entra ID (Azure AD) credentials for Field Service Mobile app access post-migration.

iGEO Supplier records hold vendor contact details and associated product or service offerings. We map them directly to Business Central Vendor or Finance and Operations VendTable, preserving catalog associations and contact information. Supplier product associations migrate as Vendor Catalog entries in Business Central or as trade agreements in Finance and Operations if the supplier is tied to pricing agreements.

iGEO Stock entries track inventory items, quantities, reorder points, and supplier associations for pesticide products and consumables. We migrate stock records including current quantities and reorder thresholds, mapping units of measure to Business Central Unit of Measure or Finance and Operations InventUnit. Pesticide product inventory migrates as Items with a custom pesticide_registration field holding the regulatory license number. Warehouse location codes map to Location codes in Business Central or InventLocation in Finance and Operations.

iGEO Invoice records include line items, taxes, totals, and payment status. We migrate invoice headers and line items, preserving regulatory compliance codes and pesticide tracking fields as custom fields on the Business Central Sales Invoice or Finance and Operations invoice entity. Historical invoices (closed, paid) migrate with status locked. Open invoices (unpaid, partially paid) migrate with their current status and remain open for payment processing in Dynamics 365.

iGEO Quotes and Estimates are proposals sent to clients before service commitment. We migrate these including line items, totals, and status (sent, accepted, rejected), mapping them to Business Central Sales Quote or Finance and Operations SalesQuotation. Active quotes migrate with status Open; expired or rejected quotes migrate as closed records with a custom status_reason field for reporting on lost-quote analysis.

iGEO Employee records include staff beyond field technicians — office staff, admins, and managers. We migrate these as Business Central Employee records and User accounts, or Finance and Operations HcmWorker records with User mapping via HcmWorkerLinkedWorker and DirPersonUserMapping. Role assignments and department associations migrate as Responsibility Centers in Business Central or HcmDepartment assignments in Finance and Operations.

iGEO supports custom fields on most objects, particularly for compliance and pesticide tracking. We document all custom field definitions during discovery — including pesticide product codes, regulatory license numbers, application method codes, country-specific compliance statuses, and water quality measurement fields — and map each explicitly to Dynamics 365 custom fields, option sets, or extended data types. This object-level entry represents the entire custom field estate and is addressed before any data migration phase begins to ensure the destination schema is complete.