Migrate from Tuhund to Microsoft Dynamics 365 Business Central

Tuhund company records (B2B entities) map directly to Dynamics 365 Account. The company name becomes Account Name, the registered address maps to the primary address fields, and any company-level GST registration number migrates to a custom Account-level field. Deduplication uses company name and GST number as the composite key. We create the Account before any Contact import so that the parentcustomerid relationship is satisfied at Contact insert.

Tuhund person records (B2C contacts) map to Dynamics 365 Contact. First name and last name are split from the Tuhund full-name field. Email, phone, and address data migrate to Contact standard fields. We link each Contact to a parent Account (from the Tuhund company mapping) when the person record carries a company association; standalone person records create Contacts without a parent Account assignment. Mobile number migrates to the Contact MobilePhone field and any secondary phone to Business Phone.

Tuhund's multi-branch architecture requires architectural mapping during scoping. For Dynamics 365 Finance and Operations, branches map to Business Units in the organizational hierarchy, preserving branch-specific product availability and financial dimension configurations. For Business Central, branches map to company entities or custom fields depending on whether the customer uses the multi-company or single-company with dimensions deployment pattern. We inspect Tuhund's branch-level field schema during discovery before finalizing the mapping.

Tuhund department associations on users, expense claims, and purchase orders map to Dynamics 365 financial dimensions (Department) or to a custom Department field on the User entity depending on the Dynamics 365 edition and configuration. Department-to-Dynamics dimension mapping is confirmed during schema inspection. Approval routing references are not migrated as active workflows but documented as a list for the customer's admin to rebuild in Power Automate.

Tuhund quotations with line items, pricing, quantity, and product references map to Dynamics 365 Quote. The quotation validity period, currency, and payment terms migrate to Quote header fields. Line items map to Quotation Lines with product references resolved to Released Products in Dynamics 365. Quotation status (open, accepted, rejected) maps to a custom status field because Dynamics 365 Quote does not have a closed-lost equivalent by default.

Tuhund commercial invoices map to Microsoft Dynamics 365 Sales Invoice or Free Text Invoice depending on whether the invoice references products from the inventory module or is a simple tax invoice. Invoice headers migrate with invoice number, date, billing address, and tax registration references. Line items migrate with product, quantity, unit price, tax code, and line amount. Tax calculation logic in Tuhund is destination-side; we preserve base amounts and tax rates as separate fields to enable post-migration tax verification. GSTIN references from Indian-compliant Tuhund invoices map to India-specific Dynamics 365 tax fields if the Dynamics 365 deployment is India-region configured.

Tuhund product records with categories, stock levels per location, and material allocation map to Dynamics 365 Product2 (the catalog entity) with Released Products created for each operating unit. Product categories map to Product Categories in Dynamics 365. Stock levels per warehouse migrate as inventory on-hand quantities via the InventSum and InventDim tables or the Data Management framework data entities. Stock balances are migrated as static snapshots at cutover because live stock positions are transactional state that recalculates from open transactions in the destination.

Tuhund purchase orders with line items, vendor references, and GRN associations map to Dynamics 365 Purchase Order. Open and closed PO statuses migrate. Vendor account is resolved from the Tuhund vendor/supplier record to the Dynamics 365 Vendor (released vendor) account. Line items migrate with item number, quantity, unit, and cost price. GRN-linked receipts do not migrate as separate records; they are documented as a reference for the customer to match against open PO receipts in Dynamics 365 post-migration.

Tuhund service requests and linked job card statuses map to Dynamics 365 Case if the destination includes the Customer Service module. Case origin, priority, and status map from Tuhund service request type, urgency, and stage. Job card statuses and warranty information migrate as Case-level custom fields or to a linked custom job card entity. Solution database entries from Tuhund migrate as Knowledge Article drafts for the customer's service team to review and publish in Dynamics 365.

Tuhund expense claims with item-level details, approval statuses, and amounts map to Dynamics 365 Expense Report if Project Service Automation is licensed. Expense category maps from Tuhund expense type to the Dynamics 365 expense category list. Approval status is not migrated as an active approval workflow because approval chains are configured in Dynamics 365 rather than stored as data. We document the approval hierarchy as a written handoff for the customer's admin to configure in Power Automate or the native expense approval workflow.

Tuhund project hierarchies, milestones, assignees, and tasks map to Dynamics 365 Project (if Project Service Automation is licensed) or to custom project entities in Business Central. Task hierarchies and assignees migrate as Project Task records with the assignment and hours preserved. Custom fields at project level require schema inspection before migration because Tuhund's custom field model at the project level is not publicly documented. Projects without Project Service Automation licensing are documented as a custom entity design for the customer's admin to provision post-migration.

Tuhund users with branch and department associations and role assignments map to Dynamics 365 User. We resolve users by email match against the Azure Active Directory tenant backing the Dynamics 365 instance. Branch and department associations migrate to organizational assignment fields on the User entity. Role mappings are destination-dependent because Tuhund's permission model does not map directly to Dynamics 365 Security Roles and are documented as a role reconciliation task for the customer's Dynamics 365 administrator.