Migrate from ABRA Gen to Infor CloudSuite Corporate

ABRA Gen firmy records contain address, contact, financial classification, and sometimes custom fields. We map firmy to Infor CloudSuite Account with associated Address records. The firmy ICO (company registration number) maps to a custom field on Account to preserve the Czech business identifier. Custom firmy extensions identified during database audit require manual field-level mapping to Infor Account extension fields or custom fields on Account.

ABRA Gen dodavatele records include payment terms, banking details, and vendor-specific discount structures. We map dodavatele to Infor CloudSuite Supplier records with associated Address entries. Payment terms from ABRA Gen (e.g., specific Czech payment day conventions) map to Infor's Payment Terms configuration table. Vendor-specific discount structures become custom fields on Supplier.

ABRA Gen odberatele records mirror the vendor structure with billing and shipping details. We map odberatele to Infor CloudSuite Customer records, preserving the original ABRA Gen customer code as a reference field. In scenarios where ABRA Gen uses the same firmy record for both company and customer relationships, we split into separate Infor Account and Customer records based on the record type flag.

ABRA Gen zakazky capture project-level financial tracking, billing, and cost allocation. We map zakazky to Infor CloudSuite Project or Work Order depending on the customer's operational use. Job codes preserve as Project codes. Nested zakazky hierarchies require flattening into a Work Breakdown Structure in Infor Project. Job-specific cost centers map to Infor Cost Codes.

ABRA Gen vyrobky records include pricing, BOM, unit-of-measure definitions, and product variants. We map vyrobky to Infor CloudSuite Item Master. Multi-level BOMs in ABRA Gen require flattening or reconstruction in Infor's BOM management because Infor CloudSuite Industrial represents BOM structures differently with routing and work center assignments. Unit-of-measure definitions map to Infor's UoM conversion tables.

ABRA Gen sklady records cover stock locations, quantities, and inventory valuation methods. We map warehouse codes to Infor CloudSuite Warehouse records with corresponding Bin/Location structures. Serialized and lot-controlled items from ABRA Gen require mapping to Infor's lot/serial number tracking. Inventory valuation method differences (e.g., Czech-specific cost methods) map to Infor's inventory valuation configuration, with any unsupported methods flagged for customer finance review.

ABRA Gen ucetni records represent Czech accounting journal entries with COA structures and tax codes tied to Czech statutory requirements. We map account codes to Infor CloudSuite's General Ledger chart of accounts, performing a structural COA mapping that translates Czech account class numbers (1-9) to the Infor account structure. Document-level detail and audit trails preserve for each journal entry. Closed fiscal years migrate as read-only historical records; open fiscal years load into Infor's open GL.

ABRA Gen doklady records include sales invoices, purchase orders, and delivery notes as document headers with line items. Open invoices (unpaid AP/AR) map to Infor CloudSuite vouchers and invoice records. Historical closed invoices migrate as read-only reference records if the retention scope covers them. Posting dates outside the migration window are flagged and excluded from operational load into Infor's live AP/AR tables.

ABRA Gen zamestnanci records include employment status, department assignment, and contact data. We map to Infor CloudSuite Employee records. Czech/Slovak employee data privacy requirements (GDPR compliance) are respected during extraction; national ID numbers and sensitive fields are mapped to the corresponding Infor Employee fields with access controls configured per the customer's data residency requirements.

ABRA Gen uzivatele records contain user accounts, roles, and permission sets. We map user records to Infor CloudSuite User accounts, resolving role and permission structures to Infor's role-based access model. Inactive ABRA Gen user accounts are flagged to be deactivated at cutover. The mapping preserves the original ABRA Gen user login name as a reference field for audit trails.

Custom-developed ABRA Gen modules and heavily customized standard modules identified during the database audit require manual schema comparison. We inspect the live database schema against the standard ABRA Gen data dictionary to identify custom tables and extended columns. Each custom object is mapped manually to Infor custom objects or extension fields on standard Infor objects, and flagged for customer review before load. Custom module behavior logic does not migrate; it requires rebuild by the customer's Infor implementation partner.

Czech and Slovak tax law mandates retention of accounting records for 5 to 10 years depending on document type. We do not load closed fiscal years into Infor CloudSuite's operational GL; instead, we export them as read-only archive files in a structured format (CSV or XML) alongside the migration. The archive satisfies legal retention requirements without bloating the Infor operational database. The customer's finance team retains access to the archive for statutory audit requests.