ERP migration
Field-level mapping, validation, and rollback between Global Shop Solutions ERP and Epicor Prophet 21. We move data and schema; workflows are rebuilt natively in Epicor Prophet 21.
Global Shop Solutions ERP
Source
Epicor Prophet 21
Destination
Compatibility
11 of 15
objects map 1:1 between Global Shop Solutions ERP and Epicor Prophet 21.
Complexity
BStandard
Timeline
8-12 weeks
Overview
Moving from Global Shop Solutions ERP to Epicor ERP is a structural manufacturing data migration that requires resolving differences in chart-of-accounts design, BOM representation, work-order modeling, and multi-company hierarchy between the two platforms. We migrate GL accounts, customers, vendors, inventory items, BOMs with their engineering revisions and routing steps, open and historical sales and purchase orders, work orders with their labor postings, AR and AP ledgers, employees, quality-control records, and all custom GAB-defined fields. Global Shop Solutions does not publish a documented REST API, so migration access depends on the available export mechanism identified during discovery. We deliver a written inventory of GAB-defined custom screens and automations for the customer's Epicor consultant to rebuild. We do not migrate Workflows, Sequences, Automations, or Reports as code; these require manual reimplementation in Epicor Kinetic using its native tools post-cutover.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Global Shop Solutions ERP object lands in Epicor Prophet 21, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Global Shop Solutions ERP
General Ledger Accounts
Epicor Prophet 21
GL Account
1:1Global Shop Solutions GL accounts map to Epicor Kinetic GL Account records with account numbers and descriptions preserved. The division and department distribution flags used in Global Shop require remapping to Epicor's company and cost center hierarchy. We extract the full chart of accounts including account types, posting rules, and department distributions during the first migration phase so that all downstream records reference valid account numbers.
Global Shop Solutions ERP
Customers
Epicor Prophet 21
Customer
1:1Global Shop Solutions Customers map to Epicor Kinetic Customer records with name, address, contact details, payment terms, and credit limits preserved. Open AR balances and aging bucket data migrate as part of the AR migration phase. Ship-to addresses migrate as Customer ShipTo records tied to the parent Customer.
Global Shop Solutions ERP
Vendors
Epicor Prophet 21
Supplier
1:1Global Shop Solutions Vendors map to Epicor Kinetic Supplier records with address, contact, payment terms, 1099 settings, and 3-way AP match configuration preserved. Open AP balances migrate as part of the AP migration phase. Vendor-managed 3-way match settings transfer to Epicor's AP configuration per supplier.
Global Shop Solutions ERP
Inventory Items
Epicor Prophet 21
Part
1:1Global Shop Solutions Inventory Items map to Epicor Kinetic Part records with part numbers, descriptions, UOMs, on-hand quantities, cost layers, ABC classifications, and bin locations preserved. FIFO/LIFO/average cost method and lead times carry forward. Stock levels are captured at migration timestamp to set the Epicor PartWhse on-hand quantity accurately.
Global Shop Solutions ERP
Bill of Materials
Epicor Prophet 21
Job (BOM component)
1:1Global Shop Solutions BOMs with multi-level structures, component items, quantities per assembly, operations routing, work center assignments, and engineering revision control map to Epicor Kinetic Job records and Part BOM records. We carry forward pending ECOs as flagged records requiring re-approval in Epicor's MES. Revision control history migrates as Epicor PartRev records with effective date andECO linkage preserved.
Global Shop Solutions ERP
Sales Orders
Epicor Prophet 21
SalesOrder
1:1Open and historical sales orders migrate to Epicor Kinetic SalesOrder records with customer, line items, pricing, due dates, and fulfillment status preserved. Back-order quantities carry forward as open demand in Epicor's Demand Management. Related documents attached to the order migrate as EDMS files linked to the SalesOrder.
Global Shop Solutions ERP
Purchase Orders
Epicor Prophet 21
POHeader and POLine
1:1Open purchase orders migrate to Epicor Kinetic POHeader and POLine records with supplier assignments, line items, expected receipt dates, and landed cost allocations preserved. 3-way match status transfers to Epicor's PO receiving configuration. Historical POs migrate as closed records for reporting purposes. POLine.unitCost and landed cost components are mapped to Epicor's PO Logical Ref fields for traceability.
Global Shop Solutions ERP
Work Orders
Epicor Prophet 21
JobHead, JobOper, JobMtl
1:manyGlobal Shop Solutions Work Orders map to Epicor Kinetic JobHead (job header), JobOper (operations), and JobMtl (materials) as separate records. BOM reference, production schedule with start and end dates, work center assignments, actual labor postings, and operation completion percentages transfer to the correct Epicor table. Engineering revision linkage migrates as JobHead.JobEngineered = true with PartRev reference. Completed operations history and pending material allocations are preserved as separate JobOper and JobMtl records with their respective status flags.
Global Shop Solutions ERP
Accounts Receivable
Epicor Prophet 21
ARLedger
1:1Open AR invoices, credit memos, and cash receipts migrate to Epicor Kinetic ARLedger records with customer payment terms and aging bucket data. Historical AR invoices carry forward for collection reporting and audit purposes. Payment terms and discount eligibility transfer to Epicor's Customer AR configuration.
Global Shop Solutions ERP
Accounts Payable
Epicor Prophet 21
APInvoice and APSql
1:1Open AP vouchers, invoice images, and 3-way match status migrate to Epicor Kinetic APInvoice records. Vendor payment terms, discount eligibility, and accrued payables map to Epicor's Supplier AP configuration. 3-way match receiving status (approved, pending, exception) transfers to Epicor's POReceipt and APPreText logic for reconciliation.
Global Shop Solutions ERP
Employees
Epicor Prophet 21
Employee
1:1Global Shop Solutions Employee records migrate to Epicor Kinetic Employee with demographics, department assignments, pay rates, exempt/non-exempt status, and PTO balances. Year-to-date earnings and payroll history transfer for tax and benefit reporting. Department assignments map to Epicor's OrgLevel or EmpBasic configuration depending on the Epicor edition.
Global Shop Solutions ERP
Quality Control Records
Epicor Prophet 21
NonConf and RMA
1:1Inspection results, SPC data points, non-conformance records, and corrective action logs tied to work orders and inventory lots migrate to Epicor Kinetic NonConf records and RMA records. The full quality history required for ISO/AS9100 compliance is preserved and linked to the JobHead and PartLot records that carry the inspection data.
Global Shop Solutions ERP
Custom Properties
Epicor Prophet 21
UD Fields (User Defined)
lossyGlobal Shop Solutions user-defined GAB fields attached to any object are extracted with their data types and values. We map them to Epicor Kinetic UD fields or standard fields based on field type compatibility. Custom property naming conventions are translated to Epicor UD field naming. Any custom properties that cannot be mapped directly are flagged in the deliverable with notes on manual reimplementation in Epicor Kinetic's UD Configuration screen.
Global Shop Solutions ERP
Documents and Attachments
Epicor Prophet 21
EDMS (Electronic Document Management)
lossyDocuments attached to transactions, work orders, or the item master in Global Shop Solutions are exported and mapped to Epicor Kinetic's EDMS with DocType classification and references to the parent record. CODESOFT label templates and Crystal Report layouts do not migrate directly; we document the existing label and report configurations for the customer's Epicor consultant to recreate in Epicor Kinetic's report designer.
Global Shop Solutions ERP
Dashboards (GAB)
Epicor Prophet 21
BAQ and Dashboard Designer
lossyGAB-defined dashboards, custom screens, conditional formatting, and screen layouts do not export directly from Global Shop Solutions. We map the underlying data for all GAB-dependent records and deliver a written screen-by-screen inventory identifying which data each GAB screen references. The customer's Epicor consultant rebuilds the presentation layer in Epicor Kinetic's BAQ and Dashboard Designer. We do not rebuild GAB screens as part of the migration scope.
| Global Shop Solutions ERP | Epicor Prophet 21 | Compatibility | |
|---|---|---|---|
| General Ledger Accounts | GL Account1:1 | Fully supported | |
| Customers | Customer1:1 | Fully supported | |
| Vendors | Supplier1:1 | Fully supported | |
| Inventory Items | Part1:1 | Fully supported | |
| Bill of Materials | Job (BOM component)1:1 | Fully supported | |
| Sales Orders | SalesOrder1:1 | Fully supported | |
| Purchase Orders | POHeader and POLine1:1 | Fully supported | |
| Work Orders | JobHead, JobOper, JobMtl1:many | Fully supported | |
| Accounts Receivable | ARLedger1:1 | Fully supported | |
| Accounts Payable | APInvoice and APSql1:1 | Fully supported | |
| Employees | Employee1:1 | Fully supported | |
| Quality Control Records | NonConf and RMA1:1 | Fully supported | |
| Custom Properties | UD Fields (User Defined)lossy | Mapping required | |
| Documents and Attachments | EDMS (Electronic Document Management)lossy | Mapping required | |
| Dashboards (GAB) | BAQ and Dashboard Designerlossy | Mapping required |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Global Shop Solutions ERP gotchas
GAB editor license costs $8K and has a steep learning curve
Full company-wide buy-in is required during implementation
Not designed as a short-term or temporary ERP solution
Epicor Prophet 21 gotchas
Third-party bolt-on integrations complicate migration scope
Dirty data without standardized processes compounds migration risk
SDK customizations and BPMs may not survive platform upgrades
Report-based export only for non-technical users
Per-user pricing model requires accurate user count before migration planning
Pair-specific challenges
Migration approach
Discovery and scoping
We audit the source Global Shop Solutions environment: master record counts (GL accounts, customers, vendors, inventory items), transactional volume (open and historical sales orders, purchase orders, work orders, AR/AP records), BOM complexity (maximum nesting depth, active ECO count), open work order status, multi-company and multi-location structure, GAB-defined custom field count and object assignments, document attachment volume, quality record count, and quality standard requirements. We identify the available data export mechanism (direct database access, integration platform, or EDI) and assess multi-site inventory distribution. The discovery output is a written migration scope, Epicor edition recommendation, and timeline estimate.
Epicor Kinetic schema provisioning and design
We provision or configure the Epicor Kinetic tenant (cloud or on-premise) and design the destination schema: company and legal entity hierarchy, GL account structure and cost center configuration, UOM class setup, Part number and inventory warehouse configuration, BOM and routing structure, work center and labor code setup, customer and supplier master configuration, employee organization levels, and UD field definitions mapped from the Global Shop GAB custom property inventory. We design the multi-company mapping and identify inter-company elimination accounts for the customer's GL team to configure.
Sandbox migration and reconciliation
We run a full migration into an Epicor Kinetic sandbox environment using production-like data volume. The customer's operations and finance leads reconcile record counts and spot-check 25-50 records per major object against the Global Shop source data. Reconciliation covers GL balance verification, AR/AP aging comparison, inventory on-hand quantities, BOM structure depth, and work order operation counts. The customer approves the schema, mapping, and reconciliation results before production migration begins.
Production migration in dependency order
We execute production migration in the correct dependency sequence: GL accounts first, then customers and vendors, inventory items and stock levels, BOMs with revision history, open and historical sales orders and purchase orders, open work orders split across JobHead/JobOper/JobMtl, AR and AP ledgers, employees, quality control records, document attachments, and GAB-defined custom field values. We apply delta syncs for any records modified during the migration window and emit a per-phase reconciliation report before advancing to the next phase.
Cutover, delta sync, and handoff
We freeze writes in Global Shop Solutions at cutover, perform a final delta migration capturing any records modified during the migration window, then switch Epicor Kinetic to active production mode. We deliver the GAB field inventory with Epicor UD field mapping, the GAB screen inventory with rebuild notes for the Epicor consultant, and the automation inventory with recommended Epicor Kinetic equivalents. We support a one-week hypercare window for reconciliation issues. We do not rebuild GAB screens or automations as part of the migration scope; those require a separate engagement with the customer's Epicor consultant.
Platform deep dives
Global Shop Solutions ERP
Source
Strengths
Weaknesses
Epicor Prophet 21
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Global Shop Solutions ERP and Epicor Prophet 21.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Global Shop Solutions ERP: Not publicly documented.
Data volume sensitivity
Global Shop Solutions ERP doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Global Shop Solutions ERP to Epicor Prophet 21 migration scoping. Not seeing yours? Book a call.
Walk through your Global Shop Solutions ERP to Epicor Prophet 21 migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Global Shop Solutions ERP
Other ways to arrive at Epicor Prophet 21
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.