How long does a Tuhund to Acumatica migration take?

Most Tuhund-to-Acuminica migrations complete in 5–10 business days for under 25,000 records across all modules. Complex setups with inventory, multi-branch configuration, or project module data extend to 3–6 weeks. The longest step is schema preparation in Acumatica — creating Customer classes, Vendor classes, item classes, and any Usr custom fields — which FlitStack surfaces as a checklist before data movement begins. The actual data migration typically runs within 24–48 hours once Acumatica is ready.

Will my Tuhund workflows, approval chains, and automation rules migrate to Acumatica?

No. FlitStack migrates data and schema only — Tuhund workflows, approval chains, sequence rules, and custom automation do not transfer to Acumatica. These constructs are destination-side configuration that must be rebuilt using Acumatica's Screen-Based Workflows, Automation Schedules, or business events. FlitStack exports your Tuhund workflow definitions as structured reference documents listing each rule's trigger, condition, and action so your Acumatica administrator can rebuild them in the new system.

What happens to my Tuhund commercial invoices in Acumatica?

Tuhund commercial invoices from the List of Commercial Invoices endpoint map to Acumatica ARInvoice records with DocType='INV'. The Tuhund invoice number becomes ARInvoice.RefNbr, invoice date becomes DocDate, and line items (product, quantity, amount) map to ARTran lines. Customer resolution uses the Tuhund customer name matched to Acumatica Customer.CustomerID. If the Tuhund invoice uses a non-base currency, the currency code and exchange rate must be set up in Acumatica's Currencies screen before the import runs.

Can I migrate Tuhund custom fields to Acumatica custom fields?

Yes, but Acumatica requires custom fields to be pre-created in the schema before import. Tuhund custom fields discovered in the API responses are cataloged by FlitStack and surfaced in the migration plan. For each Tuhund custom field, your Acumatica administrator creates a corresponding Usr-field in the target screen using Acumatica's Customization Project editor or through the screen's schema settings. Once the Usr fields exist, FlitStack maps and imports the values via Acumatica's Import by Scenario. This two-step sequence — create schema first, then migrate data — is mandatory.

What happens to Tuhund purchase orders in Acumatica?

Tuhund purchase orders from the Procurement Module API map to Acumatica POOrder records with POType='Normal'. The Tuhund PO number becomes POOrder.OrderNbr, vendor name resolves to Acumatica Vendor.VendorID, and line items (product, quantity, unit cost) map to POLine with InventoryID and CuryUnitCost. Vendor records must pre-exist in Acumatica before POOrder migration — FlitStack runs a vendor reconciliation step to flag any Tuhund vendors without matching Acumatica Vendor records so they can be created first.

Does the migration affect my Tuhund account during cutover?

No. FlitStack uses scoped read access on Tuhund — your team continues working in Tuhund during the migration with no disruption to daily operations. A delta-pickup window (24–48 hours) runs after the initial migration snapshot, capturing any records created or modified in Tuhund during the cutover period. Those delta records are then merged into Acumatica before go-live so the destination system reflects Tuhund's final state at the moment of switchover.

How does Tuhund inventory data map to Acumatica Stock Items?

Tuhund products from the Product Details API map to Acumatica InventoryItem with ItemType='Stocked Item'. The Tuhund product name becomes InventoryItem.InventoryCD, description maps to Descr, and unit cost maps to StdCost. The unit of measure from Tuhund is mapped to Acumatica's UOM code — non-matching UOMs are flagged for UOM setup. Acumatica requires each InventoryItem to belong to an ItemClass that defines the valuation method (Average, FIFO, Standard); FlitStack defaults to Average and surfaces ItemClass selection as a migration configuration step before inventory import.

What happens to my Tuhund expense claims in Acumatica?

Tuhund expense claims registered via the Expense Claims Integration API map to Acumatica EmployeeExpense documents. The Tuhund claim number becomes EmployeeExpense.RefNbr, claim date becomes DocDate, and total amount maps to CuryOrigDocAmt. Each Tuhund expense item (category, amount, description) becomes an EmployeeExpenseDetail line with an ExpenseCodeID that must exist in Acumatica's Expense Codes list. FlitStack maps Tuhund expense categories to Acumatica Expense Codes and flags any category with no matching code for setup before the import runs.

Tuhund to Acumatica Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Tuhund stores business data across several overlapping modules: CRM (companies, persons, addresses, contact queries), Sales (quotations, proforma invoices, commercial invoices, delivery orders), Procurement (purchase orders), Inventory (products, stock), Services (service requests), Project Management (job cards), Expense Claims, and Shopping Cart. Acumatica models equivalent data using Customers, Vendors, Stock Items, ARInvoices, APInvoices, SROrder, POOrder, CRCase, Project, and EmployeeExpense objects, each with its own branch-keyed schema. The migration must resolve Tuhund's flat company/person model into Acumatica's Customer lookup structure, translate Tuhund's quotation and invoice records into Acumatica's document-line hierarchy, map product records to Stock Items with UOM and unit price, and route service requests into CRCase with the original requester and timestamp preserved. Acumatica's Import by Scenario tool provides the import pathway; FlitStack AI sequences the data so foreign-key relationships (Customer before ARInvoice, Vendor before POOrder) resolve correctly. Workflows, approval chains, and custom automation in Tuhund do not migrate — FlitStack exports workflow definitions as reference documents for Acumatica configuration.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Tuhund

What's pushing teams away

Significant licensing, maintenance, and implementation cost positions Tuhund toward mid-market and enterprise rather than SMB — small organizations may find total cost of ownership prohibitive.
Typical 3-6 month implementation timeline is a meaningful project commitment compared with SaaS-first ERPs that promise faster time-to-value.
Limited public reviewer presence on G2 and Capterra makes peer validation difficult, especially for buyers outside ECS's existing customer regions.
Custom module deployment on top of the core means vendor services are typically required, increasing dependency on ECS for ongoing changes.
Pricing is not published, making early-stage budget conversations difficult without a sales engagement.

Choosing

Acumatica

What's pulling them in

Unlimited user licensing lets companies add staff without per-seat billing shocks, making Acumatica cost-predictable at scale.
Flexibility and scalability earn consistent praise — users value a platform that adapts to vertical workflows without forcing a redesign.
Real-time visibility across financials, inventory, and projects gives mid-market businesses a consolidated operational view previously available only in enterprise-tier ERPs.
Cloud-native architecture with automatic updates removes infrastructure management burden from in-house IT teams.
Modular licensing lets companies start with one or two suites (Financials, Distribution) and expand into Manufacturing or CRM incrementally.

Object mapping

How Tuhund objects map to Acumatica

Each row shows how a Tuhund object lands in Acumatica, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Tuhund

Company

maps to

Acumatica

Customer

1:1

Fully supported

Tuhund company records map directly to Acumatica Customer records. The Tuhund company name becomes Customer.AcctName. Company status in Tuhund determines whether the Acumatica Customer is active or on hold. Tuhund company phone and website fields map to Customer.Phone and Customer.WebSite respectively.

Tuhund

Person (primary contact)

maps to

Acumatica

CustomerContact

1:1

Fully supported

The primary person on a Tuhund company becomes the primary contact on the Acumatica Customer. Tuhund person fields — first name, last name, email, phone, and job title — map to CustomerContact.FirstName, CustomerContact.LastName, CustomerContact.Email, CustomerContact.Phone1, and CustomerContact.JobTitle respectively. The contact is linked to the Customer record via the CustomerID foreign key, ensuring that all communications and activities reference the correct account in Acumatica.

Tuhund

Address

maps to

Acumatica

CustomerAddress

1:1

Fully supported

Tuhund address records attached to a company map to Acumatica CustomerAddress with address line 1, city, state, postal code, and country. Address type in Tuhund (billing vs shipping) maps to Acumatica's address purpose field. Multiple Tuhund addresses per company create multiple CustomerAddress rows with distinct purposes.

Tuhund

Quotation

maps to

Acumatica

Quote

1:1

Fully supported

Tuhund quotation records (Register Quotation API) map to Acumatica Quote. The Tuhund quotation number becomes Quote.DocumentNbr. CustomerRef maps to the linked Acumatica Customer. Each quotation line (product, quantity, unit price) maps to QuoteDetail with InventoryID, OrderQty, and CuryUnitPrice. Tuhund quotation expiry date maps to Quote.ExpirationDate.

Tuhund

Commercial Invoice

maps to

Acumatica

ARInvoice

1:1

Fully supported

Tuhund commercial invoices from the List of Commercial Invoices endpoint map to Acumatica ARInvoice with DocType='INV'. Tuhund invoice number maps to ARInvoice.RefNbr. Customer mappings use the same CustomerID lookup as quotations. Tuhund invoice line items (product, quantity, amount) map to ARTran lines with Acumatica InventoryID and CuryLineAmt.

Tuhund

Delivery Order

maps to

Acumatica

SOShipment

1:1

Fully supported

Tuhund delivery orders (Register Delivery Order API) map to Acumatica SOShipment. The Tuhund delivery order number becomes SOShipment.ShipmentNbr. Customer linked from the original quotation or invoice. Lines map to SOShipmentLine with shipped quantity and the linked InventoryID. Tracking information from Tuhund's Delivery Order Tracking API is preserved as SOShipment.ShipmentTrackingNbr.

Tuhund

Purchase Order

maps to

Acumatica

POOrder

1:1

Fully supported

Tuhund purchase orders from the Procurement Module API map to Acumatica POOrder with POType='Normal'. Tuhund PO number becomes POOrder.OrderNbr. Vendor resolution uses Tuhund vendor name matched against Acumatica Vendor.VendorID. Line items (product, quantity, unit cost) map to POLine with Acumatica InventoryID and CuryUnitCost.

Tuhund

Product (Inventory Item)

maps to

Acumatica

InventoryItem

1:1

Fully supported

Tuhund product records from the Product Details API map to Acumatica InventoryItem with ItemType='Stocked Item'. Product description maps to InventoryItem.Descr. Unit cost from Tuhund maps to the current cost in Acumatica's item site record. UOM requires mapping Tuhund's unit-of-measure to Acumatica's UOM code.

Tuhund

Service Request

maps to

Acumatica

CRCase

1:1

Fully supported

Tuhund service requests (Register Service Request API) map to Acumatica CRCase. The Tuhund service request subject maps to Case.Subject, and description maps to Case.Description. Customer resolution uses the Tuhund customer name matched to Acumatica Customer.CustomerID. Original request date maps to Case.CreatedDateTime.

Tuhund

Expense Claim

maps to

Acumatica

EmployeeExpense

1:1

Fully supported

Tuhund expense claims (Register Expense Claim API) map to Acumatica EmployeeExpense. Each Tuhund expense item (amount, category, description) becomes an EmployeeExpenseDetail line. Tuhund claim status maps to Acumatica EmployeeExpense.Status. The submitting employee is resolved by email match against Acumatica Employees.

Tuhund

Job Card (Project Task)

maps to

Acumatica

PMTask

1:1

Fully supported

Tuhund job cards map to Acumatica PMTask under a PMProject. The job card date and time fields map to PMTask.StartDate and the estimated hours field. Task status in Tuhund maps to PMTask.Status. If Tuhund does not have a project header, a default PMProject is created and all job cards become tasks under it.

Tuhund

Shopping Cart Order

maps to

Acumatica

SOOrder

1:1

Fully supported

Tuhund shopping cart orders (Create Shopping Cart Order API) map to Acumatica SOOrder with OrderType='SO'. Tuhund order details map to SOOrderLine with InventoryID, OrderQty, and CuryUnitPrice. CustomerRef links to the resolved Acumatica Customer. Payment details from Tuhund's Update Payment Details API are noted for reference in SOOrder.

Tuhund	Acumatica	Compatibility
Company	Customer1:1	Fully supported
Person (primary contact)	CustomerContact1:1	Fully supported
Address	CustomerAddress1:1	Fully supported
Quotation	Quote1:1	Fully supported
Commercial Invoice	ARInvoice1:1	Fully supported
Delivery Order	SOShipment1:1	Fully supported
Purchase Order	POOrder1:1	Fully supported
Product (Inventory Item)	InventoryItem1:1	Fully supported
Service Request	CRCase1:1	Fully supported
Expense Claim	EmployeeExpense1:1	Fully supported
Job Card (Project Task)	PMTask1:1	Fully supported
Shopping Cart Order	SOOrder1:1	Fully supported

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Tuhund gotchas

High

Per-customer module configuration creates schema drift

High

No publicly documented developer API

Medium

Long implementation cycles imply long extraction cycles

Low

Geographic vendor presence affects support cadence

Acumatica gotchas

High

API user licenses cap concurrent sessions and request throughput

High

Multi-tenant filtering requires CompanyID awareness

Medium

Custom fields require separate discovery before field mapping

Medium

Notes and attachments use a separate linked table structure

Low

Implementation timelines frequently run 3–9 months end-to-end

Tuhund gotchas		Acumatica gotchas
Severity	Issue	Severity	Issue
High	Per-customer module configuration creates schema drift	High	API user licenses cap concurrent sessions and request throughput
High	No publicly documented developer API	High	Multi-tenant filtering requires CompanyID awareness
Medium	Long implementation cycles imply long extraction cycles	Medium	Custom fields require separate discovery before field mapping
Low	Geographic vendor presence affects support cadence	Medium	Notes and attachments use a separate linked table structure
		Low	Implementation timelines frequently run 3–9 months end-to-end

Pair-specific challenges

Tuhund company-person associations require Acumatica CustomerContact resolution before ARInvoice can link

Tuhund exposes persons as distinct API objects that are linked to companies through explicit relationship records. In Acumatica, the CustomerContact must already be present before an ARInvoice line can attach a ContactID reference. If a Tuhund person lacks a corresponding Acumatica CustomerContact, the invoice line will fail foreign‑key validation. FlitStack resolves this by pre‑creating every required CustomerContact before the ARInvoice migration runs, using email as the unique match key to tie each Tuhund person to the correct Acumatica contact.
Acumatica Import by Scenario requires pre-created schema for custom fields and item classes

Acumatica's Import by Scenario tool can import standard fields directly, but any custom field (fields with Usr prefix in Acumatica's DAC model) requires the field to exist in the target screen schema before import runs. Tuhund custom fields on products and service requests have no automatic mapping to Acumatica Usr fields. FlitStack generates a schema preparation checklist as part of the migration plan — customers create Usr fields in Acumatica first, then the import scenario references them.
Tuhund purchase order vendor lookups must pre-exist in Acumatica Vendor table

Acumatica's POOrder.VendorID field is a mandatory foreign key pointing to the Vendor table, and Acumatica will reject any POOrder record that references a missing or mismatched VendorID. Tuhund vendors retrieved via the Purchase Order List endpoint do not automatically align with Acumatica Vendor records if those records are absent or have a different naming convention. FlitStack therefore executes a vendor reconciliation step prior to POOrder migration, identifying any unmatched vendors and creating the corresponding Acumatica Vendor entries using the Tuhund vendor API payload before the PO import proceeds.
Tuhund inventory valuation method must be mapped to Acumatica item class before stock import

Acumatica mandates that every InventoryItem belong to an ItemClass, and the ItemClass controls the inventory valuation method (FIFO, Average, Standard) as well as the posting and cost‑layer settings. The Tuhund Product Details API does not expose a valuation method, so FlitStack cannot infer the intended class automatically. To keep valuation consistent, FlitStack defaults to the Average method and presents an ItemClass selection screen during migration configuration: customers pick the appropriate class for each product group before the InventoryItem import runs, ensuring that cost layers and GL accounts are set correctly in Acumatica.
Multi-currency Tuhund invoices need Acumatica CuryID and rate setup before ARInvoice import

If a Tuhund invoice is recorded in a currency that differs from Acumatica's base currency, the ARInvoice.CuryID and CuryDocBal fields must be populated with the appropriate currency code and document balance in that currency. Acumatica enforces that the currency be defined in the Currencies screen and that an exchange rate be available for the invoice date before the import proceeds. FlitStack extracts the currency code from each Tuhund invoice, verifies it against Acumatica's currency list, and flags any missing entries. The migration workflow then pauses to prompt the administrator to create the missing currency and assign a rate, ensuring the ARInvoice import completes without currency‑related errors.

Migration approach

Six steps for a successful Tuhund to Acumatica data migration

Ingest Tuhund API data across all modules

FlitStack connects to Tuhund using your API credentials and pulls data from all active modules: CRM (companies, persons, addresses), Sales (quotations, proforma invoices, commercial invoices, delivery orders), Procurement (purchase orders), Inventory (products), Services (service requests), and Expense Claims. Each module's data is staged in a migration workspace with original timestamps and owner IDs preserved. Any Tuhund custom fields discovered in the API responses are cataloged for Acumatica field mapping.
Build Acumatica schema and resolve master-data lookups

Before data moves, Acumatica's target schema must be prepared: Customer classes, Vendor classes, item classes, UOM definitions, and any Usr custom fields referenced in the mapping plan are created. FlitStack delivers a schema preparation checklist. Master-data lookups — Customers for each Tuhund company, Vendors for each Tuhund vendor, InventoryItems for each Tuhund product — are reconciled. Unmatched master records are flagged for creation before the document migration step.
Run a sample migration with field-level diff

A representative slice of records — typically 100–500 items spanning customers, quotations, invoices, delivery orders, purchase orders, service requests, and expense claims — migrates into Acumatica first. FlitStack generates a field-level diff comparing source values against destination field values, with any transformation exceptions surfaced. You verify mapping correctness for document totals, line quantities, dates, and status values before the full run commits.
Execute full migration with delta-pickup window

The full dataset migrates into Acumatica using the previously validated field‑mapping and object‑relationship rules. During the cutover period your team continues to operate in Tuhund, and a delta‑pickup window of typically 24–48 hours captures any new or changed records after the initial snapshot. FlitStack performs the load in configurable batches, logs each insert, update, and skip operation, and runs a totals‑check to confirm that document amounts and line quantities match the source data. If reconciliation reveals unexpected gaps, a one‑click rollback restores the target to its pre‑migration state.
Deliver reconciliation report and workflow-rebuild reference

After the migration and delta-pickup complete, FlitStack delivers a reconciliation report showing record counts per entity, any records that failed migration with error codes, and the delta records that were picked up. Tuhund workflow definitions, approval chains, and automation rules are exported as structured reference documents for your Acumatica administrator to rebuild in Acumatica's Screen-Based Workflow or Automation Schedules. Post-migration validation confirms that ARInvoice totals match Tuhund invoice totals within the rounding threshold.

Platform deep dives

Context on both ends of the pair

Tuhund

Source

Strengths

Broad module footprint (finance, inventory, supply chain, manufacturing, PM, CRM, HRM, analytics) on a single core.
Core platform includes meaningful functionality out of the box.
Cloud and on-premise deployment for regulated and data-residency-sensitive customers.
Multi-region vendor presence (US, Canada, UK, Australia, India).
Subscription licensing that scales users and modules over time.

Weaknesses

High total cost of ownership positions Tuhund away from SMB.
3-6 month implementation timelines.
Limited public reviewer presence.
No public developer API — integrations require vendor services.
Pricing not published, slowing early-stage evaluation.

Acumatica

Destination

Strengths

Unlimited named-user licensing eliminates per-seat cost scaling as teams grow.
Modular architecture lets companies deploy Financials first and add Distribution, Manufacturing, or CRM incrementally.
Cloud-native with automatic updates removes infrastructure patching and version management from IT responsibilities.
Flexible customization framework (UDFs, extensions) supports vertical-specific workflows without forking core code.
Multi-tenant architecture with CompanyID isolation enables safe data segregation across subsidiaries.

Weaknesses

Steep learning curve and complex initial setup create significant onboarding friction.
Report Designer is widely cited as unintuitive and difficult to use for non-developers.
Feature gaps require customizations or third-party add-ons, adding implementation cost and complexity.
Implementation timelines frequently exceed initial estimates, especially for multi-module deployments.
API rate limits and concurrent session caps are tied to license tier, creating throughput constraints for bulk data operations.

	Tuhund Source	Acumatica Destination
Strengths	Broad module footprint (finance, inventory, supply chain, manufacturing, PM, CRM, HRM, analytics) on a single core. Core platform includes meaningful functionality out of the box. Cloud and on-premise deployment for regulated and data-residency-sensitive customers. Multi-region vendor presence (US, Canada, UK, Australia, India). Subscription licensing that scales users and modules over time.	Unlimited named-user licensing eliminates per-seat cost scaling as teams grow. Modular architecture lets companies deploy Financials first and add Distribution, Manufacturing, or CRM incrementally. Cloud-native with automatic updates removes infrastructure patching and version management from IT responsibilities. Flexible customization framework (UDFs, extensions) supports vertical-specific workflows without forking core code. Multi-tenant architecture with CompanyID isolation enables safe data segregation across subsidiaries.
Weaknesses	High total cost of ownership positions Tuhund away from SMB. 3-6 month implementation timelines. Limited public reviewer presence. No public developer API — integrations require vendor services. Pricing not published, slowing early-stage evaluation.	Steep learning curve and complex initial setup create significant onboarding friction. Report Designer is widely cited as unintuitive and difficult to use for non-developers. Feature gaps require customizations or third-party add-ons, adding implementation cost and complexity. Implementation timelines frequently exceed initial estimates, especially for multi-module deployments. API rate limits and concurrent session caps are tied to license tier, creating throughput constraints for bulk data operations.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from Tuhund to Acumatica

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Tuhund

Acumatica

How Tuhund objects map to Acumatica

What specifically takes care here

Six steps for a successful Tuhund to Acumatica data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Tuhund to Acumatica migration cost

What are you migrating?

Frequently asked questions about Tuhund to Acumatica data migrations

Can't find your answer?

Related migrations to explore

Move from Tuhund.
Land in Acumatica, intact.

Migrate from Tuhund to Acumatica

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Tuhund

Acumatica

How Tuhund objects map to Acumatica

What specifically takes care here

Six steps for a successful Tuhund to Acumatica data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Tuhund to Acumatica migration cost

Frequently asked questions about Tuhund to Acumatica data migrations

Can't find your answer?

How long does a Tuhund to Acumatica migration take?

Will my Tuhund workflows, approval chains, and automation rules migrate to Acumatica?

What happens to my Tuhund commercial invoices in Acumatica?

Can I migrate Tuhund custom fields to Acumatica custom fields?

What happens to Tuhund purchase orders in Acumatica?

Does the migration affect my Tuhund account during cutover?

How does Tuhund inventory data map to Acumatica Stock Items?

What happens to my Tuhund expense claims in Acumatica?

Related migrations to explore

Move from Tuhund. Land in Acumatica, intact.

Move from Tuhund.
Land in Acumatica, intact.