Migrate from Gauss Box ERP to Odoo ERP

Gauss Box account structures map to Odoo's account.account with account.type and account.code preserved. JOPPD-specific tax accounts are flagged for Croatian payroll module configuration in Odoo. Inactive Gauss Box accounts map as archived records in Odoo rather than deleted. We preserve the full account code hierarchy for audit trail continuity.

Gauss Box's Contacts module holds both customers and vendors in a single table with a type field. We separate these into res.partner records with partner_type set to 'customer' or 'supplier' in Odoo. Custom Attribute Set fields on Gauss Box contacts map to res.partner custom fields (x_ prefixed). Vendor tax IDs and customer payment terms migrate as notes or dedicated fields depending on Odoo configuration.

Gauss Box Items map to Odoo product.product with SKU preserved as default_code and product name as name. Units of measure migrate from Gauss Box uom fields to Odoo uom.uom records. Pricing tiers ( Gaul Box 'price lists') map to Odoo product.pricelist entries. Duplicate SKUs and inconsistent naming are flagged in pre-migration audit and remediated before import; historical transactions referencing deleted SKUs map to a catch-all legacy product record.

Gauss Box Work Orders cover both production manufacturing and field-service task tracking. We classify each Work Order by its status and line item type: production-oriented Work Orders map to Odoo mrp.production (Manufacturing app); service or project-oriented Work Orders map to project.task linked to an Odoo project. Work Order line items, assignments, and status history migrate. Custom fields from Attribute Sets map to x_ fields on the respective Odoo model.

Gauss Box Projects map to Odoo project.project with project budgets and team assignments preserved as Odoo project allocation fields. Task hierarchies (parent task, subtask) map to Odoo task hierarchy via parent_id. Activity logs from Gauss Box project collaboration migrate as Odoo mail.message records on the project. Assignees resolve by email against Odoo res.users.

Gauss Box Documents (inbound, outbound, templated) migrate to Odoo ir.attachment with res_model set to the related Odoo model (res.partner, account.move, mrp.production, etc.). Document binary files migrate separately from metadata. Custom Gauss Box document statuses (e.g., approved, rejected, archived) map to Odoo workflow states or ir_attachment.res_field. Template documents migrate as Odoo document templates if the Documents app is enabled.

Gauss Box Employees map to Odoo hr.employee with department assignments from Gauss Box mapped to Odoo hr.department. Branch locations migrate as Odoo hr.department with parent_id for multi-branch hierarchies. Employee custom fields (e.g., personal ID, emergency contact) from Gauss Box Attribute Sets map to x_ fields on hr.employee. Historical department assignments migrate as Odoo hr.employee logs.

Gauss Box JOPPD compliance records, automatic payroll calculations, and time entries require a Croatian payroll module in Odoo (Odoo Community Association l10n_hr_payroll or a third-party module). We migrate time entries as Odoo hr.attendance records and payroll summaries as hr.payslip.employee_salary_batches where supported. If the destination Odoo instance lacks a JOPPD module, we deliver a written configuration plan for the customer's Odoo partner to implement.

Gauss Box Equipment with QR codes maps to Odoo asset management (account.asset) for capital equipment and stock.quant for warehouse-tracked items. QR code identifiers migrate as Odoo lot_id or serial number fields. Assigned user and location data migrate as Odoo asset owner and location fields.

Gauss Box Log In module (working hours via QR code terminals) maps to Odoo hr.attendance with check_in and check_out times. User assignments resolve by email to Odoo res.users. Attendance summaries migrate as Odoo hr.attendance records ordered by date for continuity of historical attendance data.

Gauss Box Attribute Sets are enumerated during scoping and mapped to Odoo ir.model.fields with x_ prefixes. Field type mapping is required: Gauss Box date fields map to Odoo date fields, single-select attributes to Odoo selection fields, multi-select to Odoo many2many_tags, and free-text to Odoo char or text fields. All custom field mappings require customer sign-off before Odoo schema deployment.

Gauss Box user roles with per-module access levels map to Odoo res.groups. Role semantics differ: Gauss Box roles are module-level feature gates, while Odoo groups control access at the model and record level. We map the functional intent (e.g., 'Sales user can view Leads') to the nearest Odoo group and document gaps for manual admin configuration.

Gauss Box provides 50+ dashboard widgets as a platform-specific visualization layer. These are not portable. We do not migrate dashboard configurations. We deliver a written inventory of active Gauss Box widgets with Odoo reporting equivalents (Odoo Reporting app, BI dashboard, or third-party Odoo Apps Store tools) for the customer's admin to configure post-migration.