Migrate from reybex to Acumatica

reybex stores customers, vendors, and personal contacts in a unified Contact entity with a type flag (Customer/Vendor/Both). We split these into separate Acumatica Customer and Vendor records — the original reybex contact type preserved as a custom attribute on each party record for audit continuity.

reybex Articles carry inventory quantities, pricing tiers, BOM links, and warehouse assignments in a single record. Acumatica separates Stock Items (with Inventory ID and warehouse-specific On Hand quantities) from Non-Stock Items. We map reybex articles with positive stock to Acumatica Stock Items, drop-ship and service-only articles to Non-Stock Items, and preserve original reybex article type codes as custom attributes.

reybex Sales Orders map directly to Acumatica Sales Orders. Key transformations: reybex warehouse code maps to Acumatica warehouse-branch assignment; reybex line-level discount percentages become Acumatica Discount Code and ManualDiscount fields; reybex shipping terms map to Acumatica Ship Terms on the order header. Open orders import first; completed orders follow for historical reporting continuity.

reybex Purchase Orders migrate to Acumatica Purchase Orders with vendor lookup resolved by matching the vendor email address to an existing Acumatica Vendor record. Order-status values (Open, In-Transit, Completed, Cancelled) are translated to Acumatica status codes (Open, Pending Approval, Completed, Cancelled) using a value‑mapping table. Any reybex line‑level notes are preserved as Purchase Order text fields for audit continuity.

reybex Invoices are split into Acumatica AR Invoices (for customer-facing invoices) and AP Invoices (for vendor bills). reybex invoice-line tax codes map to Acumatica tax zone assignments. We preserve the original reybex invoice number as a custom field for source-system traceability.

reybex Projects map to Acumatica Projects with cost-code breakdowns preserved as Acumatica cost codes within each project. reybex project status values map to Acumatica status codes (Planning, Active, Completed, On Hold). Billable flag translates to Acumatica's billing rule assignment on the project.

reybex warehouse records map one‑to‑one to Acumatica Warehouse entities, preserving the original warehouse code as the Acumatica WarehouseID. reybex N:N article‑warehouse assignments are broken into per‑warehouse quantity records (On Hand, Available, In‑Transit) that link each Stock Item to its location‑specific inventory levels. All quantity records are validated against the Acumatica warehouse schema before import to avoid orphan inventory entries.

reybex BOM (Stücklisten) translate to Acumatica BOMs with material and overhead components mapped to Bill of Materials lines. reybex production orders migrate to Acumatica Production Orders with Material Issue and Labor capture — Acumatica Manufacturing Edition required for full MES and scheduling capabilities.

reybex GoBD‑compliant POS transactions are loaded into Acumatica Cash Management, with the original TSE serial number and signature reference stored as custom fields on each Cash Flow entry. The reybex POS transaction ID maps to the Acumatica reference number, preserving a complete audit trail for German fiscal reporting. The Acumatica customization project must be published before Cash Management import so the custom attributes exist in the schema.

reybex imported bank statements are mapped to Acumatica Cash Flow Entries, with reybex bank‑match codes converted to Acumatica matching references for reconciliation. MT940‑format bank feeds from German banks are ingested through Acumatica's Cash Management import, supporting standard field parsing for account number, transaction date, amount, and reference. All imported entries are validated against the Acumatica Cash Flow schema to ensure proper GL account assignment and to avoid duplicate entries.

reybex custom fields on Articles, Contacts, and Orders migrate as Acumatica custom fields using the DAC attribute system. Pick-list custom fields in reybex require value-by-value mapping to Acumatica segmented keys or custom selector fields. All reybex custom field definitions are exported as a schema reference document for Acumatica admin review before activation.