Migrate from proALPHA ERP to Microsoft Dynamics 365 Business Central

proALPHA Customers map to Dynamics 365 Customer records. proALPHA stores classification data (customer type, payment terms, tax classification) as partner-specific properties; we map these to Customer Posting Groups, Payment Terms, and the Shipment Method fields in Business Central or to the CustCustomerGroup and related tables in Finance and Operations. Customer-specific pricing conditions stored as user-defined fields are mapped to the applicable price list entity at migration time.

proALPHA Vendors map to Dynamics 365 Vendor records with the same structural approach as Customer mapping. Vendor-specific fields for EDI identifiers, preferred carrier, and quality rating map to Vendor Posting Groups and the Dimensions on vendor-ledger entries. We preserve the proALPHA vendor number as the primary key and the Dynamics 365 vendor account number as a cross-reference field.

proALPHA contact persons linked to business partners map to Dynamics 365 Contact records. The Contact is linked to the parent Customer or Vendor via the Contact Business Relation table. Multiple contacts per business partner migrate with their role, phone, email, and address data preserved. In Finance and Operations, contacts are stored in the DirPartyContactInfoView and ContactPerson table.

proALPHA Items with single-level BOMs map to Dynamics 365 Item records with the Bill of Materials tab populated. Multi-level BOMs require decomposition in proALPHA before reassembly in Dynamics 365: we extract each subassembly as a separate Item, then create the parent BOM with line items referencing the subassemblies. proALPHA's variant configuration data maps to Item Variants in Business Central or to the Product Configuration Model in Finance and Operations.

Multi-level proALPHA BOMs are decomposed into a flat Item list (each subassembly becomes its own Item with a BOM of its own) before migration, then reassembled in Dynamics 365. We extract the full BOM tree structure from proALPHA, create Items for every node, and construct the BOM lines referencing the child Items. Routing data with work center assignments maps to the Dynamics 365 routing entity with workstation and capacity data preserved.

proALPHA Work Orders (Fertigungsaufträge) map to Dynamics 365 Production Orders. We extract order status, material allocations, backflush records, and operation sequences. The linked BOM reference and routing are resolved through the Item and BOM mappings. Finished goods posting dates and quantities are mapped to the production journal in Dynamics 365. Closed or completed orders migrate as posted production orders with history preserved.

proALPHA's Chart of Accounts with cost center and department assignments maps cleanly to Dynamics 365's standard chart of accounts structure. Account types, posting definitions, and account categories migrate as configured fields. We verify account types against the destination's posting group taxonomy before import and flag any proALPHA cost center assignments that require mapping to Dynamics 365 Dimensions (Financial Dimensions in Finance and Operations; Default Dimensions in Business Central).

proALPHA Journal Entries migrate as General Journal lines in Dynamics 365. We extract GL date, account, debit or credit amount, dimensions, and source document reference. Entries with complex split-line structures (multiple accounts on a single document) are decomposed into individual journal line records. Very old entries spanning more than five years are flagged for archive recommendation unless the customer explicitly requests full historical migration.

Outstanding payables migrate as open vendor ledger entries with payment terms, due dates, remaining amounts, and partial allocations. We perform a fixed-point-in-time extraction to capture the open item state before the migration cutover date. Any invoices partially paid are migrated with the remaining open amount. In Finance and Operations, open AP records are imported via the VendOpenTransEntity.

Outstanding receivables migrate as open customer ledger entries with payment terms, due dates, and partial allocations. We use the same fixed-point-in-time extraction method as AP. Credit limit data from proALPHA maps to the Customer Credit Limit field in Dynamics 365. Any customer balances with payment holds are flagged as notes for the customer's AR team to review post-migration.

Fixed asset records including acquisition cost, depreciation schedules, useful life data, and location assignments migrate to Dynamics 365 Fixed Asset records. The depreciation method (linear, declining balance, units of production) is preserved. Fixed Asset posting groups are mapped to the destination's FA posting groups. Any assets with capital investment subsidies or special depreciation treatment are flagged for manual review before posting group assignment.

Stock quantities, locations, and lot or serial numbers map to the Dynamics 365 inventory structure. proALPHA's multi-location planning means inventory records may span sites; we map each proALPHA site to a Dynamics 365 Location (Business Central) or Site and Warehouse (Finance and Operations). Lot numbers and serial numbers migrate to Item Tracking. The customer specifies the on-hand snapshot date during scoping to avoid counting inventory movements post-extraction.