Configuration packages are the standard tool for loading data into Business Central during an implementation or company migration. They let you export a table structure to Excel, fill in records, and import the data back, with validation before anything is applied to the database.
They work for any table in Business Central, but the most common use cases are loading master data: customers, vendors, items, and chart of accounts records.
When to Use Configuration Packages
Configuration packages are best suited for:
- Initial data load during a new implementation
- Migrating data from another company within BC
- Bulk-creating setup records (payment terms, posting groups, etc.)
For ongoing integrations or regular data imports, use the API or a dedicated import routine instead. Configuration packages are a one-time or infrequent tool, not a scheduled data feed.
Step 1: Navigate to Configuration Packages
- Search for Configuration Packages using
Alt + Q. - The list shows any existing packages. Select New to create a fresh package.
Step 2: Create a New Package
- On the Configuration Package Card, enter a Code (e.g.
CUSTIMPORT) and a Package Name (e.g.Customer Import – March 2026). - Leave Exclude Configuration Tables unchecked unless you specifically want to skip setup tables.
Step 3: Add Tables to the Package
- In the Tables section of the package card, select Add Tables.
- Search for and select the tables you want to include. Common tables:
| Table Name | Table ID |
|---|---|
| Customer | 18 |
| Vendor | 23 |
| Item | 27 |
| G/L Account | 15 |
- Each table appears as a row. You can add multiple tables to a single package.
Step 4: Review Field Mapping
- Select a table row and then choose Fields to see which fields are included in the export.
- By default, all fields are included. Uncheck Include Field for fields you do not need to populate, this keeps the Excel template simpler.
- Required fields (those that will cause validation errors if empty) are marked in the list.
Step 5: Export the Package to Excel
- Back on the package card, select Export to Excel from the action bar.
- Business Central generates an Excel file with one worksheet per table. Each sheet has a header row matching the field names in BC.
- Open the file and fill in one row per record. Do not change the column headers or add new sheets, the import will fail if the structure is modified.
Common fields to populate for customers:
| Field | Notes |
|---|---|
| No. | Customer number, leave blank to use number series |
| Name | Customer name |
| Customer Posting Group | Must match an existing posting group code |
| Gen. Bus. Posting Group | Must match an existing posting group code |
| Payment Terms Code | Must match an existing payment terms code |
| Currency Code | Leave blank for local currency |
Step 6: Import the Excel File
- On the Configuration Package Card, select Import from Excel.
- Select the filled-in Excel file. Business Central reads the rows into the package staging area, records are not yet written to the database at this point.
Step 7: Validate Records
- Select Validate Package to check the imported rows against Business Central’s validation rules.
- Any rows with errors are flagged. The No. of Errors field on each table row shows the count.
- Select a table row and choose Errors to see a list of validation messages. Common errors include missing posting groups, invalid codes, or required fields left blank.
- Fix errors either by editing the Excel file and re-importing, or by correcting records directly in the package using Edit Records.
Step 8: Apply the Package
- Once validation passes (or after reviewing and accepting remaining errors), select Apply Package.
- Business Central writes the records to the database. A confirmation message shows how many records were created or updated.
- Check the imported tables, for example, open the Customer List, to confirm the data is correct.
Handling Validation Errors
If a field value does not match an existing code in Business Central (for example, a posting group that has not been set up yet), the record will fail validation. The fix is usually one of two things: either set up the missing code in BC before importing, or correct the value in the Excel file and re-import.
Do not apply a package with a large number of unresolved errors. Partial applies can leave inconsistent data that is difficult to clean up.
To move data between companies within the same Business Central environment, see How to Move Data Between Companies in Business Central.