Migrate from iGEO ERP to Epicor Prophet 21

iGEO Client records (contact details, addresses, service locations) map to Epicor Customer records at the header level, with each distinct service address from iGEO mapped to a corresponding Epicor ShipTo record under that Customer. The customer's primary contact in iGEO becomes the Customer primary contact. We use the iGEO client identifier as an external key on Epicor Customer.XrefCustID for dedupe and cross-reference during migration.

iGEO Contracts with scope, frequency, pricing, and work-order templates map to Epicor Service Contracts. Each iGEO contract line (representing a service type and frequency) maps to a ContractLine record with coverage terms and billing frequency. The service frequency pattern in iGEO (e.g., biweekly, monthly, quarterly) translates to ContractLine recurring billing terms in Epicor Service Management.

iGEO service types (insect treatment, rodent control, legionella inspection, water quality testing) map to Epicor Part records with PartType = Service. The iGEO service type code and description preserve in Part.PartNum and Part.Description. For services that involve materials (pesticides, treatments), we map to Part with PartType = Material or Stock, preserving unit of measure from iGEO. Compliance-relevant service types receive a UDF for EN16636 certification status.

iGEO Work Orders (the core operational record tying client, service type, technician, date, status, and location) map to Epicor Job records as the parent container, with the service type and any materials applied represented as JobMtl rows. Job.JobType = Service for field service operations. We preserve iGEO work order status (Open, In Progress, Completed, Cancelled) mapping to Job.JobEngineered, Job.Released, and Job.Closed flags. Historical work orders (Closed in iGEO) migrate as Completed Jobs in Epicor.

Each iGEO work order line representing a specific treatment or service action maps to an Epicor JobMtl record referencing the Part (service or material) and quantity. If the work order includes labor tracking in iGEO, those hours map to Epicor LaborDtl records with LaborType = Production and a JobNum reference. Technician time from iGEO maps to LaborDtl with the assigned iGEO technician resolved to an Epicor Employee record.

iGEO Technician records (contact, territory, availability, mobile app credentials) map to Epicor Employee records. The technician's assigned service territories from iGEO map to Epicor ResourceGroup and Resource records for scheduling purposes. Mobile app access credentials do not migrate — the customer provisions new Kinetic mobile access for technicians post-migration. Active versus inactive technician status from iGEO maps to Employee.Inactive = false/true.

iGEO AI-generated daily technician routes (visit sequence, estimated times, geographic waypoints) do not have a direct Epicor equivalent because Epicor has no native route planning module. We extract the most recent route assignments and convert them to Epicor Job records with scheduled start dates and assigned Employees for migration day-one scheduling context. Long-term route planning requires a third-party field service scheduling add-on or Kinematic API customization, which we document in the handoff notes.

iGEO Stock entries (inventory items, quantities, reorder points, supplier associations, units of measure) map to Epicor PartWhse records for warehouse-level quantity and PartBin for bin-level location. Reorder points from iGEO translate to PartWhse.MinimumOrderQty or PartWhse.SafetyStockQty depending on the customer's usage. Supplier associations from iGEO map to Epicor PartPlant.SupplierPPVendorNum.

iGEO Supplier records (vendor contact details and product or service offerings) map to Epicor Vendor records. The iGEO supplier code and description preserve on Vendor.VendorID and Vendor.Name. Associated product lines in iGEO map to Epicor PORel records or as VendorPP records for supplier-specific pricing. Contact information from iGEO maps to Vendor primary contact fields.

iGEO Invoice records (line items, taxes, totals, payment status, and any pesticide compliance codes) map to Epicor ARInvoice header and InvcDtl lines. The iGEO invoice number becomes the Epicor InvoiceNum for reference integrity. Regulatory compliance codes from iGEO pesticide tracking fields migrate to custom UDC columns on InvcDtl. Payment status (Paid, Outstanding, Overdue) maps to ARInvoice.OpenInvoice flag. Historical invoices spanning multiple years are migrated as posted ARInvoice records.

iGEO Quotes and Estimates (proposals with line items, totals, and status) map to Epicor QuoteHed and QuoteDtl records. The quote status from iGEO (Sent, Accepted, Rejected, Expired) maps to Epicor QuoteHed.QuoteStatus values. Line items referencing service types from iGEO resolve to Epicor Part records already loaded in the Part migration phase.

iGEO pesticide tracking fields (product name, application rate, target pest, regulatory classification, EN16636 compliance status) are iGEO-native compliance artifacts with no Epicor standard equivalent. We map these to User Defined Columns (UDCs) on Epicor's PartLot table (for lot-tracked inventory), JobMtl (for materials applied during work orders), and InvcDtl (for invoice-level compliance reporting). UDC definitions are created per product line during the schema design phase. RD865/2003 and CEPA regulatory codes preserve as UDC values for audit traceability.

iGEO custom fields on any object migrate to Epicor User Defined Fields (UDFs) with equivalent data types. Text custom fields map to UDFs of type string, numeric custom fields to decimal or integer UDFs, date fields to date UDFs, and checkbox fields to logical UDFs. The customer identifies all active custom fields during discovery, and we create the corresponding UDC schema in Epicor before any data load. Industry-specific custom fields (compliance codes, pesticide categories, regulatory statuses) map to the same UDC framework as the pesticide tracking fields above.

iGEO Employee records beyond field technicians (office staff, admins, managers) map to Epicor Employee records, preserving role assignments, department associations, and department code. The iGEO employee type field (Field Technician, Office Staff, Admin, Manager) maps to Epicor Employee LaborType codes. User credentials for the iGEO application do not migrate.