Migrate from Tuhund to Dolibarr ERP

Tuhund Company records (B2B contacts) map to Dolibarr ThirdParty in Company mode. The Company name maps to the name field, address and phone fields map directly, and the email maps to the email field. We use the ThirdParty email as the dedupe key during import. Branch associations from Tuhund are preserved in a custom text field tuhund_branch__c for audit and reporting in Dolibarr.

Tuhund Person records (B2C contacts) map to Dolibarr ThirdParty in Individual mode. First name and last name split from the Tuhund full-name field using name-order detection, and the email maps to the email field. Individual mode enables Dolibarr's contact-specific fields (birthday, personal address) while preserving the original Tuhund Person ID in a custom field tuhund_person_id__c.

Tuhund's multi-branch architecture has no direct Dolibarr equivalent because Dolibarr's third-party records are flat without branch inheritance. We map branch membership by creating a Dolibarr Tag for each Tuhund branch (e.g., branch_mumbai, branch_bengaluru) and attaching it to all third parties belonging to that branch via the Tag/Category system. This preserves branch provenance without requiring a custom branch object.

Tuhund departments associate with users, expense claims, and purchase orders. Dolibarr has no native department object, so we create a custom extrafields dropdown tuhund_department__c on Dolibarr User and Project records, populating it with the distinct department names from Tuhund. This keeps department provenance for audit without affecting Dolibarr's access control model.

Tuhund Sales Quotations and Proforma Invoices map to Dolibarr Commercial Proposal (Propal). We map line items (product reference, quantity, unit price, discount) directly, preserve the quotation date and expiry date, and link the proposal to the corresponding ThirdParty. The tuhund_quotation_id__c field stores the original Tuhund document ID for reconciliation.

Tuhund Commercial Invoices map to Dolibarr Invoice. Invoice header fields (number, date, due date, total, tax amount) migrate with line items intact. Tuhund's tax calculation logic is not migrated; we preserve base amounts and tax amounts as separate fields in Dolibarr, and the customer reconciles tax accounts during post-migration setup. Invoice status (Draft, Validated, Paid, Cancelled) maps to Dolibarr's fk_statut.

Tuhund product records map to Dolibarr Product. We preserve product categories (mapped to Dolibarr Product Category), stock levels per location, and the SKU/reference field. Stock balances migrate as static values at migration time; we flag any product with zero stock for inventory count reconciliation post-migration.

Tuhund stock locations map to Dolibarr Warehouse. Each warehouse record in Dolibarr stores the physical location, and stock entries per product per warehouse are created from Tuhund's stock-level data. Multi-location setups (one warehouse per Tuhund location) are preserved; if Tuhund has a single stock location, we default to the Dolibarr Default warehouse.

Tuhund Purchase Orders map to Dolibarr Purchase Order. We map vendor reference (linked to the Tuhund vendor ThirdParty), PO number, line items, quantities, and amounts. The GRN (Goods Receipt Note) association from Tuhund is preserved as a custom field tuhund_grn_ref__c on the Dolibarr receipt line, but GRN itself is not a separate Dolibarr object unless the Receipt module is activated.

Tuhund GRN records link to purchase orders and inventory updates. Dolibarr's Reception module (activated as part of the Purchase workflow) handles supplier receipt recording. We map GRN fields (receipt date, vendor, received quantities) to Dolibarr Reception, linking each receipt to the corresponding Purchase Order line item and updating product stock accordingly.

Tuhund Service Requests map to Dolibarr Ticket, and Job Cards map to Dolibarr Intervention (if the Interventions module is activated). We preserve request status, priority, requester ThirdParty link, and the job card timeline. Warranty tracking from Tuhund's Services module is stored as a custom field tuhund_warranty_end_date__c on the Ticket or Product record, as Dolibarr's warranty tracking requires a community add-on module.

Tuhund Expense Claims map to Dolibarr Expense Report if the HR module is activated. We migrate claim headers (submitter user, department, approval status), individual expense items (category, amount, date, description), and totals. Tuhund approval workflow state migrates as a read-only status field; approval routing is not migrated as Dolibarr does not replicate the same approval chain model.

Tuhund Projects map to Dolibarr Project, and tasks map to Dolibarr Task with parent project linkage. Milestones from Tuhund map to Dolibarr Project milestones if the Project module is configured accordingly. Assignees resolve by email against the Dolibarr User table. Custom fields at project level require schema inspection before import.

Tuhund User records map to Dolibarr User. We resolve by email match and preserve the Tuhund role assignment and branch/department associations in Dolibarr extrafields. Tuhund's permission model does not map to Dolibarr's permission set system; we deliver a role-reconciliation table as part of the migration output.

Tuhund attachments associated with service requests, expense claims, and documents are downloaded via the Attachment Download API and stored in Dolibarr's documents directory, linked to the corresponding record via ContentDocumentLink. We flag attachments where the listing API does not expose the full set; the customer verifies completeness against Tuhund's document storage during the scoping walkthrough.