A configuration package defines tables and fields you export to Excel, fill in and import back, to load master data and setup into a Business Central company.
A configuration package, part of what Business Central calls RapidStart Services, is a definition of tables and, for each table, the fields you want to move. You export it to Excel, fill in the sheets, import them back, then apply the package so the data is written into the company. It is the usual way to load master data and setup values into a new company.
Search for Configuration Packages with Alt+Q, create a package code, and add one line per table with the fields you need. The actions on the package let you export to Excel, import from Excel, validate the imported records and apply them. Imported rows and their errors are visible on the package records before anything reaches the real tables.
A company migrating 480 items creates package ITEM-INIT with the item table and the fields it needs: number, description, base unit of measure, item category and the posting groups. The export produces an Excel file, data from the old system is pasted in, and the import reports 12 rows in error because the unit of measure PCS does not exist yet. Once that unit is created, the package applies and the 480 items are in place.
Order is the most frequent problem: applying items before posting groups, units of measure or number series exist produces long error lists that look like a package fault. Switching off field validation to force rows through is worse, it creates records that look correct and then fail at posting. Applying the same package twice, or including entry tables instead of master data, causes duplicates and inconsistent balances; opening balances belong in journals, not in a package.
Keep packages small and thematic: one for the chart of accounts, one for customers, one for items, and store the Excel files with the project so the same load can be replayed on another environment. Configuration templates pair well with them, since they fill the default values, such as posting groups, that you do not want to repeat on every row.
Yes. Applying a package overwrites the fields it contains on records with the same primary key. Check the field list first, because every field in the package gets written.
Validation checks the values against the related tables, so a missing posting group, unit of measure or dimension value appears as an error on the package record. Create the missing setup, then validate again.
Zentriq's AI tools automate many of the manual processes around configuration package in Business Central. Learn about the Zentriq Agent or try Zentriq PunchOut to see how AI simplifies procurement in BC.