Migrate from Tuhund to Infor CloudSuite Corporate

Tuhund Company records (B2B contacts) map to Infor CloudSuite Customer Party records. We use the Company name as the Account name and the registered address fields as the primary address. GSTIN and CIN from Tuhund migrate to custom identifier fields on the Customer Party. Tuhund branch-specific company configurations require resolution: if the same company exists with different data per branch, we consolidate into a single Customer record with the most recent active configuration, flagging branch-specific variations for manual review in CloudSuite.

Tuhund Person records (B2C contacts) map to Infor CloudSuite Contact records attached to an Anonymous or Consumer Party. Where a Person record has an associated Company, we link the Contact to that Customer Party. Mobile and email from Tuhund migrate to the Contact communication fields; the Tuhund person_type (customer, supplier, staff) determines whether the Contact attaches to a Customer or Supplier Party in CloudSuite.

Tuhund's Branch entity maps to Infor CloudSuite Site. The branch code becomes the Site code, and branch-level address details migrate to the Site address. Tuhund's multi-branch architecture means the same customer, product, or user can exist with different configurations per branch; we scope the migration to a named branch or replicate across all branches depending on the customer's requirements. Branch-level custom fields migrate as Site-level extension attributes if supported by the CloudSuite edition.

Tuhund Department records map to Infor CloudSuite Department or Business Unit depending on the CloudSuite edition. Workflow and approval chains scoped to departments in Tuhund do not migrate as automation; we document the department-to-approver matrix and deliver it as a written handoff for the customer's Infor administrator to configure in Infor OS Ming.le. Mapping to flat organizational structures in CloudSuite requires admin discretion on whether to preserve the hierarchy or consolidate.

Tuhund Product records map to Infor CloudSuite Item master records. The product category from Tuhund maps to the Item Product Group or Category in CloudSuite. Stock levels per location migrate as on-hand quantity records against the mapped Site and Warehouse. Tuhund's Material Allocation data migrates as a static on-hand quantity note; live allocation tracking is destination-side. The product hs_sku equivalent migrates to the Item code or cross-reference field.

Tuhund stock locations per branch map to Infor CloudSuite Warehouses within the corresponding Site. We reconcile Tuhund's stock location codes against CloudSuite's warehouse structure before migration to avoid duplicate warehouse creation. If a Tuhund stock location spans multiple branch inventories, we flag the mapping for manual consolidation or multi-warehouse split as appropriate.

Tuhund Sales Quotations and Proforma Invoices map to Infor CloudSuite Sales Order records with a Quote or ProForma document type. Line items, pricing, quantity, and product references migrate intact. Status mapping: Tuhund's quotation status (open, accepted, expired, rejected) maps to CloudSuite Order Status values. If the quotation has an expiry date in Tuhund, we set the corresponding field in CloudSuite or flag for manual status update post-migration.

Tuhund Commercial Invoice records map to Infor CloudSuite Invoice records. Invoice headers, line items, and totals migrate directly. Tax calculation logic in Tuhund is destination-side; we preserve the base amounts, tax rates, and tax codes as extracted from Tuhund and validate against CloudSuite's tax configuration during the import run. We flag any invoices where Tuhund's tax calculation differs from CloudSuite's computed amount for manual review.

Tuhund Purchase Orders map to Infor CloudSuite Purchase Orders. Line items, vendor references, and GRN associations migrate directly. Open and closed PO status maps to CloudSuite PO status. Tuhund's vendor reference (Supplier) resolves against the mapped Customer Party where vendor_type equals supplier in Tuhund. If the Tuhund PO has associated Goods Receipt Notes, we migrate the GRN as a receiving transaction against the PO in CloudSuite.

Tuhund GRN records map to Infor CloudSuite receiving transactions or inventory receipt records. The GRN is linked to the corresponding Purchase Order and Item. Receipt quantity and date migrate directly; receipt status (pending, partial, complete) maps to the CloudSuite transaction status. GRN notes and inspection results migrate as transaction comments.

Tuhund Service Request records map to Infor CloudSuite Service Management Request or Case records depending on the CloudSuite edition's service module availability. Request status, priority, description, and linked customer party migrate. Job card associations from Tuhund map to task or work order records within the Case or Service Request. Warranty information from Tuhund migrates as entitlement or coverage records in CloudSuite where supported.

Tuhund Job Card records map to Infor CloudSuite Work Order or Service Task records. Job card status, assigned technician, and linked service request migrate. Solution database entries from Tuhund map to Knowledge Base articles or Service Resolution records in CloudSuite if the Knowledge Management module is licensed.