Migrate from Runple to Microsoft Dynamics 365 Business Central

Runple Customer records map to Dynamics 365 Customer Master. The customer name, addresses, tax identification number, and payment terms transfer directly. We use the Runple customer number or a customer-assigned external ID as the dedupe key. VAT registration numbers map to the destination's VAT Registration No. field. Business Central supports separate Bill-to and Sell-to addresses; Finance/SCM supports multiple address purposes per party record.

Runple Products map to Dynamics 365 Item records with SKU, name, description, unit price, and cost preserved. Item type (Inventory vs Service vs Non-Inventory) maps from Runple's item classification. The unit of measure from Runple maps to the Dynamics 365 Unit of Measure, which must be pre-configured if non-standard units are used. Business Central requires a Stockkeeping Unit setup if inventory tracking by location is needed.

Runple Invoices migrate as posted sales invoices in Dynamics 365. Invoice number, customer reference, invoice date, due date, currency, and line items (product, quantity, unit price, discount, tax amount) transfer directly. The Runple invoice body including tax calculations and totals map to the Dynamics 365 invoice document. We preserve invoice status (Open vs Paid) by matching against the migrated payment records. Draft invoices are migrated as open invoices and marked accordingly.

Runple Payment records link to invoices by payment amount and date. We match payments to the corresponding Dynamics 365 open invoice using amount, date, and customer as the reconciliation key, then mark the related CustLedgerEntry as Applied. Payment method (bank transfer, credit card, cash) maps from Runple to a configured Payment Method in Dynamics 365. Historical payment method distributions are preserved in the payment journal.

Outstanding receivables from Runple migrate as open CustLedgerEntry records with Remaining Amount set to the open balance, Due Date preserved, and Aging Bucket ID assigned based on the original Runple aging configuration. We extract current open items and map them to the destination's corresponding AR module, flagging any items where the customer or vendor does not yet exist in Dynamics 365 and must be created first. Runple's payables (if applicable) map similarly to VendLedgerEntry.

Runple stock movement records including quantity changes, dates, and warehouse locations map to Dynamics 365 Item Ledger Entry. Current stock levels populate the Item Tracking or WMSLocation tables. For Finance/SCM destinations with multi-warehouse configuration, Runple's single-warehouse location maps to a primary site with the option to create additional sites during setup. We preserve the last stock count date from Runple for inventory valuation reconciliation.

Runple's chart of accounts entries map to Dynamics 365 G/L Account numbers. Account type (Posting, Heading, Total) transfers directly. We preserve account names in both German and English if the customer's Runple instance uses German-language account descriptions. Balance carryforward entries are created for the opening date in Dynamics 365 with amounts from Runple's year-end closing entries. Dimensions from Runple (Cost Center, Department) map to Dynamics 365 DefaultDim or Financial Dimension structures.

Runple EU VAT codes require manual review and remapping because the two systems use different tax code schemas. We extract every distinct Runple VAT rate and code combination and present them as a tax mapping table for the customer's finance team to assign to Dynamics 365 VAT Posting Groups or Tax Codes. Reverse-charge rules from Runple must be recreated as Tax Transactions in Finance/SCM. This is a manual compliance step; we flag it as requiring finance-team sign-off before go-live.

Runple user accounts with roles and permissions require remapping because access control models differ between systems. We extract role assignments and map them to the nearest equivalent Dynamics 365 permission sets or security roles. In Finance/SCM, users are associated with Workers from the Human Resources module, which requires provisioning. We extract the Runple role-permission matrix and deliver a written security role design recommendation for the customer's IT admin to implement.

Runple commission data is stored as HR-adjacent records with no direct Dynamics 365 equivalent. We extract commission percentages, salesperson assignments, and applicable product or customer groupings and map them to custom fields on the Sales Line (if Microsoft Dynamics 365 Sales and Marketing is licensed) or as a Salesperson Dimension in the general ledger. The customer chooses commission handling during scoping.

Time tracking data from Runple (hours, dates, employee assignments) may map to the Time Registration module in Business Central or the Project Management module if the customer uses project costing. Finance/SCM requires the Human Resources module for time and attendance. Not all Runple time records are migratable to standard Dynamics 365 objects; we map these to custom fields or a project journal entry at the customer's direction.

Runple POS transactions are point-of-sale events that have no standard equivalent in Dynamics 365 Business Central or Finance/SCM without the Retail module. We do not migrate POS transactions as line items. We extract a POS transaction summary (daily totals by register, payment method, and shift) and deliver it as a reconciliation document for the customer's finance team to post manually or via a journal entry template. The customer must separately evaluate Dynamics 365 Commerce if ongoing POS integration is required.