Last Updated: April 2026
Your team just finished a system migration. The go-live went well. Then someone drops a spreadsheet on your desk with 400 inventory items and says, “Can you get these loaded?”
And instead of using the bulk import tool that’s been sitting in Acumatica this whole time, your team starts entering records one by one.
Here’s what drives me crazy about this: Acumatica Import Scenarios are already built into your system. No add-on. No extra license. No calling a developer. Just a straightforward tool that lets you take a spreadsheet and push data directly into virtually any screen in Acumatica. If someone on your team can type data into a screen manually, you can almost certainly import it in bulk instead.
Whether you’re loading new records for the first time, running a recurring monthly process, or working through a full data migration from a system like Dynamics GP, Import Scenarios are one of the most practical tools in Acumatica’s toolbox. Here’s how they work and how to set one up.
Import Scenarios vs. File Upload: Know the Difference
Before you build anything, it helps to understand what Import Scenarios actually are, because they get confused with another Acumatica feature – File Upload.
File Upload creates a single entry with multiple line items. Think of a complex journal entry or a payroll batch. One transaction, many lines. We covered this in detail in our post on Excel File Upload in Acumatica.
Import Scenarios create multiple separate records from a single file. A spreadsheet with 400 items becomes 400 inventory records. A file with 200 customers becomes 200 customer accounts. That’s the key distinction. Import Scenarios are your bulk processing tool, and they work across a wide range of data types: customer and vendor records, inventory items, sales and purchase orders, open invoices, pricing updates, bills of materials, and more.
One more thing worth noting: the equivalent tool in Microsoft Dynamics GP, Integration Manager, requires a separate license purchase after the initial implementation window. Acumatica Import Scenarios are included in your system at no additional cost. That’s one of the reasons we highlight it in our Acumatica vs. Dynamics GP comparison as a meaningful differentiator.
The Three Pieces Every Import Scenario Needs
Every Acumatica bulk import runs on three components. Once you understand what each one does, the setup process makes a lot more sense.
- The Data Provider This tells Acumatica where your data is coming from and what format it’s in. Excel and CSV are the most common. You point the Data Provider at your file, select the worksheet, and pick which columns are relevant. Acumatica reads those column headers and builds a schema your import can reference.
- The Import Scenario This is the mapping layer. You connect each column in your spreadsheet to the corresponding field on the Acumatica screen. Customer Name to Customer Name. Invoice Date to Invoice Date. You can also write formulas to transform data on the way in, convert non-standard values to what Acumatica expects, or assign fixed defaults to required fields that don’t exist in your source file.
- Import by Scenario This is where you run the actual import. Select your scenario, upload your file, and click Prepare. Acumatica loads the data into a staging grid so you can review every row before anything gets written to the database. Click Import, and a checkmark in the Processed column means it worked. Errors surface at the row level with a clear message so you know exactly what failed and why.
How to Set Up Your First Import Scenario
Acumatica gives you two ways to build an import scenario. Start with the Simple method.
Navigate to the Import by Scenario screen and click the plus button. You’ll be prompted to upload your Excel file, select the Acumatica screen you’re importing into from the site map, and give the import a name. Acumatica reads the file and automatically creates both the Data Provider and the Import Scenario structure, including the command lines that control how records get saved.
Go to the Mapping tab and connect your spreadsheet columns to the Acumatica fields. Map the key field first. Acumatica uses that field to determine whether it’s creating a new record or updating an existing one, and it sets up the matching logic automatically once you map it. Save, go to Import by Scenario, upload your file, and run Prepare and Import. Most people have their first import working in under an hour.
A few things worth knowing before you start:
- Acumatica comes with about 40 pre-built import scenarios. Check whether a template already exists before building one from scratch. Copying an existing scenario and adjusting the mapping is significantly faster.
- Parallel processing is available for large files. Acumatica breaks the import into batches and processes them simultaneously. For hundreds or thousands of rows, you’ll notice the difference. See it in action in our overview of Acumatica’s faster data import features.
- Complex imports need the Manual method. Parent-child screens like an invoice header with multiple detail lines, or screens that trigger pop-up dialog boxes, require the manual scenario approach for full control. The Acumatica community forum for import scenarios is a solid resource when you hit those situations.
Don’t Overlook Scheduling and Automation
Most people don’t discover this until they’ve been using Import Scenarios for a while: you can schedule them to run automatically.
If your team receives a vendor pricing file every Monday, or pulls transaction data from a separate system nightly, you can configure Acumatica to pick up that file and run the import without anyone manually kicking it off. This is where Import Scenarios start crossing into genuine integration territory without requiring custom development or third-party middleware.
Three Mistakes to Avoid
Not mapping the key field first. Acumatica uses it to determine whether to create or update a record. Skip it and you’ll end up with duplicates or failures.
Skipping a small test batch. Always run five to ten rows before committing a full file to production. Errors on row 312 of 400 are a lot more painful than errors on row 4 of 10.
Ignoring the substitution list. If your source data uses values that don’t match what Acumatica expects, the substitution list handles that translation automatically on every import. Use it instead of cleaning your spreadsheet manually each time.
Ready to Cut Manual Entry Out of Your Process?
If your team is still entering data row by row when a spreadsheet full of records is sitting right there, that’s time you’re not getting back. CAL Business Solutions has over 40 years of experience implementing ERP systems for small and mid-sized businesses. We can help you set up your first import scenario, build a library of reusable templates, or manage a full data migration from your prior system.
Contact CAL Business Solutions at 860-485-0910 x4 or sales@calszone.com. Or reach out through our website and we’ll get back to you.
