---
title: "NetSuite to Acumatica Migration: Field Mapping & Rollback"
description: "Migrate NetSuite to Acumatica with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/erp/netsuite/to/acumatica"
---

# NetSuite to Acumatica migration

Moving from NetSuite to Acumatica is a common mid-market migration, driven by Acumatica's resource-based licensing model and flexible deployment options. FlitStack AI maps every NetSuite entity — customers, vendors, items, accounts, and transactional records — into Acumatica's relational schema, preserving original create dates and audit trails. Acumatica's full relational database export capability means your data exits NetSuite completely, with no black-box constraints on what can move.

Short answer

FlitStack AI migrates customers, vendors, employees, stock items and non-stock items from NetSuite to Acumatica, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 50,000 records.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See the field mapping →](https://flitstack.ai/migrations/erp/netsuite/to/acumatica#field-mapping)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source NetSuite ![](https://flitstack.ai/platforms-trim/netsuite.webp)

Destination Acumatica ![](https://flitstack.ai/platforms-trim/acumatica.webp)

Customer Vendor Employee Stock Item Non-Stock Item

Mapped field by field · sample run · one-click rollback

## What moves from NetSuite to Acumatica?

NetSuite and Acumatica share a similar ERP footprint — both handle financials, inventory, sales orders, and purchasing — but their data models diverge in how they represent entities and transactions.

Read the full summary

NetSuite uses a unified record structure with custom fields via SuiteScript and saved searches, while Acumatica uses an industry-standard relational schema with customizable screens and generic inquiries. The migration carries NetSuite's customers, vendors, chart of accounts, inventory items, projects, and transactional history into Acumatica's equivalent entities. Custom records (NetSuite Custom Records) map to Acumatica custom tables, and NetSuite custom fields migrate as user-defined fields on their parent entities. Saved searches require manual reconstruction as Acumatica Generic Inquiries, and NetSuite workflows or SuiteFlow automations do not migrate. FlitStack AI sequences the migration to respect Acumatica's import-by-scenario tool, which requires understanding field-level structure before upload. We deliver a schema preparation plan so your Acumatica instance has the right screen customizations and user-defined fields in place before data lands.

direct

### Customer → Customer

NetSuite Customer records map directly to Acumatica Customers.

How it maps

NetSuite's subsidiary and territory assignments translate to Acumatica Customer Class and Branch assignments. Primary contact details (name, email, phone) transfer directly; multi-address records are preserved as separate Customer Locations in Acumatica. Addressee and print-on-check information also transfer, and customer-specific pricing maps to Acumatica's customer price classes.

direct

### Vendor → Vendor

NetSuite Vendor records map to Acumatica Vendors.

How it maps

Tax ID fields and 1099 flags translate to Acumatica tax settings on the vendor record. Multi-address vendor records become separate Vendor Locations in Acumatica. 1099 flags map to Acumatica tax settings on the vendor record. Payment hold status and default payment account assignments also transfer to maintain vendor payment preferences in the target system.

direct

### Employee → Employee

NetSuite Employee records map to Acumatica Employees.

How it maps

E-mail address is the matching key for owner resolution. Inactive employees in NetSuite can be mapped as inactive in Acumatica or excluded based on your migration scope. Department and location assignments transfer as Employee Department and Branch references, preserving the organizational reporting structure across the migration.

direct

### Item (Inventory Part) → Stock Item

NetSuite Inventory Part items map to Acumatica Stock Items.

How it maps

The item number, description, base price, and units of measure transfer directly. NetSuite's units types map to Acumatica's Unit of Measure setup on the Stock Item. Item class assignments translate to Acumatica Item Class, and any custom fields prefixed custitem become user-defined fields on the Stock Item DAC.

direct

### Item (Non-Inventory Part) → Non-Stock Item

NetSuite Non-Inventory Part items map to Acumatica Non-Stock Items.

How it maps

These are used for services or materials not tracked in inventory. The item number and description transfer; pricing fields map where applicable. Non-stock items typically represent service items, expense items, or job materials that are expensed or invoiced without inventory tracking requirements.

transformed

### Item (Kit/Bundled) → Kit / Stock Item with bill of materials

NetSuite Kit items with component lists map to Acumatica Stock Items with an attached bill of materials (BOM).

How it maps

The kit header becomes the parent stock item, and each component is created as a BOM line. This requires BOM setup in Acumatica before the migration run.

******What moves 14 objects

NetSuite Acumatica

- Customer Customer 1:1
- Vendor Vendor 1:1
- Employee Employee 1:1
- Item Stock Item 1:1
- Item Non-Stock Item 1:1
- Item Kit transformed

\+ 8 more in the mapping below

## How NetSuite and Acumatica differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension                       | NetSuite                                                                                                                                                        | Acumatica                                                                                                                                             |
| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| Customization approach          | NetSuite uses SuiteScript (JavaScript-based) and SuiteBuilder for custom fields and forms — access requires SuiteCloud licenses and developer-tier permissions. | Acumatica uses C# and .NET for customizations, with a screen-customization editor that business analysts can use without developer licenses.          |
| Reporting tools                 | NetSuite provides Saved Searches that function as both search queries and live reports — native BI is available at higher tiers.                                | Acumatica ships pre-configured BI tools and allows full relational database exports for external reporting at any tier.                               |
| Custom records                  | NetSuite Custom Records use a custom record type system with custom fields, accessible via SuiteScript and web services.                                        | Acumatica custom tables (DACs) are created via the Customization Project editor and accessed via screen-based or API-based entry.                     |
| List and search views           | NetSuite provides standard list views and Saved Searches out of the box for every record type.                                                                  | Acumatica requires Generic Inquiries (saved searches) to be built manually for every list view that differs from the default.                         |
| Notification and workflow model | NetSuite SuiteFlow provides a visual workflow engine for approvals, notifications, and record actions.                                                          | Acumatica uses Business Events, email templates, and notification screens — automation logic requires rebuilding as Generic Inquiries or custom code. |
| Deployment model                | NetSuite is cloud-only with mandatory Oracle-controlled upgrade schedules.                                                                                      | Acumatica offers cloud, on-premises, or hybrid deployment with self-managed upgrade timelines.                                                        |

## NetSuite to Acumatica field mapping

The 30 most-used fields of 41 mapped for this pair. Custom fields are added from your own schema during scoping. [Download the full mapping (CSV) ↓](https://flitstack.ai/migrations/erp/netsuite/to/acumatica.csv) or open it in the [field mapping template](https://flitstack.ai/tools/field-mapping-template).

******Field mapping 5 shown

NetSuite Acumatica

1. `companyname` Customer `CustomerName` Customer
2. `email` Customer `Email` Customer
3. `phone` Customer `Phone1` Customer
4. `fax` Customer `Fax` Customer
5. `url` Customer `WebSite` Customer

| NetSuite field                        | Acumatica field                | Mapping                 | Note                                                                                                                                    |
| ------------------------------------- | ------------------------------ | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| `Customer.companyname`                | `Customer.CustomerName`        | direct                  |                                                                                                                                         |
| `Customer.email`                      | `Customer.Email`               | direct                  |                                                                                                                                         |
| `Customer.phone`                      | `Customer.Phone1`              | direct                  |                                                                                                                                         |
| `Customer.fax`                        | `Customer.Fax`                 | direct                  |                                                                                                                                         |
| `Customer.url`                        | `Customer.WebSite`             | direct                  |                                                                                                                                         |
| `Customer.terms`                      | `Customer.CreditTerm`          | value\_mapping          | NetSuite payment term names (Net 30, Net 60, etc.) map to Acumatica Credit Terms by exact name match or nearest equivalent.             |
| `Customer.creditlimit`                | `Customer.CreditLimit`         | direct                  |                                                                                                                                         |
| `Customer.taxitem`                    | `Customer.TaxZoneID`           | value\_mapping          | NetSuite tax item assignments map to Acumatica Tax Zone IDs. Tax zone configuration must be set up in Acumatica before customer import. |
| `Customer.custentity_ns_custom_field` | `Customer.UsrNSOriginID`       | custom\_field\_required | NetSuite custom entity fields prefixed custentity map to Acumatica user-defined fields on the Customer DAC.                             |
| `Customer.datecreated`                | `Customer.CreatedDateTime`     | custom\_field\_required | NetSuite Created Date is preserved as a custom datetime field because Acumatica sets CreatedDateTime at migration time.                 |
| `Customer.internalid`                 | `Customer.UsrNSInternalID`     | custom\_field\_required | NetSuite internal ID stored for traceability and delta-run de-duplication during subsequent migration passes.                           |
| `Vendor.companyname`                  | `Vendor.VendorName`            | direct                  |                                                                                                                                         |
| `Vendor.email`                        | `Vendor.Email`                 | direct                  |                                                                                                                                         |
| `Vendor.phone`                        | `Vendor.Phone1`                | direct                  |                                                                                                                                         |
| `Vendor.taxid`                        | `Vendor.TaxID`                 | direct                  |                                                                                                                                         |
| `Vendor.terms`                        | `Vendor.CreditTerm`            | value\_mapping          | NetSuite vendor payment terms map to Acumatica Credit Terms by exact name match.                                                        |
| `Employee.firstname`                  | `Employee.FirstName`           | direct                  |                                                                                                                                         |
| `Employee.lastname`                   | `Employee.LastName`            | direct                  |                                                                                                                                         |
| `Employee.email`                      | `Employee.Email`               | direct                  |                                                                                                                                         |
| `Employee.department`                 | `Employee.Department`          | value\_mapping          | NetSuite department internal IDs map to Acumatica Department IDs. Both must exist in Acumatica before employee import.                  |
| `Stock Item.itemid`                   | `Stock Item.InventoryCD`       | direct                  |                                                                                                                                         |
| `Stock Item.displayname`              | `Stock Item.Descr`             | direct                  |                                                                                                                                         |
| `Stock Item.baseprice`                | `Stock Item.DefaultPrice`      | direct                  |                                                                                                                                         |
| `Stock Item.class`                    | `Stock Item.ItemClass`         | value\_mapping          | NetSuite class assignments map to Acumatica Item Class IDs. Both must be configured in Acumatica before item import.                    |
| `Stock Item.custitem_ns_custom`       | `Stock Item.UsrNSOriginItemID` | custom\_field\_required | NetSuite item custom fields (prefixed custitem) map to Acumatica UDFs on the Stock Item DAC.                                            |
| `Account.acctnumber`                  | `Account.AccountCD`            | direct                  |                                                                                                                                         |
| `Account.acctname`                    | `Account.Description`          | direct                  |                                                                                                                                         |
| `Account.accttype`                    | `Account.Type`                 | value\_mapping          | NetSuite account types (Bank, Income, Expense, Asset, Liability, etc.) map to Acumatica account types by type group.                    |
| `Sales Order.tranid`                  | `Sales Order.OrderNbr`         | direct                  |                                                                                                                                         |
| `Sales Order.trandate`                | `Sales Order.OrderDate`        | direct                  |                                                                                                                                         |

## What to watch for in a NetSuite to Acumatica migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### NetSuite Saved Searches have no Acumatica equivalent — query logic must be rebuilt

NetSuite Saved Searches are a flexible reporting and query tool that functions as both a data extraction mechanism and a live report builder.

How we handle it

Acumatica Generic Inquiries serve a similar role but require manual reconstruction in Acumatica's GI editor, including re-establishing joins, filters, and display column configurations. This is a known rebuild item for every NetSuite-to-Acumatica migration. FlitStack AI exports the Saved Search definition as a reference document that your Acumatica administrator or consultant can use to rebuild each GI. We surface all Saved Searches in the migration plan and assign each one a rebuild status (straightforward mapping, complex join requiring consultant review, or abandoned). Failure to rebuild Saved Searches before go-live means you lose a critical reporting tool that your team relies on daily.

high

### NetSuite subsidiary hierarchies require explicit entity resolution in Acumatica

NetSuite supports multi-subsidiary configurations where a single customer or vendor can be shared across subsidiaries.

How we handle it

Acumatica uses Branch and Organization entities to represent multi-entity structures, and customers belong to specific organizations. NetSuite's intercompany subsidiary accounting does not have a direct Acumatica equivalent — intercompany transactions must be reconfigured as separate vendor and customer records within Acumatica's organization structure. We analyze your NetSuite subsidiary configuration during the assessment phase and deliver an entity mapping plan that resolves subsidiary ownership to Acumatica organizations before any customer or vendor data is imported.

high

### NetSuite Custom Records require Acumatica custom table creation before migration

NetSuite Custom Record Types are created via Setup > Custom Record Types and can have custom fields, list views, and sublists.

How we handle it

Acumatica has no built-in Custom Record Type equivalent — you create custom tables via the Customization Project editor (DACs), and each custom field must be added as a user-defined field. We map every NetSuite Custom Record Type to an Acumatica custom table schema, but the Acumatica custom table must exist (be created) before data can load. This adds a schema preparation step that takes 1–3 days depending on the number of custom record types and their field complexity.

medium

### NetSuite SuiteFlow workflows and approval workflows do not migrate

NetSuite SuiteFlow provides a visual workflow engine for approval routing, automated data entry, and notification sequences tied to record events.

How we handle it

Acumatica's automation model uses Business Events, Generic Inquiries with redirects, and email templates — these are fundamentally different paradigms. Approval workflows built in SuiteFlow must be redesigned in Acumatica's Business Events framework or rebuilt using Acumatica's screen automation capabilities. We export your SuiteFlow definitions as a reference and include them in the rebuild package, but the migration itself carries data only.

medium

### NetSuite's class and department structures map to multiple Acumatica entities

NetSuite uses Class and Department as classification dimensions on transactions and records, with Class often functioning as a cost categorization tool.

How we handle it

Acumatica separates these concerns across Item Class, Customer Class, Department, Cost Code, and Branch entities. A single NetSuite Class assignment on an invoice line may need to split into an Acumatica Cost Code (on the line), a Department (on the header), and an Item Class (on the inventory item). We analyze your Class usage patterns and deliver a classification mapping plan that assigns each NetSuite Class value to the appropriate Acumatica classification entity before transaction import.

## How the migration runs

1. ### Assess NetSuite schema and Acumatica target configuration

   We connect to your NetSuite account using scoped read access and inventory every record type, custom field, custom record type, saved search, and workflow definition.

   What this step covers

   Simultaneously, we review your target Acumatica configuration (organizations, chart of accounts, tax zones, item classes, and custom tables). We deliver a Schema Preparation Plan that specifies which Acumatica entities and user-defined fields need to be created before data import begins. This step typically takes 2–4 days and produces the blueprint your Acumatica administrator uses to stand up the target schema.

2. ### Build data extraction jobs for master data before transactions

   We build NetSuite data extraction jobs using Saved Searches for customers, vendors, employees, chart of accounts, and items.

   What this step covers

   Each extraction runs against NetSuite's API with pagination and rate-limit handling to ensure complete record retrieval. For Acumatica, we load master data (accounts, customers, vendors, items) first because transactional records reference these as foreign keys. If your NetSuite instance uses multiple subsidiaries, we extract subsidiary-level account hierarchies and map them to Acumatica organizations. This step produces an ordered load sequence that respects Acumatica's import dependency chain.

3. ### Run sample migration with field-level diff

   A representative slice of records — typically 100–500 across customers, vendors, items, and 50–100 transaction lines — migrates first.

   What this step covers

   We generate a field-level diff comparing the NetSuite source values against what landed in Acumatica, with color-coded mismatches for review. This validates mapping logic for custom fields, value mappings for pick-lists, and date/timestamp preservation before committing the full dataset. Your team reviews the sample diff and approves field mapping logic before the full migration run is scheduled.

4. ### Execute full migration with dependency-ordered load sequence

   The full migration runs in dependency order: chart of accounts first, then customers and vendors, then items, then transactional records (sales orders, invoices, bills, payments, journal entries).

   What this step covers

   NetSuite custom records load after their parent standard records. We batch records to respect Acumatica's import-by-scenario tool limits and apply delta-pickup at the end to capture any records modified in NetSuite during the cutover window. Audit logging tracks every record written, with rollback capability if reconciliation identifies unexpected data gaps.

5. ### Delta-pickup window and go-live reconciliation

   A 24–48 hour delta-pickup window captures any NetSuite records created or modified after the main migration run snapshot was taken.

   What this step covers

   During this window, your team continues working in NetSuite. After the delta is applied to Acumatica, we run a reconciliation report comparing record counts, transaction totals, and customer balances between systems. One-click rollback is available if reconciliation fails a pre-defined threshold. Once your team confirms the Acumatica data matches expectations, you go live and NetSuite access can be decommissioned.

![](https://flitstack.ai/platforms/netsuite.svg) NetSuite ![](https://flitstack.ai/platforms/acumatica.svg) Acumatica

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Acumatica Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**48–72 hours for under 50,000 records** Typical, smaller accounts

**5–7 days for over 500,000 records or complex custom-record setups** Large or heavily customised accounts

A quote scales with the number of NetSuite records, the count of custom fields and custom record types, and the degree of data-model divergence that requires transformation logic. NetSuite setups with heavy custom-record usage, multiple subsidiary structures, or SuiteScript-driven custom fields fall in the upper range because each custom record type needs its own Acumatica custom table mapping and because subsidiary hierarchies require explicit parent-company resolution before customer and vendor records can land cleanly. Standard chart-of-accounts and transaction migration without extensive custom objects typically lands in the lower-to-middle range. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for NetSuite to Acumatica →](https://flitstack.ai/contact)

## Why teams move from NetSuite to Acumatica

- NetSuite's per-user pricing model creates unpredictable cost growth as organizations add seasonal staff, contractors, or warehouse teams — each new named user triggers license renegotiation. Acumatica's resource-based licensing charges based on compute and storage consumption rather than headcount, allowing unlimited user access without proportional cost increases. Reddit threads on r/Netsuite confirm this as a primary driver for teams evaluating the switch.
- NetSuite's SuiteScript and SuiteFlow-based customization model requires developer-tier access and niche JavaScript expertise. Acumatica uses C# and .NET, technologies more commonly found in internal development teams. G2 review themes consistently note that NetSuite's customization overhead increases long-term maintenance costs when compared to industry-standard tooling.
- NetSuite's multi-tenant cloud-only architecture enforces Oracle's upgrade schedule, which can conflict with compliance requirements or seasonal business cycles. Acumatica's self-managed upgrade path lets organizations defer upgrades until after peak seasons or audit periods. First-hand customer feedback from migrating teams cites this as a key operational risk reduction.
- NetSuite does not provide a full relational database export, which creates migration constraints when deep integrations or compliance audits require complete data portability. Acumatica grants full relational database access at every tier, making data extraction complete and auditable without proprietary tooling.
- NetSuite's support model requires VAR-mediated ticket submission, where even 15-minute triage conversations are billable events. Acumatica offers direct support channels and community resources that reduce the cost of issue resolution. This support cost asymmetry compounds over multi-year deployments, particularly for organizations with complex configurations.

Questions, answered

## NetSuite to Acumatica migration questions

How long does a NetSuite to Acumatica migration take?

Most NetSuite-to-Acumatica migrations complete within 48–72 hours of clock time for datasets under 50,000 records across customers, vendors, items, and accounts. Larger deployments with 500,000+ records or extensive custom record types extend to 5–7 days. The longest planning step is the schema preparation phase where Acumatica custom tables and user-defined fields are created to match NetSuite's custom record structure. Saved Search and Generic Inquiry rebuilding happens in parallel and is not included in the migration timeline.

Will my NetSuite SuiteFlow workflows migrate to Acumatica Business Events?

No. FlitStack AI migrates data and schema only — SuiteFlow approval workflows, automated record actions, and notification sequences do not transfer to Acumatica's Business Events model. These use fundamentally different paradigms and must be redesigned for Acumatica. We export your SuiteFlow definitions as a reference rebuild package so your Acumatica administrator or consultant can reconstruct the logic in Acumatica's automation framework.

What does NetSuite Custom Record become in Acumatica?

NetSuite Custom Record Types map to Acumatica custom tables (DACs) created via the Customization Project editor. Each custom field on the NetSuite record becomes a user-defined field on the corresponding Acumatica custom table. Parent-child relationships between custom records may need junction tables in Acumatica. The custom table must be created in Acumatica before the migration run loads the data — we include this in the schema preparation plan so your Acumatica instance is ready before records land.

Can I migrate NetSuite saved searches to Acumatica Generic Inquiries?

No — NetSuite Saved Searches are definition exports only, and their query logic cannot execute in Acumatica. We export every Saved Search definition as a structured reference document that your Acumatica administrator can use to rebuild the equivalent Generic Inquiry. Saved Searches that involve complex joins or calculated fields may require Acumatica consultant assistance to reproduce accurately. This is always a rebuild item, not a data migration item.

Does the migration affect my NetSuite account during the cutover?

No. FlitStack AI uses scoped read access on NetSuite — your team keeps working in NetSuite throughout the migration. A delta-pickup window (typically 24–48 hours after the main run) captures any records created or modified during the cutover so Acumatica reflects NetSuite's final state at go-live. No write operations are performed on NetSuite during the migration, so there is no risk of data corruption or locked records.

What happens to NetSuite's subsidiary structure in Acumatica?

NetSuite subsidiary hierarchies with intercompany accounting require redesign in Acumatica, because Acumatica uses Organization and Branch entities rather than NetSuite's subsidiary model. Shared customers or vendors across subsidiaries must be created separately within each Acumatica Organization. We analyze your NetSuite subsidiary configuration during assessment and deliver an entity mapping plan that resolves each NetSuite subsidiary to its corresponding Acumatica organization before customer and vendor import begins.

How does NetSuite class and department classification map to Acumatica?

NetSuite Class assignments on transactions do not map to a single Acumatica entity — they split across Cost Code (on transaction lines), Department (on transaction headers), and Item Class (on inventory items). We analyze your Class usage patterns during the assessment phase and produce a classification mapping plan that assigns each NetSuite Class value to the appropriate Acumatica classification entity before transactional data is imported.

Can NetSuite project billing data migrate to Acumatica Projects?

Yes. NetSuite SuiteProjects Pro project records, task hierarchies, time entries, and labor allocations map to Acumatica Projects. Project headers transfer as Acumatica Projects with the project ID, name, status, and customer association preserved. Task-level data becomes Acumatica Project Tasks, and time entries migrate as labor allocation lines. However, project-specific approval workflows built in NetSuite SuiteProjects must be rebuilt in Acumatica's project automation framework.

## Related migrations

[![](https://flitstack.ai/platforms-trim/acumatica.webp) Migrate to **Acumatica** Every source we move into Acumatica, native options and the checklist. Guide, checklist & sources ](https://flitstack.ai/migrations/erp/acumatica) [**NetSuite to Business Central** Mapping · history · rollback](https://flitstack.ai/migrations/erp/netsuite/to/microsoft-dynamics-365-business-central) [**NetSuite to Odoo ERP** Mapping · history · rollback](https://flitstack.ai/migrations/erp/netsuite/to/odoo-erp) [**NetSuite to Epicor Prophet 21** Mapping · history · rollback](https://flitstack.ai/migrations/erp/netsuite/to/epicor-prophet-21)

## Sources: official documentation

1. [Acumatica Web Services and Integration Best Practices](https://www.acumatica.com/blog/acumatica-web-services-rest-api-odata-and-integration-best-practices)
2. [I330 Data Manipulation with Web Services — Acumatica Open University](https://openuni.acumatica.com/wp-content/uploads/2017/08/I330_WebServicesDataManipulation_2022R1-1.pdf)
3. [No-Code Customizations Guide — Acumatica Blog](https://www.acumatica.com/blog/no-code-customizations-a-comprehensive-guide-to-the-basics/)
4. [To Create a CSV Data Provider — Acumatica Help](https://help-2018r1.acumatica.com/\(W\(1\)\)/Wiki/ShowWiki.aspx?wikiname=HelpRoot_User\&PageID=7eb06ccf-2a09-4635-960e-7395ad43a4fc)
5. [T210 Customized Forms and Master-Detail Relationship — Acumatica Open University](https://openuni.acumatica.com/wp-content/uploads/2017/08/T210_MasterDetailAndCustomizedForms_2019R2-June.pdf)
6. [F110 Data Migration 2025 R2 — Acumatica Open University](https://openuni.acumatica.com/courses/fin/f110-data-migration/)
7. [Acumatica Licensing Guide Supplement](https://www.acumatica.com/media/2024/02/Acumatica-Licensing-Guide-Supplement.pdf)

Get a quote

## Moving from NetSuite to Acumatica?

Tell us roughly how many records and objects you have. We scope the mapping and the Acumatica setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
