Migrate from Gauss Box ERP to Dolibarr ERP

Gauss Box stores account hierarchies in its accounting module. We map the account structure to Dolibarr's accounting plan, flagging inactive accounts and preserving account codes used in JOPPD payroll records. Dolibarr supports both simple and full accounting modes; the customer's choice of accounting mode during Dolibarr setup determines the exact account structure we deploy. Inactive Gauss Box accounts migrate as archived records with a note field indicating the original account status.

Gauss Box's Contacts module stores customers and vendors as a unified record type with a type flag. We separate these at migration time into Dolibarr ThirdParty records classified as Customer or Supplier. Any Custom Attribute Set fields attached to contact records migrate to Dolibarr extrafields with type-mapped equivalents (date fields, select fields, free text). Dolibarr stores address records separately from the ThirdParty; we create Address records linked to the migrated ThirdParty using the address data present in Gauss Box.

Gauss Box Items map to Dolibarr Products (type=product) or Services (type=service) based on the Gauss Box item type flag. We map SKUs from the Gauss Box reference field, units of measure, and pricing tiers. Duplicate SKUs and naming inconsistencies are flagged in the pre-migration audit and consolidated into a catch-all legacy item record; historical transaction lines referencing deleted SKUs are mapped to this legacy item rather than dropped silently.

Gauss Box Work Orders (planning through tracking to invoicing) map to Dolibarr Projects with Tasks representing work order line items. Gauss Box Work Order status flows map to Dolibarr Project status values; the customer defines this mapping during scoping. Custom Attribute Set fields on Work Orders migrate to Dolibarr extrafields on the Project object. Work Order assignment data maps to Task assignees via Dolibarr's contact-assignment model.

Gauss Box Projects and Tasks map directly to Dolibarr Projects and Tasks. Project timelines, assignees, and task statuses transfer directly. Gauss Box activity logs are preserved as Project-level notes (using Dolibarr's note field or as attached text documents) since Dolibarr does not have a native activity log equivalent at the project level. Subtask hierarchies map to Dolibarr Task parent-child relationships.

Gauss Box Documents (inbound, outbound, templated) with custom statuses migrate as binary file attachments linked to the appropriate Dolibarr object (ThirdParty, Product, Project, Proposal, Invoice). Document metadata (status, type, date) is stored in a Dolibarr note field on the attachment record. Dolibarr's document directory structure is created to match the migrated hierarchy. Custom document statuses are mapped to the closest standard Dolibarr document status and documented for admin review.

Gauss Box Employee records map to Dolibarr Users with the Employee module enabled. Department and branch assignments migrate as Dolibarr department records and User properties. Dolibarr's HR module supports employee records with contact info, position, and organizational hierarchy, though Gauss Box's more elaborate organizational chart views do not have a direct Dolibarr equivalent and are preserved as a structured note document for the HR admin to reference.

Gauss Box JOPPD payroll compliance records (Croatian EU payroll standard) require EU-specific field mapping. Dolibarr's HR module does not include a native JOPPD-compliant payroll engine; we migrate the historical payroll records as read-only data (as a structured CSV import and accompanying PDF of historical records) for compliance retention, and flag for the customer's HR admin to evaluate a dedicated EU payroll add-on or external system for ongoing payroll processing. This is a known Dolibarr limitation for Croatian EU compliance.

Gauss Box Equipment records with QR code identifiers and location data map to Dolibarr Assets. QR code values migrate as the Asset serial number or a custom Asset extrafield. Assigned user references are resolved to Dolibarr User records at migration time. Warehouse organization data maps to Dolibarr warehouse/location records under the Stock module.

Gauss Box Log In module records (QR code terminal check-ins, working hours) map to Dolibarr Timesheets linked to Users. Attendance summaries and time entries migrate as Dolibarr time records. Gauss Box's live status tracking does not have a direct Dolibarr equivalent; we preserve this as a note on the relevant Employee record. Dolibarr's Holiday module handles leave requests separately from timesheets.

Gauss Box Custom Attribute Sets (organization-specific custom fields across modules) enumerate during scoping and are mapped to Dolibarr extrafields. We handle data type translation: Gauss Box date fields become Dolibarr date extrafields; select fields become Dolibarr select extrafields; free-text fields become varchar or text extrafields. The customer signs off on the extrafield schema before migration. Any Attribute Sets with no Dolibarr equivalent are preserved as structured note content on the relevant record.

Gauss Box User roles map to Dolibarr permission sets under the HR module's menu security configuration. Role semantics differ significantly between platforms; we map role names to the closest Dolibarr permission profile and deliver a written role-mapping document for the customer's admin to verify and adjust post-migration. Active vs inactive user status is preserved in a Dolibarr user property field.