Migrate from Tuhund to Epicor Prophet 21

Tuhund Company records (B2B) map to Epicor Customer. The Company name becomes Customer.CustID and Customer.Name. Billing and shipping addresses from Tuhund map to CustomerBillTo and CustomerShipTo respectively. Branch associations on Tuhund Companies require resolution: a Tuhund Company scoped to Branch-A may need to become a separate Epicor Customer or a Customer with a site in a specific Plant/Warehouse. We determine this during scoping based on whether the Tuhund branches represent separate legal entities or operational divisions of the same customer.

Tuhund Person records (B2C or individual contacts) map to Epicor Customer if they represent a billing entity, or to Contact records attached to a Customer if they represent an individual within an existing account. The Tuhund person_type property determines whether the record is a standalone customer or a linked contact. Email, phone, and address fields migrate directly; Tuhund's branch association maps to the Contact's Plant or Department reference in Epicor if used.

Tuhund Sales Quotations map to Epicor Quote. The quotation header (quotation number, date, validity, terms) migrates directly. Line items with product references, quantity, pricing, and discounts map to QuoteLine. We resolve the PartNum reference from Tuhund's product code to Epicor's Part master during the line-item phase. Open/closed quotation status maps to a Quote status flag in Epicor.

Tuhund Commercial Invoices map to Epicor AR Invoice (InvcHead and InvcDtl). Invoice number, date, tax amounts, and totals migrate from the Tuhund commercial_invoice endpoint. Line items map to InvcDtl with PartNum resolved to Epicor's Part master. Tax calculation logic in Tuhund is destination-side; we preserve the base amounts, tax rate, and tax jurisdiction code, and flag any invoices where the Tuhund tax calculation may need to be recomputed in Epicor's tax engine.

Tuhund Product records map to Epicor Part. Product code becomes Part.PartNum; description and category map to Part.SearchDescription and Part.PMGClass. Stock levels per Tuhund stock location map to PartWhse records across Epicor sites and warehouses. Lot/Serial tracking in Epicor is enabled per Part; if Tuhund uses lot numbers on inventory transactions, we map them to Epicor's PartLot table. Stock balances are migrated as a static snapshot; we flag to the customer that Epicor will recompute on-hand quantities from transactional history post-migration.

Tuhund Purchase Orders map to Epicor POHeader and POLine. The vendor reference from Tuhund resolves to a Supplier in Epicor. Open and closed PO status migrates with the current approval status preserved in a custom field. POLine items carry PartNum (for stocked parts) or a description-only line (for non-stocked items). Tuhund's GRN (Goods Receipt Note) association is preserved as a reference comment on the POLine since Epicor's receiving process generates its own receipt records.

Tuhund GRN records map to Epicor Receipt Entry (RcvHead/RcvDtl). The GRN-to-PO linkage in Tuhund resolves to Epicor's PO Receipt reference. Received quantity, unit cost, and warehouse assignment map from the Tuhund goods_receipt API response to RcvDtl. If Tuhund stores inspection status or lot numbers on the GRN, these map to RcvDtl.UserData fields that we configure as part of the UD field provisioning phase.

Tuhund Service Requests do not have a direct Epicor equivalent outside of the optional Service Module. If Epicor Service is licensed, Service Requests map to Cases with status mapping (Open to Open, In Progress to In Process, Resolved to Resolved). If Epicor Service is not licensed, we map Service Requests to a custom UD table or to the Cases table via an extension. Warranty information from Tuhund's warranties database migrates to Case fields or UD fields on the Case record.

Tuhund Job Cards map to Epicor Job Entry (JobHead/JobMtl/JobOpr) only if Epicor Manufacturing is licensed. Job card status (Open, In Progress, Closed) maps to JobHead.JobReleased, JobHead.JobComplete, and JobHead.JobClose. Tuhund's linking of job cards to service requests maps to Epicor's LinkToContract/LinkToCase fields if the Service Module is active. If Epicor Manufacturing is not in scope, Job Card data is migrated to a custom UD table with a written schema definition for the customer's admin.

Tuhund Expense Claims map to Epicor's AP Expense Entry or to a custom UD table depending on whether the Epicor Financials module handles per-diem and receipt-based expenses. Expense line items (amount, category, currency) migrate to expense detail records. Approval status from Tuhund migrates as a read-only field; the actual approval workflow is Epicor BPM-driven and must be rebuilt. Tuhund's department-scoped approval rules are documented in the workflow inventory for the customer's admin.

Tuhund Project records map to Epicor Project if the Project Management module is licensed. Task hierarchies, assignees, milestones, and due dates migrate to ProjectPhase and ProjectTask. If Epicor Project is not licensed, Project data migrates to a custom UD table. Tuhund's custom fields at project level require schema inspection before import; these map to UD fields on the Epicor Project record that we provision during the UD field scoping phase.

Tuhund User records map to Epicor User by email address match. Branch and department associations on Tuhund users map to Epicor Plant and Department references, or to UD fields if the organizational structure is more complex. Any Tuhund user without a matching Epicor User is held in a reconciliation queue; the customer's Epicor admin provisions the User in Epicor before record migration proceeds. Role and permission mappings are destination-dependent and documented as a written role map for the customer's admin.