Migrate from Exact Globe to Epicor Prophet 21

Exact Globe Accounts map to Epicor ERP Customer and Vendor records. The mapping uses the account code as the Epicor Key1 value and preserves payment terms, tax codes, and credit limits. Multi-address structures in Exact Globe (billing address, delivery address) map to Epicor ShipTo and MXCustomerPostalCode records respectively. We resolve the country and currency dimensions during extraction so that the Epicor country codes and currency IDs are pre-validated before insert.

Exact Globe journal entries and their line items map to Epicor GLJrnGrp and GLJrnLine. The journal number and entry date migrate as GroupNum and JEDate respectively. Debit and credit amounts map to GLJrnLine amounts with account codes resolved to Epicor AccountNum via a pre-built lookup table. Dimension values from Exact Globe (cost centre, project, department) map to Epicor GLJrnLine user-defined fields. Date-range scoping is applied during extraction to keep the export window within API timeout tolerances.

Sales and purchase invoices split into header and line tables in both systems. Exact Globe Invoice, InvoiceLine, and InvoiceLineTax map to Epicor InvcHead, InvcDtl, and InvcTax. We preserve invoice number, invoice date, due date, and payment status. Line-level data (item code, quantity, unit price, tax code) maps to Epicor equivalents with tax codes validated against the destination tax configuration. Invoices in Exact Globe that reference a project are linked to Epicor Project via ProjectID on the line record.

Exact Globe Items map to Epicor Part records with PartCode as the destination key. We map item code, description, unit of measure, cost price, and sales price. For inventory-managed items, we create PartPlant records for each warehouse defined in Exact Globe. BOM links from Exact Globe Items are preserved as separate BOM records mapped in the BOM step. Stock levels migrate as PartBin records per warehouse. Service items and non-inventory items are flagged using Epicor's PartType field.

Exact Globe sales and purchase orders split into Order and OrderLine tables. Header fields (order number, customer account, order date, warehouse) map to Epicor OrderHed; line fields (item code, quantity, unit price, delivery date) map to OrderDtl. Order status from Exact Globe (open, processed, invoiced) maps to Epicor OrderRel status. Back-order relationships are preserved through order line parent links. We use Epicor's Bulk API for orders with more than 1,000 line items to avoid timeout conditions.

Exact Globe Project headers, cost categories, billing methods, and budgets map to Epicor Project and ProjectPhase. Time entries in Exact Globe map to ProjectTransaction records with work date and hours preserved. Billing methods (time and materials, fixed price) map to Epicor billing rules. For Exact Globe projects with linked invoices, we link the Epicor Project to the migrated InvcHead records via ProjectID. Multi-phase project hierarchies in Exact Globe translate directly to Epicor's Phase structure.

Exact Globe Quotations map to Epicor QuoteHed and QuoteDtl. The quotation number, customer account, and expiry date migrate to Epicor QuoteHed. Line items (item code, quantity, unit price, discount) map to QuoteDtl. Conversion status (expired, converted to order) in Exact Globe maps to Epicor QuoteHed status, and converted quotations are linked to the corresponding Epicor OrderHed via the quotation reference field. We flag quotations past expiry for the customer's review before loading.

Exact Globe Contact persons map to Epicor Person and Contact records. The contact name, email, phone, and role fields migrate to Epicor Person fields. We link each Contact to the corresponding Customer record via the CustID foreign key resolved from the Account mapping step. Multiple contact roles per contact person in Exact Globe are mapped to Epicor ContactRole records. Primary contact flag is preserved as the PrimaryPerson field on the Customer record.

Exact Globe Chart of Accounts structure maps to Epicor GLAccount with natural account as the primary segment and cost centre or department as secondary segments. We build a segment mapping table during discovery that identifies how many segments Exact Globe uses versus the Epicor account structure. Account groups, active/inactive status, and descriptions migrate directly. Posted transaction history maps to GLJrnLine records. Locked or reconciled periods in Exact Globe require date-range scoping; we flag any locked period modifications for the customer's admin to handle before extraction.

Exact Globe multi-level BOMs with embedded routing steps decompose into Epicor BOMHead (header), ECOMtl (component lines), and PartMtl records. Recursive traversal of sub-assemblies runs in staged extraction passes from Exact Globe, constructing Epicor BOM records per level. Operation routing steps from Exact Globe BOMs map to ECOOp records in Epicor Kinetic, with work centre references resolved from the Epicor WorkCenter table. For Epicor Prophet 21 distribution editions without manufacturing, BOMs are not available and items map as standard Part records.

Exact Globe fixed asset records (acquisition cost, depreciation method, book value, asset class) map to Epicor FaAsset. Depreciation method codes are translated to Epicor FaAsset.DepreciationMethod values. Asset class from Exact Globe maps to FaAsset.AssetClass. We validate that the fiscal year calendar in Epicor aligns with Exact Globe's; if not, we recalculate depreciation schedules during the transform step and flag the adjusted values for the customer's finance team to verify before posting.

Exact Globe HR data (employee records, compensation, org structure) maps to Epicor EmpBasic and extended data fields. Effective-dated compensation changes in Exact Globe are stored as separate transaction rows that we consolidate into the current Epicor compensation field. Org structure hierarchy maps to Epicor EmpBasic.ReportsTo field. HR data migration is scoped to active employees; terminated employee records are archived with a status flag rather than loaded as active Epicor employees. This mapping is lower-volume and handled as a final-phase migration step.

Exact Globe custom fields (text, long, double, date, bit) on 14 standard tables require pre-creation of Epicor UD (user-defined) fields with matching data types before the load phase. Field types are validated: Exact Globe double maps to Epicor decimal UD fields, date maps to date, and bit maps to checkbox. We inventory all custom field names and types during discovery and lock the Epicor UD schema before extraction begins. Any destination-side custom field mapping that has not been pre-created will cause record rejection on insert.