ERP migration
Field-level mapping, validation, and rollback between Wiise and Acumatica. We move data and schema; workflows are rebuilt natively in Acumatica.
Wiise
Source
Acumatica
Destination
Compatibility
13 of 13
objects map 1:1 between Wiise and Acumatica.
Complexity
BStandard
Timeline
48–96 hours
Overview
Wiise is built on Microsoft Dynamics 365 Business Central and serves Australian and New Zealand SMBs with accounting, inventory, warehousing, CRM, and project costing. As businesses outgrow the Business Central tier, they encounter Wiise's per-user pricing ceiling, limited API rate flexibility, and the need to build saved searches manually rather than configure native reports. Acumatica Cloud ERP offers a consumption-based pricing model with unlimited users, branch-based inventory across multiple warehouse locations, multi-entity consolidations, and a robust Generic Inquiry (saved search) framework that replaces Business Central's RoleTailored client approach. FlitStack AI extracts Wiise data via the Business Central API — customers, vendors, items, sales orders, purchase invoices, jobs, GL entries, and custom fields — and loads them into Acumatica using Acumatica's Import by Scenario framework. Workflows, approval routing, and notification templates in Wiise do not migrate; these must be rebuilt in Acumatica's Business Events and Screen-Based Workflows. We preserve custom fields as Acumatica user-defined fields and surface the full field mapping before the migration run so your Acumatica admin can pre-create any missing schema. A delta-pickup window captures in-flight documents created during cutover so Acumatica reflects Wiise's final state at go-live.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Wiise 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.
Wiise
Customer
Acumatica
Customer
1:1Wiise customer records map directly to Acumatica Customers. The primary address maps to Acumatica's main address, and secondary addresses map to Customer Locations. Wiise's Customer Posting Group is preserved as a reference attribute on the Acumatica customer card for GL posting group assignment.
Wiise
Vendor
Acumatica
Vendor
1:1Wiise vendor records map one-to-one to Acumatica Vendors, preserving all attributes during migration. Primary and payment addresses map to Acumatica's main vendor address and payment address fields respectively. The Vendor Posting Group defined in Wiise transfers to Acumatica's Vendor Class, ensuring payables post to the correct general ledger accounts and that your existing AP workflow settings remain consistent after go-live.
Wiise
Item
Acumatica
Inventory Item
1:1Wiise inventory items map to Acumatica Stock Items with all item attributes, pricing, and costing information preserved. Item tracking settings including lot/serial assignment rules and the stockkeeping unit structure map to Acumatica's lot/serial attributes per warehouse location. Non-stock items map to Acumatica Non-Stock Items using the same general product posting group, ensuring correct revenue and expense recognition when these items are sold or consumed on projects.
Wiise
Sales Order
Acumatica
Sales Order
1:1Wiise sales orders migrate as Acumatica Sales Orders with all header details, line items, quantities, discounts, tax amounts, and payment terms fully preserved. The original Wiise order number is stored in Acumatica's External Reference field, maintaining full traceability to source documents for your finance team. Ship-to addresses from Wiise map directly to Customer Locations in Acumatica, ensuring delivery instructions and address-specific pricing are retained for each order.
Wiise
Sales Invoice
Acumatica
Sales Invoice
1:1Wiise posted sales invoices migrate to Acumatica Sales Invoices with all header and line details intact. Original invoice dates, due dates, payment terms, and currency codes map correctly to ensure accurate aging reports and cash application after go-live. Partial shipments that generated multiple invoices in Wiise create corresponding multiple invoices in Acumatica, preserving the complete billing history and ensuring customer account balances remain accurate throughout the transition.
Wiise
Purchase Order
Acumatica
Purchase Order
1:1Wiise purchase orders map directly to Acumatica Purchase Orders with all header information, line items, quantities, and pricing preserved. Buy-from vendor addresses are resolved to Acumatica Vendor Locations, while ship-to warehouse locations are matched to corresponding Acumatica Warehouse records. Expected receipt dates and delivery instructions transfer as-is, ensuring your purchasing team can continue tracking incoming shipments without manual re-entry after migration.
Wiise
Purchase Invoice
Acumatica
Purchase Receipt
1:1Wiise posted purchase invoices are more accurately represented as Acumatica Bills since they have already been received and recorded. If the receipt and invoice are separate in Wiise, the purchase receipt migrates first, followed by the bill linked to that receipt.
Wiise
Job
Acumatica
Project
1:1Wiise Job records map to Acumatica Projects with all job attributes and settings preserved. Job tasks and sub-tasks become Acumatica project tasks nested under the parent project, maintaining the full work breakdown hierarchy. Work type codes from Wiise map to Acumatica Labour Types, and all resource hours transfer as Project Transactions with the original work date and employee assignments intact for accurate project costing.
Wiise
GL Entry
Acumatica
GL Entry (Journal)
1:1Wiise general ledger entries migrate to Acumatica GL Journal lines with original posting dates, document numbers, account assignments, and amounts fully preserved. Dimension values from Wiise Business Central (Shortcut Dimension 1 and 2, typically representing department and cost centre) map directly to Acumatica Subaccounts using the configured Subaccount segment mappings. This ensures that your financial reporting structure and cost allocation logic remain intact throughout the migration.
Wiise
Contact
Acumatica
Contact
1:1Wiise Contact records map to Acumatica Contacts with all contact information preserved during migration. The link to the parent Customer record is preserved via the Customer ID lookup field in Acumatica, maintaining the relationship between contacts and their associated accounts. Job title, phone numbers, email addresses, and physical address fields transfer directly with their original values intact, ensuring your sales and service teams can continue communicating with customers after go-live.
Wiise
Fixed Asset
Acumatica
Fixed Asset
1:1Wiise fixed asset records map to Acumatica Fixed Assets with depreciation book values, acquisition dates, useful life information, and asset class assignments fully preserved. The asset cost, accumulated depreciation, and net book value transfer to Acumatica's primary depreciation book. However, depreciation books and schedules require review after migration since Acumatica supports multiple depreciation conventions per asset for tax, statutory, and financial reporting purposes.
Wiise
Custom Fields (Text, Checkbox, Integer, Decimal, Lookup, Date)
Acumatica
User-Defined Fields (UsrCustomText01–04, UsrCustomCheckbox01–02, etc.)
1:1Wiise custom fields per page type (Customer, Vendor, Item, Sales Header, Purchase Header, Job) map to Acumatica user-defined fields on the equivalent screens. Each custom field requires pre-creation in Acumatica through the Customization Project editor. Lookup fields preserve their display value as text in Acumatica's user-defined text fields unless a corresponding value list is built.
Wiise
Company Information
Acumatica
Organization
1:1Wiise company-level settings including company name, primary address, tax registration numbers, and fiscal year start date map to Acumatica's Organization screen during migration. Multiple Wiise companies within a single subscription require a topology decision in Acumatica — they can map to separate tenants for full isolation, or to separate branches within a single tenant when consolidated reporting is required, depending on your specific consolidation and financial reporting needs.
| Wiise | Acumatica | Compatibility | |
|---|---|---|---|
| Customer | Customer1:1 | Fully supported | |
| Vendor | Vendor1:1 | Fully supported | |
| Item | Inventory Item1:1 | Fully supported | |
| Sales Order | Sales Order1:1 | Fully supported | |
| Sales Invoice | Sales Invoice1:1 | Fully supported | |
| Purchase Order | Purchase Order1:1 | Fully supported | |
| Purchase Invoice | Purchase Receipt1:1 | Fully supported | |
| Job | Project1:1 | Fully supported | |
| GL Entry | GL Entry (Journal)1:1 | Fully supported | |
| Contact | Contact1:1 | Fully supported | |
| Fixed Asset | Fixed Asset1:1 | Fully supported | |
| Custom Fields (Text, Checkbox, Integer, Decimal, Lookup, Date) | User-Defined Fields (UsrCustomText01–04, UsrCustomCheckbox01–02, etc.)1:1 | Fully supported | |
| Company Information | Organization1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Wiise gotchas
No public API for document attachments
Custom field decimal precision loss
Multi-company scoping must be declared upfront
Opening balance reconciliation requires manual sign-off
Payroll is a priced add-on with separate schema
Acumatica gotchas
API user licenses cap concurrent sessions and request throughput
Multi-tenant filtering requires CompanyID awareness
Custom fields require separate discovery before field mapping
Notes and attachments use a separate linked table structure
Implementation timelines frequently run 3–9 months end-to-end
Pair-specific challenges
Migration approach
Map Wiise chart of accounts to Acumatica account structure
Before any record migration, FlitStack AI maps Wiise's Business Central chart of accounts to Acumatica's account structure. This includes reconciling the account number format, mapping Wiise Business Central dimensions to Acumatica Subaccounts (Branch and Department), and identifying any accounts that require Acumatica to be extended with new account segments. The output is a row-by-row account mapping spreadsheet that your Acumatica admin reviews and approves before any GL data moves.
Pre-create Acumatica warehouses and branches for Wiise location codes
Wiise warehouse and location codes must have matching Acumatica Warehouse records before inventory can be distributed. FlitStack AI exports the complete list of Wiise Location Codes and their on-hand quantities per item, then delivers a warehouse setup plan specifying the Warehouse ID, name, address, and inventory posting group for each location. Your Acumatica admin creates these in advance so the inventory migration can write quantities directly to the correct warehouse.
Create Acumatica user-defined fields for Wiise custom fields
Wiise custom fields on Customers, Vendors, Items, Sales Orders, Purchase Orders, and Jobs require corresponding Acumatica user-defined fields. FlitStack AI lists every Wiise custom field by page type with its data type and character limit, giving your Acumatica admin a complete checklist for the Customization Project editor. After fields are created, they must be published to the Acumatica endpoint before field mapping validation runs.
Run a sample migration with field-level validation
FlitStack AI runs a representative slice of Wiise records — typically 200–500 across customers, vendors, items, and a sample sales order and job — into the Acumatica sandbox. The sample includes records with custom fields populated so your team can verify that the user-defined field mapping resolves correctly. We generate a field-level diff showing every source field, its mapped destination value, and any validation errors that Acumatica returned. Your team signs off on the sample before the full migration run is scheduled.
Execute full migration with delta-pickup window
The full migration extracts all Wiise records — customers, vendors, items, sales orders, posted invoices, purchase orders, jobs, job tasks, job ledger entries, and GL entries — and loads them into the production Acumatica environment using Import by Scenario. A delta-pickup window of 24–48 hours after the initial load captures any records created or modified in Wiise during the cutover period. FlitStack AI generates an audit log of every record created and a reconciliation summary comparing Wiise record counts against Acumatica record counts per object type. One-click rollback is available if the reconciliation summary reveals a mismatch that exceeds the agreed tolerance threshold.
Platform deep dives
Wiise
Source
Strengths
Weaknesses
Acumatica
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Wiise and Acumatica.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Wiise: Not publicly documented — governed by Business Central cloud throttling defaults.
Data volume sensitivity
Wiise exposes a bulk API — large-volume migrations stream efficiently.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Wiise to Acumatica migration scoping. Not seeing yours? Book a call.
Walk through your Wiise to Acumatica migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Wiise
Other ways to arrive at Acumatica
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.