Migrate from Gauss Box ERP to Microsoft Dynamics 365 Business Central

Gauss Box accounting module stores the account hierarchy with account codes used in JOPPD payroll records. We map the account structure to Dynamics 365 Finance and Operations General Ledger, preserving account numbers, names, account type (revenue, expense, asset, liability, equity), and the main account category. JOPPD-specific account codes used in payroll journal entries are flagged for EU compliance review before posting to the destination. Inactive Gauss Box accounts are created as inactive in Dynamics 365 Finance to preserve historical trial balance integrity.

Gauss Box Contacts module with customer type flag maps to Dynamics 365 Finance and Operations Customers (or Business Central Customers). We separate customer and vendor records by type at extraction time since Gauss Box stores both in a unified Contacts module. Customer address records, payment terms, and credit limits transfer directly. Any custom Attribute Set fields on customer records are enumerated during scoping and mapped to Dynamics 365 custom fields or extended as notes.

Gauss Box Contacts module with vendor type flag maps to Dynamics 365 Finance and Operations Vendors. Vendor-specific fields including tax registration, payment terms, W-9/W-8BEN equivalents, and bank account details transfer to the vendor record. Inactive vendor records from Gauss Box are flagged in a pre-migration audit and mapped to a blocked or inactive status in Dynamics 365 to prevent open invoice generation against stale vendor accounts.

Gauss Box Items (inventory and product records) map to Dynamics 365 Finance and Operations Released Products or Business Central Items. We transfer SKU, item name, item type (stockkeeping, service, non-stock), unit of measure, cost method, and pricing tiers. During extraction we run a duplicate SKU audit and flag naming inconsistencies that commonly accumulate in ERP systems over time. Historical transactions referencing deleted Gauss Box items are mapped to a catch-all legacy item record rather than silently dropped.

Gauss Box Work Orders flow from planning through tracking to invoicing. We map Work Order records with status, line items, bill of materials references, and assignment data to Dynamics 365 Finance and Operations Production Orders or Business Central Manufacturing work orders. Custom fields added via Gauss Box Attribute Sets are mapped to production order extension fields or carried as comments if no typed Dynamics 365 field exists.

Gauss Box Projects and Tasks with activity logs, collaboration features, and subtask hierarchies map to Dynamics 365 Finance and Operations Project Management and Accounting or Business Central Projects. We map project timelines, assignees, task statuses, and the activity log as project comments. Project budgets, cost categories, and billing settings transfer to the corresponding Dynamics 365 project structure. Phase and task hierarchies migrate as WBS (work breakdown structure) lines.

Gauss Box Documents (inbound, outbound, and templated documents with custom statuses) store both metadata and binary files. We migrate document metadata as SharePoint-compatible file records or Dynamics 365 Finance attachments linked to the parent entity (customer, vendor, project, work order). Document statuses are mapped to Dynamics 365 document handling status values. Binary files are transferred separately as document attachments; Gauss Box templated documents are inventoried for manual rebuild in Dynamics 365 templates if needed.

Gauss Box Employee records include departments, branches, room reservations, live status, and organizational chart data. We map employment data to Dynamics 365 Finance Human Resources Workers or Business Central Employees, preserving department assignments, branch locations, job titles, employment status, and hire/termination dates. Effective-dated compensation history requires a separate review because Dynamics 365 HR compensation plans use a different data model than Gauss Box payroll records.

Gauss Box JOPPD compliance, automatic payroll calculations, and time tracking records require explicit EU compliance mapping for the destination. JOPPD-specific fields (Croatian payroll reporting) do not have native equivalents in Dynamics 365 Finance HR and must be configured as custom fields or handled through EU payroll add-ons. Time entries from Gauss Box Log In (QR code terminal tracking) map to Dynamics 365 Finance and Operations Attendance or Project Time Entries depending on the use case. We recommend a separate EU payroll compliance review with a Dynamics 365 HR partner before loading historical payroll data.

Gauss Box Equipment records with QR code assignment and warehouse organization map to Dynamics 365 Finance Fixed Assets or Business Central Fixed Assets. We transfer equipment identifier, assigned user, location data, and QR reference. Depreciation books, acquisition values, and useful life schedules are set up as new Fixed Asset records in Dynamics 365 because Gauss Box does not expose fixed asset depreciation schedules in its standard exports.

Gauss Box Log In module tracks working hours via QR code terminals. We migrate time entries, user assignments, and attendance summaries to Dynamics 365 Finance and Operations Attendance journals or Business Central time sheets. Attendance records are mapped to the corresponding Worker and linked to any open Project or Production Order for job costing. QR terminal assignment data has no Dynamics 365 equivalent and is noted as a manual configuration item.

Gauss Box Custom Attribute Sets are organization-specific custom fields added across multiple module types. We enumerate all custom attributes during scoping, classify them by data type (date, datetime, single-select, free-text, numeric), and map them to typed Dynamics 365 custom fields. Fields with data types that cannot map to a typed Dynamics 365 field (such as Gauss Box-specific enumerated values) are flagged and carried as text fields or as note attachments with customer sign-off before loading. This step requires the most customer collaboration because attribute naming conventions vary by Gauss Box organization.