Migrate from PayTraq to Microsoft Dynamics 365 Business Central

PayTraq GL accounts map to Dynamics 365 G/L Account records. We carry account code, name, and type (Asset, Liability, Equity, Revenue, Expense) into the destination. PayTraq account groups map to Dynamics Account Categories for reporting grouping. Dynamics 365 requires the chart to be established before any journal or transaction import because every record references a G/L Account number as a foreign key. We validate account codes against Dynamics 365's account mask format during scoping.

PayTraq Clients map to Dynamics 365 Customer records. The Customer in Dynamics is created as a Customer type (separate from Vendor). We preserve payment terms, currency code, tax ID, and address blocks. Dynamics 365 requires a payment terms setup linked to the Customer; we create the terms from PayTraq's due date rules during migration or flag for configuration. Customer post codes and country codes are validated against the Dynamics address format before insert.

PayTraq Suppliers map to Dynamics 365 Vendor records. Vendor currency, payment terms, and tax ID transfer directly. Dynamics 365 distinguishes Vendors from Customers by record type; we set the Vendor type during insert. Any PayTraq supplier with a negative balance (creditor) is flagged for the customer's AP team to reconcile before closing PayTraq.

PayTraq Products and Services merge into Dynamics 365 Item records. Products (inventory items) become Item Type = Inventory; Services become Item Type = Service. Unit of measure, item category, and inventory posting group transfer. The PayTraq SKU becomes the Dynamics Item No. prefix or a custom field. We resolve the item category and posting group references during migration by matching PayTraq category names to Dynamics setup tables.

PayTraq Services are imported as Dynamics 365 Item records with Item Type = Service. Unlike inventory items, service items do not carry stock. We map the service price list to the Sales Price on the Item Card and flag any service items that should be linked to a Resource or Resources group in Dynamics 365.

PayTraq price list rows migrate to Microsoft Dynamics 365 Sales Price and Purchase Price lines. We preserve currency, minimum quantity, unit of measure, and effective-from and effective-to dates. Dynamics 365 requires a Price List to be attached to a Sales or Purchase header before price lines can insert; we create the Price List records before loading line data.

PayTraq Invoices (issued to customers) map to Microsoft Dynamics 365 Sales Invoice records. Invoice header fields (invoice number, date, due date, currency, tax amount) transfer to the Dynamics invoice header. Invoice lines with product references, quantity, unit price, and discount transfer as Sales Invoice Lines with G/L Account references resolved. Multi-currency invoices require the exchange rate to be present in the Dynamics currencies table; we validate or insert rates during the migration window.

PayTraq Purchase Orders map to Dynamics 365 Purchase Order records. We map PO headers and lines, preserving supplier reference, order date, and expected delivery date. Any PO that was fully received in PayTraq migrates as a Posted Purchase Receipt with the PO header for audit trail. Partially received POs are flagged for the customer's AP team to complete receiving in Dynamics 365.

PayTraq Journal Entries map to Dynamics 365 General Journal lines. Each journal entry is a header with multiple debit and credit lines. We map account number, debit amount, credit amount, and description. Dynamics 365 requires the journal batch name to be established before lines insert. Prepaid expense journal entries (PayTraq prepaid allocation schedules not exposed via API) are flagged for manual reconstruction in Dynamics 365; we migrate the current unallocated balance as a journal entry with a note to the accountant.

PayTraq warehouse locations map to Dynamics 365 Warehouse records. On-hand quantities per product per warehouse are reconstructed from individual product-warehouse API reads (PayTraq has no bulk warehouse export) and written to Dynamics 365 as Item Ledger Entries for initial inventory. Dynamics 365 Warehouse Management (if licensed) requires location directives and inventory put-aways; we document these as configuration steps outside the data migration scope.

PayTraq employee records migrate to Dynamics 365 Worker records (Human Resources module in Business Central Premium or Finance and Operations). Compensation fields, employment start date, and department map to the corresponding Worker fields. We flag any Worker records that require a new User to be provisioned in Dynamics 365 for login access.

PayTraq Fixed Assets (acquisition cost, depreciation schedule, linked GL accounts) map to Dynamics 365 Fixed Asset records. We migrate asset name, acquisition date, acquisition cost, depreciation method, and useful life. Accumulated depreciation books transfer to the Fixed Asset Depreciation Book. We flag depreciation methods for review against Dynamics 365's supported depreciation convention list; certain PayTraq methods may require manual adjustment in the Fixed Asset setup.

PayTraq financial loans map to Dynamics 365 Fixed Asset records with a linked recurring general journal template for principal and interest postings. The loan principal and interest schedule transfer as journal entry templates. We preserve the loan ID reference in a custom field for reconciliation. Interest calculation methods require manual validation against Dynamics 365's loan amortization setup.

PayTraq tax codes and rates map to Dynamics 365 Tax Groups and VAT Business Posting Groups. We map the tax rate percentage and applicability (sales vs. purchase) to the corresponding Dynamics tax setup. The customer must configure Tax Posting Groups in Dynamics 365 before tax-enabled transactions can post; we flag this as a required pre-migration configuration step and deliver a tax mapping table with the PayTraq tax codes and their intended Dynamics 365 equivalents.