Migrate from Tuhund to Odoo ERP

Tuhund maintains separate 'company' and 'person' records for B2B and B2C contacts. We map Tuhund Company records to Odoo Contact with the is_company checkbox enabled and the company_name field populated from Tuhund's company_name. Tuhund Person records map to Odoo Contact with is_company disabled. The Tuhund contact type (B2B vs B2C) is preserved in a custom field tuhund_contact_type__c for segmentation and reporting in Odoo.

Tuhund's multi-branch architecture means customers, products, and users can have different configurations per branch. We map branches to Odoo Company records if the customer needs strict data isolation per entity (separate Chart of Accounts, warehouse, or user access). If the customer runs a single legal entity with branch-level reporting tags, we map branch to a custom tuhund_branch__c picklist field on Contact, Product, and Stock Quant. The choice is made during scoping based on how Tuhund's branch data is currently used.

Tuhund departments scope approval workflows on expense claims, purchase orders, and service requests. We export department associations on user records and attach them to hr.employee in Odoo. Approval routing tied to Tuhund departments does not migrate because Odoo Approvals operates on document-level rules rather than department-level hierarchies. We deliver a written inventory of every active approval chain with the recommended Odoo Approvals or server action configuration for the customer's admin to rebuild.

Tuhund Sales Quotations map to Odoo sale.order in draft state. Line items transfer with product reference, quantity, unit of measure, and price. The tuhund_quotation_type__c field distinguishes between standard quotation and proforma invoice so that Odoo sale.order records are flagged accordingly. Sales order confirmation in Odoo is gated as a manual action post-migration; we do not auto-confirm migrated quotations.

Tuhund commercial invoices map to Odoo account.move with move_type='out_invoice'. Invoice headers, line items with tax breakdown, and totals transfer directly. Tax calculation logic is Odoo-side; we preserve the base amounts and tax amounts as separate lines so that Odoo's tax engine can recompute totals during first posting. We flag any rounding differences exceeding 0.01 per line for the customer's accounting team to review post-migration.

Tuhund product records map to Odoo product.product with categories mapped to product.category. Stock levels per location transfer to stock.quant records as a static snapshot at migration time. Tuhund material allocation data maps to product MPRouting or product.bom if the customer uses Odoo's manufacturing module; otherwise it is preserved in custom fields for reference. We verify that Tuhund product types (stockable, consumable, service) map correctly to Odoo's product.product type field.

Tuhund purchase orders map to Odoo purchase.order with vendor reference, line items, and GRN (Goods Receipt Note) associations preserved as custom fields. PO status (draft, sent, confirmed, done) maps to Odoo state. Goods Receipt Notes in Tuhund map to Odoo stock.picking records with picking_type set to incoming. We resolve vendor records against the Tuhund company/person contacts before PO import so that partner_id is populated on purchase.order.

Tuhund service requests map to Odoo helpdesk.ticket. Request status, priority, assigned technician, and linked customer contact transfer directly. Tuhund warranty information maps to a custom tuhund_warranty__c field on the ticket. If the customer uses Odoo Project instead of Helpdesk for service tracking, we map to project.task with the project scoped to a services project created during schema setup.

Tuhund job cards map to Odoo project.task records under a services project. Job card status (open, in progress, closed) maps to Odoo task stage. Technician assignment and time logging migrate to Odoo's timesheet grid if the project is configured for timesheets. Job card-to-service-request linkage is preserved as a custom tuhund_jobcard_id__c field for traceability.

Tuhund expense claims with item-level detail, approval status, and amounts map to Odoo hr.expense.sheet. Expense items migrate as hr.expense.line records with product, quantity, unit price, and tax. Approval status is not migrated as active approval state because Odoo expense approval is destination-side; we set all migrated expense sheets to draft and deliver an approval-chain inventory for the admin to configure in Odoo. Amount totals reconcile against Tuhund totals before import commits.

Tuhund project and task hierarchies map to Odoo project.project and project.task. Task assignees, milestones, and parent-child relationships transfer directly. Custom fields at the project level require schema inspection before migration; we inspect the Tuhund field schema during discovery and create matching custom fields in Odoo before any project data moves. Task timesheets migrate to Odoo's timesheet model if the project has timesheet tracking enabled.

Tuhund user records carry branch and department associations and role assignments. We export users with their organizational assignments and map them to Odoo res.users. Role mappings are destination-dependent because Tuhund's permission model does not map directly to Odoo's access rights and record rules. We deliver a user-role inventory listing each Tuhund role and recommending the corresponding Odoo access group for the customer's admin to configure post-migration.