Migrate your Tuhund data

Tuhund maintains separate 'company' and 'person' records for B2B and B2C contacts. The API exposes list and register endpoints for both. We map these to Contacts or Accounts in the destination CRM depending on the target schema.

Tuhund's multi-branch architecture means the same entity (customer, product, user) can exist with different configurations per branch. We scope the migration to a named branch or replicate across all branches explicitly, based on the customer's operational structure.

Workflows and approvals in Tuhund are often scoped to departments. We preserve department associations on users, expense claims, and purchase orders, but mapping to flat organizational structures in some destinations requires a custom field rather than a native object.

Tuhund's Sales module exposes APIs for registering quotations and proforma invoices. We export these as line-item documents with pricing, quantity, and product references intact.

List and register APIs exist for commercial invoices. We pull invoice headers, line items, and totals. Tax calculation logic in Tuhund is destination-side; we preserve the base amounts and flag where taxes need re-application.

The Inventory module has product detail and stock status APIs. We export product records including categories, stock levels per location, and material allocation. Stock balances are migrated as static snapshots at cutover time.

Procurement module exposes purchase order list and detail APIs. We export open and closed POs including line items, vendor references, and GRN (Goods Receipt Note) associations.

Tuhund's Services module handles service requests, job cards, warranties, and solutions databases. We map service request records and linked job card statuses to the destination support or services module.

Expense claims with item-level details, approval statuses, and amounts are exposed via dedicated APIs. We export the full claim hierarchy including expense items, but approval workflow state is migrated as a snapshot rather than a running process.

The Project module supports internal and external stakeholder engagement. Task hierarchies, assignees, and milestones are available, but custom fields at project level require schema inspection before mapping to flat task structures in some destination PM tools.

Tuhund's user records carry branch and department associations and role assignments. We export users with their organizational assignments, but role mappings are destination-dependent since Tuhund's permission model is not fully documented in the API.

An Attachment Download API exists for retrieving files. We pull attachments associated with service requests, expense claims, and documents, but the listing API does not expose all attachment types. We confirm coverage during discovery.