There are two main ways to move data between companies in Business Central. The first is Copy Company, which duplicates an entire company at a point in time. The second is Configuration Packages, which give you control over which tables and records to export and import.
This guide focuses on Configuration Packages because they are the more common tool for targeted data migration, moving a chart of accounts, a customer list, or item records from one company to another without copying everything.
When to Use Each Approach
| Approach | Best for |
|---|---|
| Copy Company | Full company clone, setting up a new company based on an existing live one |
| Configuration Packages | Selective migration, specific tables, master data, or setup records |
Copy Company is covered in How to Configure Companies in Business Central. The rest of this guide covers Configuration Packages.
What Configuration Packages Do
A Configuration Package defines a set of tables to export from Business Central. Once exported to Excel, the data can be reviewed, adjusted, and then imported into a different company. After import, you apply the package to write the data into the company’s tables.
Common use cases:
- Copying the chart of accounts from a template company to a new one
- Moving a customer or vendor list between companies
- Transferring item records and units of measure
- Replicating dimension values and posting group setup
Configuration Packages do not carry transactions, they work on setup and master data tables. Posted ledger entries cannot be moved this way.
Step 1: Create a Configuration Package in the Source Company
Make sure you are working in the company that holds the data you want to export.
- Search for Configuration Packages using
Alt + Q. - Select New.
- Enter a Code (e.g.,
COA-EXPORT) and a Package Name (e.g.,Chart of Accounts Export).
Step 2: Add Tables to the Package
- On the Configuration Package card, go to the Tables subpage.
- Select Add Table or use the Add Tables action to select multiple at once.
- Enter or look up the Table ID for each table you want to include.
Common table IDs:
| Table | Table ID |
|---|---|
| G/L Account | 15 |
| Customer | 18 |
| Vendor | 23 |
| Item | 27 |
| Dimension | 348 |
| Dimension Value | 349 |
- For each table, you can filter which records to include. Select the table row and use Table Filters to limit records by field values (for example, only customers in a specific country).
Step 3: Export to Excel
- On the Configuration Package card, select Export to Excel from the action bar.
- Business Central generates an Excel file with one sheet per table.
- Download and open the file.
Each sheet contains the table’s field names as column headers and the current data as rows. You can edit this data directly in Excel, add rows, remove rows, or change values, before importing.
Step 4: Edit the Data in Excel
Review the exported data and make any necessary changes:
- Remove records you do not want to import (delete the rows)
- Add records by inserting new rows with the correct values
- Adjust field values that should differ in the target company (for example, different posting groups)
Do not change column headers or sheet names. The import process uses these to map data back to the correct fields.
Step 5: Import the Package into the Target Company
Switch to the company you want to import data into.
- Search for Configuration Packages and open the page.
- If the package does not exist yet in this company, select Import Package from the action bar.
- Select the Excel file you exported and edited.
- The package is created in the target company with the imported data staged for review.
Alternatively, if you want to import from a .rapidstart file instead of Excel, use Import from File and select the .rapidstart package file.
Step 6: Apply the Package
Importing the file only stages the data. You need to apply the package to write the data into the actual company tables.
- Open the imported Configuration Package in the target company.
- Review the No. of Package Records and No. of Errors columns in the tables list to check for issues.
- Select Apply Package from the action bar.
If there are validation errors, Business Central will list them after applying. Common issues include:
- Missing related records (for example, a posting group that does not exist in the target company)
- Duplicate records (a customer with the same number already exists)
- Field values that do not match allowed options
Fix errors either in the Excel file and re-import, or resolve the dependency in the target company first, then re-apply.
What Cannot Be Moved This Way
Configuration Packages are designed for setup and master data. The following cannot be reliably transferred using this method:
- Posted ledger entries (G/L entries, customer ledger entries, etc.)
- Open transactions (unposted journals)
- Bank reconciliation records
- Historical data with complex dependencies
For opening balances, the standard approach is to post an opening balance journal in the target company after the master data is in place.
Tips for a Clean Migration
- Always test the package on a copy of the target company first before applying to a live environment.
- Apply tables in dependency order, dimensions before dimension values, posting groups before accounts that reference them.
- Use table filters to keep packages small and focused rather than exporting entire tables you do not need.