ERP migration
Field-level mapping, validation, and rollback between ABRA Gen and Epicor Prophet 21. We move data and schema; workflows are rebuilt natively in Epicor Prophet 21.
ABRA Gen
Source
Epicor Prophet 21
Destination
Compatibility
9 of 12
objects map 1:1 between ABRA Gen and Epicor Prophet 21.
Complexity
BStandard
Timeline
6-10 weeks
Overview
Moving from ABRA Gen to Epicor ERP is a structural migration that requires translating Central European accounting compliance and deep manufacturing data into Epicor's global ERP schema. ABRA Gen stores firmy (companies), sklady (warehouses), vyrobky (products with BOMs), zakazky (jobs), ucetni (accounting journals), and doklady (invoices) in a Firebird, SQL Server, or Oracle on-premise database with no documented REST API. We extract directly from that database, map Czech and Slovak COA codes to the destination chart of accounts, flatten multi-level BOMs into Epicor's revision-tracked bill structure, and resolve the ISDOC invoice format that ABRA Gen produces natively into Epicor's AR/AP document schema. We do not migrate workflows, BPMs, automations, or report definitions as code. We deliver a written inventory of every ABRA Gen workflow and automation requiring rebuild in Epicor Kinetic.
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 ABRA Gen 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.
ABRA Gen
Firmy (Companies)
Epicor Prophet 21
Customer and Supplier
1:manyABRA Gen firmy records store both customer and supplier entities in a single table distinguished by a type field. We split firmy into Epicor Customer (for accounts receivable) and Supplier (for accounts payable) during the transform phase. Address, contact, payment-term, and banking-detail fields map to Epicor's Customer and Supplier records, with the ABRA Gen firmy code preserved in the legacy ID field for cross-reference.
ABRA Gen
Odberatele (Customers)
Epicor Prophet 21
Customer
1:1ABRA Gen odberatele records are a subset of firmy scoped to sales-facing entities. We map these to Epicor Customer, preserving billing and shipping addresses as ShipTo records under the parent Customer. Customer credit limits, payment terms, and price lists carry forward as configuration data in Epicor's Credit Check and AR setup.
ABRA Gen
Dodavatele (Vendors)
Epicor Prophet 21
Supplier
1:1ABRA Gen dodavatele records map to Epicor Supplier. We preserve vendor codes, payment terms, and any vendor-specific discount structures. Banking details for SEPA or wire transfers map to Epicor SupplierBankAcct records. Multi-address vendors get multiple SupplierPayment records in Epicor.
ABRA Gen
Zakazky (Jobs/Contracts)
Epicor Prophet 21
Job and Project
1:1ABRA Gen zakazky capture project-level financial tracking, cost allocation, and billing. We map these to Epicor Job records for manufacturing execution and to Project records for job costing. Job codes and contract numbers carry forward as Epicor JobNum and ProjectID. Any nested hierarchy in ABRA Gen zakazky resolves to Epicor's JobMtl and JobOper multi-level structure.
ABRA Gen
Sklady (Warehouses)
Epicor Prophet 21
Warehouse and PartBin
1:1ABRA Gen sklady define stock locations with warehouse codes, bin structures, and on-hand quantities. We map warehouse codes to Epicor Warehse records and create corresponding PartBin entries for on-hand quantities. Serialized and lot-controlled inventory is flagged during discovery and mapped to Epicor's PartLot and PartBin serial-tracking fields. Multiple ABRA Gen warehouse types map to Epicor's multi-warehouse and multi-bin configuration.
ABRA Gen
Vyrobky (Products)
Epicor Prophet 21
Part and PartRev
1:1ABRA Gen vyrobky store product master records with pricing, unit-of-measure definitions, and BOM structures. We map to Epicor Part with PartNumber, Description, ClassID, and UnitOfMeasure. Multi-level BOMs from ABRA Gen are flattened into Epicor's PartRev (revision) and JobMtl structure with the correct quantity-per and operation sequences. Stocking types (finished goods, raw material, work in process) map to Epicor TypeCode.
ABRA Gen
Ucetni (Accounting Records)
Epicor Prophet 21
GLJrnHed and GLJrnLine
1:1ABRA Gen ucetni records are Czech accounting journal entries with COA codes, tax codes, and posting dates. We map account codes to the destination Epicor COA, preserving document-level detail and debit/credit amounts in Epicor's GLJrnHed and GLJrnLine tables. Fiscal year segments and cost-center codes resolve to Epicor GL Account segments. Audit trail dates and voucher numbers carry forward for the required retention period (5-10 years under Czech and Slovak law).
ABRA Gen
Doklady (Documents/Invoices)
Epicor Prophet 21
ARInvoice and APInvoice
1:1ABRA Gen doklady store sales invoices, purchase invoices, delivery notes, and credit memos as document headers with line items. We map open and recent historical documents to Epicor ARInvcHead/APInvcHead with line items to ARInvcDtl/APInvcDtl. The ISDOC XML format that ABRA Gen produces natively maps to Epicor document references stored in the Attachment table, and ISDOC invoice numbers map to InvoiceNum fields. Documents with posting dates outside the migration window are flagged for customer decision on archive versus load.
ABRA Gen
Uzivatele (Users)
Epicor Prophet 21
User and UserComp
1:1ABRA Gen uzivatele records map to Epicor User accounts and UserComp company-access records. Role and permission-set data from ABRA Gen maps to Epicor's menu-security model during configuration. Inactive ABRA Gen users are held in a reconciliation queue and deactivated at cutover. Active users are matched by email or username for Epicor User provisioning.
ABRA Gen
Zamestnanci (Employees)
Epicor Prophet 21
Employee
1:1ABRA Gen zamestnanci records hold employment data for HR and payroll integration. We map employment status, department assignment, and contact data to Epicor Employee records. Department codes from ABRA Gen resolve to Epicor's DcdLbrGrp and DcdShift cost-center configuration. Any HR or payroll data held in ABRA Gen maps to Employee fields, though ERP-integrated payroll may require a separate HRMS integration scope.
ABRA Gen
ISDOC Invoice Format
Epicor Prophet 21
Invoice Document Attachment
lossyABRA Gen natively produces invoices in the ISDOC/ISDOCx electronic format defined by the Czech SPIS/ICT Unie working group. We map ISDOC invoice headers and line items to Epicor ARInvcHead and ARInvcDtl, and preserve the original ISDOC XML as an Epicor Attachment linked to the invoice record. Customers using ABRA Gen's ISDOC export for Czech e-invoicing compliance confirm the replacement format in Epicor's Electronic Invoice configuration before migration.
ABRA Gen
ABRA Gen Address Extensions
Epicor Prophet 21
ShipTo and SupplierPayment
1:manyABRA Gen firmy records support multiple address records per entity (billing, shipping, branch). We split these into Epicor ShipTo records under Customer and SupplierPayment address records under Supplier, with address type codes preserved as ShipToNum or SupplierNum references. The primary address designation from ABRA Gen becomes the default ShipTo in Epicor.
| ABRA Gen | Epicor Prophet 21 | Compatibility | |
|---|---|---|---|
| Firmy (Companies) | Customer and Supplier1:many | Fully supported | |
| Odberatele (Customers) | Customer1:1 | Mapping required | |
| Dodavatele (Vendors) | Supplier1:1 | Mapping required | |
| Zakazky (Jobs/Contracts) | Job and Project1:1 | Mapping required | |
| Sklady (Warehouses) | Warehouse and PartBin1:1 | Fully supported | |
| Vyrobky (Products) | Part and PartRev1:1 | Fully supported | |
| Ucetni (Accounting Records) | GLJrnHed and GLJrnLine1:1 | Mapping required | |
| Doklady (Documents/Invoices) | ARInvoice and APInvoice1:1 | Mapping required | |
| Uzivatele (Users) | User and UserComp1:1 | Mapping required | |
| Zamestnanci (Employees) | Employee1:1 | Mapping required | |
| ISDOC Invoice Format | Invoice Document Attachmentlossy | Fully supported | |
| ABRA Gen Address Extensions | ShipTo and SupplierPayment1:many | Fully supported |
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.
ABRA Gen gotchas
On-premise deployment requires direct database access
Custom modules and extensions lack standard documentation
Historical accounting data retention obligations vary by jurisdiction
No publicly documented REST API for ABRA Gen
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 database access coordination
We audit the ABRA Gen on-premise database to identify active modules, record counts per entity, custom columns, and historical periods. We map the ABRA Gen schema against our standard data dictionary and identify any non-standard custom tables. In parallel, we coordinate with the customer's IT team to obtain read-only database credentials and schedule extraction windows. The discovery output is a written migration scope covering entity coverage, historical cutoffs, custom object inventory, and a preliminary object-mapping document.
Epicor environment provisioning and configuration
We set up the Epicor Kinetic test environment and configure the base configuration: chart of accounts aligned to the Czech or Slovak COA, warehouse locations mapped from ABRA Gen sklady, part number format, customer and supplier hierarchies, and any required Epicor modules (MES, Advanced Production Management, Quality Management) based on the active ABRA Gen modules. UD columns and UD tables for ABRA Gen custom fields are provisioned in the test environment before any data loads begin.
Data extraction from on-premise ABRA Gen database
We run filtered SQL exports from the ABRA Gen production database in batches, using the migration window and record-cutoff dates agreed during discovery. Each entity exports independently: firmy (Companies), dodavatele (Vendors), odberatele (Customers), vyrobky (Products with BOM), sklady (Warehouses), zakazky (Jobs), ucetni (GL), and doklady (AR/AP documents). We use read-only access and batch sizing coordinated with the DBA to avoid impacting production performance. ISDOC invoice XML files are exported alongside structured data for document attachment mapping.
Data transformation and BOM flattening
We transform ABRA Gen data into Epicor Kinetic format in a staging environment. Account codes map to the Epicor COA segment structure. Multi-level BOMs flatten into PartRev and PartMtl with operation associations. Czech and Slovak accounting journal entries split into GLJrnHed (header) and GLJrnLine (lines) with debit/credit and tax code mapping. Firmy split into Customer and Supplier records. ISDOC invoice XML attachments link to the corresponding Epicor ARInvcHead or APInvcHead records. All transforms use the mapping documents signed off during discovery.
Test migration and reconciliation
We run a full test migration into the Epicor Kinetic staging environment using production-like data volume. We generate reconciliation reports comparing record counts, account balances, and on-hand quantities between ABRA Gen and Epicor. The customer validates a sample of 30-50 records per entity type and signs off the mapping before production migration begins. Any BOM structural corrections, COA mapping gaps, or UD field schema changes happen in this phase.
Production migration and cutover
We run production migration in dependency order: Warehouses and Part data first (with BOM revisions), then Customers and Suppliers, then open AR/AP documents, then GL historical records within the retention window, then Employees, then the ISDOC document attachment layer. We freeze ABRA Gen writes during cutover, run a final delta migration of any records modified during the window, and validate totals in Epicor before re-enabling transactions. We deliver the ABRA Gen workflow and automation inventory document at cutover and support a one-week hypercare window.
Platform deep dives
ABRA Gen
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 ABRA Gen 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
ABRA Gen: Not publicly documented.
Data volume sensitivity
ABRA Gen 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 ABRA Gen to Epicor Prophet 21 migration scoping. Not seeing yours? Book a call.
Walk through your ABRA Gen 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 ABRA Gen
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.