To import data into Business Central you have three practical routes: Edit in Excel for small, page-shaped corrections, Configuration Packages for structured setup and master data, and the free Import Export PowerTool for bulk loads and table-level changes that the first two cannot reach. Microsoft Dynamics 365 Business Central ships the first two; Insight Works publishes the third. Which one you use to move data into Business Central depends on volume, on whether validation must run on every field, and on how much damage a mistake could do. This article compares the three and answers two common questions: what to do when an import fails partway, and how to move data between companies.
What are the three ways to import data into Business Central?
The three methods are Edit in Excel, Configuration Packages (often still called RapidStart), and the Import Export PowerTool. Each solves a different problem.
| Edit in Excel | Configuration Packages | Import Export PowerTool | |
|---|---|---|---|
| Built for | Editing the records on one list page in bulk | Setting up a company from a reusable, structured package of tables | Bulk import, export, update and delete across effectively any table |
| Typical volume | Dozens to a few thousand rows on one page | Master data and setup tables for a new company | Large loads, including historical entries |
| Validation | Changes publish back through the page’s business logic | Package is imported and validated before it is applied | Per-field validation is optional; you choose which fields run Business Central logic |
| Related tables | One page at a time | Get Related Tables adds dependent tables, with documented exceptions | Any number of tables in one text file, exported by table ID with filters |
| Where errors surface | As changes publish back through the page’s business logic | During validation, before the package is applied; Validate Field can be cleared per field | Per-field validation is optional; Update and Delete preview the affected records first. Behavior of a failed multi-table import is not documented |
| Skill needed | Any user with page permission and the Excel add-in | Consultant or administrator | Integrator, consultant, developer or power user |
| Cost | Included | Included | Free; Business Central license required |
When should I use Edit in Excel to import data into Business Central?
Use Edit in Excel when the data already lives on one list page and you can see every column you need. A buyer updating lead times on two hundred items is the right scale.
Microsoft Learn describes the mechanism: “With the Edit in Excel action, you make changes to records in Excel and then publish the changes back to Business Central” (viewing and editing in Excel from Business Central). Two details matter:
- Edit in Excel is not Open in Excel. With Open in Excel “you can make changes to the records in Excel, but you can’t publish the changes back to Business Central.” Check which action you clicked before you spend an hour in a workbook.
- The action requires the Business Central add-in and “is available on most lists, but not all.” Business Central also limits the exported workbook to 100 columns when OneDrive is configured for system features, which matters on wide tables such as Item.
Edit in Excel stops where the data spans several related tables or where the target table has no list page. Inserting new items with their units of measure, cross-references and stockkeeping units is three or four pages of work and easy to get out of order.
When are Configuration Packages the right way to import data into Business Central?
Configuration Packages fit when you are standing up a company and want a repeatable set of tables validated before anything is applied. Microsoft Learn puts it this way: “On the Configuration Packages page, you can work with the package to import and validate the data before you apply the package” (import business data from other finance systems). The default package “consists of 27 tables, including master data such as customers, vendors, items, and accounts.”
A partner builds a package once, exports it to Excel for the customer to fill in, imports it back, validates, and applies. The set up company configuration packages page explains the field-level controls: “For each table, you can specify which fields to exclude, and you can modify the default processing order for each field.”
Two edges are well known:
- Related tables are not always pulled in. The same Learn page warns that Get Related Tables skips conditional relations; its example is Location not being added for Customer because the relation depends on whether Location Code is filled in.
- Speed. Packages validate every included field by default; the Validate Field check box on the Config. Package Fields page is how you switch that off per field. That validation is the point of them, and it is why a large historical load through a package can run for a long time. Insight Works describes RapidStart as able to take “an extraordinarily long time to migrate data.”
For a new company with clean master data, Configuration Packages are usually the right first choice. Where they stop is history.
What does the Import Export PowerTool add for bulk data migration?
The Import Export PowerTool adds table-level import, export, update and delete across effectively any Business Central table, including protected sub-ledger tables with no page. This is a completely free app from Insight Works for Business Central. Insight Works describes it as a free data migration app for Business Central, and the word to hold onto is migration: it is not an integration tool and does not replace Microsoft’s cloud migration tooling (migrate on-premises data to Business Central online).
How does the Import Export PowerTool import data?
Everything runs from one page with four actions: Export, Import, Update, Delete. The import data guide documents each import switch:
- Source file. Import takes text files the app itself exported: export from a source company, adjust, import into the target.
- Inserts and updates. Separate switches control whether the run may insert new records, update existing ones, or both.
- Per-field validation. Prefix a field name with an asterisk and the app runs Business Central’s business logic for that field. Insight Works’ rule: validate the fields a person would type by hand and let Business Central default the rest.
- Triggers. Choose whether OnInsert and OnModify triggers run or are suppressed, and whether to use a two-step insert.
- Housekeeping. Strip stray Excel quotes, set text encoding, decide whether missing fields prompt or are ignored, and optionally disable the change log.
Two behaviors matter for inventory loads. On item journal imports the app creates lot and serial number entries automatically, which makes an opening inventory load with tracked items workable. And the demo technique for history is to summarize roughly a million detail rows into a few thousand monthly rows and write them directly into the Item Ledger Entry table, without general ledger or value entries. That is a consultant’s technique, not a button, and it belongs in a sandbox first.
Why does Insight Works call the Import Export PowerTool “very powerful and very scary”?
Because Update and Delete apply a value or a deletion across a filtered set of records, including non-editable fields and tables with no user interface. Insight Works frames the audience as a constraint, not a boast: integrators, consultants, power users and developers, because, as its product demonstrations put it, the tool is “very powerful and very scary.” The security point from the same demonstrations is blunt: the app grants nothing beyond a user’s existing permissions, and a determined user could write a small extension to delete ledger entries anyway.
The safeguards are in the product. Update and Delete preview the affected records and require a typed confirmation. Two permission sets ship with the app: a manager set that can edit the setup page, where access to protected tables and the ability to disable the change log are granted, and a user set that cannot. Give end users the second one. Deleting records that other records depend on leaves data in a bad state, and no dialog undoes that. The post on seamless Business Central data migration with a free app sets the tool against RapidStart for partners planning a migration.
If an import fails partway, are the first table’s records saved or is the whole import rolled back?
For Configuration Packages the answer is that validation happens before anything is applied: Microsoft Learn’s wording is that you “import and validate the data before you apply the package,” so a bad row is a validation error, not a half-written table. For Edit in Excel, the add-in publishes through the page’s business logic, so keep each publish to a batch you can review and repeat. For the Import Export PowerTool, a setting on the import controls the behavior: depending on how it is set, the tables already processed are kept, or the whole import is rolled back. Choose the rollback option when loading related tables that must arrive together. Either way, design the load so a failure is easy to recover from:
- Import one table per file, in dependency order (items before stockkeeping units, stockkeeping units before item journals).
- Run each file against a sandbox first.
- Use per-field validation on the fields that can fail, so problems surface as errors rather than silent bad data.
- Keep the change log on for anything you cannot easily reload.
How do I migrate data from one company to another in Business Central?
Export from the source company and import into the target, using whichever tool fits the data. For setup and master data, a Configuration Package exported from company A and applied in company B is the standard route. For a straight copy of specific tables, the Import Export PowerTool exports any number of tables by table ID with standard filter syntax to one text file, or exports an existing configuration package, and imports the result into the target company; the export data guide covers the options, including record links and notes.
Partners building demonstration data use the same import path; the guide to mastering sample data in Business Central walks through creating sales orders in Excel and importing them with the PowerTool. Whatever the tool: export, inspect, load a sandbox, then load production.
Frequently asked questions about importing data into Business Central
Are the first table’s records saved or is the whole import rolled back if the Import Export PowerTool hits an error? That depends on a setting on the import. One option keeps the tables already processed; the other rolls back the whole import. Pick rollback for related tables that must land together, and test in a sandbox first.
Is the Import Export PowerTool really free? Yes. It needs a valid Business Central license (Essentials, Premium or Team Member) and respects the user’s existing table permissions.
Can I import general ledger or journal entries with it? Ledger tables are where a bad load does the most damage, and the app respects Business Central validation on every record. Confirm the current position on general ledger and journal tables with Insight Works support before planning a finance load around the tool.
Is there a file size limit, and can I schedule imports? The knowledge base does not publish a file size ceiling, so split large loads into one file per table. Scheduling is not built in; the app publishes events that a small extension can call for unattended imports.