Working with configuration packages in Business Central
Configuration packages in Business Central are the built-in way to move setup and master data into a company without code. A package is a list of tables and fields. You export it to Excel, fill it in, import it and apply it. This guide covers building a package, loading data, reading errors and knowing the limits.
Last updated
What configuration packages in Business Central do
Packages are part of the company setup tools. Search for Configuration Packages, create a new one and give it a code. A package can hold setup tables such as payment terms and posting groups. It can also hold master data such as customers, vendors and items, and journal lines that wait to be posted.
Two uses come up again and again. During an implementation, packages carry cleaned data from spreadsheets into the new company. Later, they copy settled setup from a sandbox to production, or from one company to a new one. That way, a second entity starts with the same posting groups and number series.
Plan your data loads →
- ✓Setup and posting groups
- ✓Customers and vendors
- ✓Items and units
- ✓G/L accounts and dimensions
- ✓Opening journal lines
Choose tables for configuration packages in Business Central
Add lines to the package by table number, or pull in related tables with the Get Tables action. For each table, open the fields list. Choose which fields to include and which to validate. Validation runs the same logic as typing the value by hand, so defaults and checks apply.
Order matters. A customer cannot exist before its posting groups and payment terms do. So parent tables get a lower processing order than the tables that refer to them. Include the primary key fields and keep the field list lean. Leave out calculated fields and anything Business Central fills in itself.
Build a package with us →- ✓Included fields chosen
- ✓Validate Field where sensible
- ✓Processing order set
- ✓Primary key present
- ✓Filters for partial export
Export to Excel, fill and import
With the tables chosen, select Export to Excel. The workbook has one sheet per table. The chosen fields are the columns, and any existing records are the rows. Fill in the rows, but leave the column headings and sheet structure alone, because the import matches on them.
You can show dimensions as columns, so default dimensions load with the master record. Watch for the usual spreadsheet traps. Excel strips leading zeros from codes, switches date formats and turns long numbers into scientific notation. Option values must also match the field's wording exactly. Import from Excel then brings the rows into the package.
Check your import sheets →- ✓Leading zeros lost
- ✓Date formats mixed
- ✓Option values misspelled
- ✓Codes longer than the field
- ✓Headings renamed by accident
Apply the package and work through errors
Imported rows sit in package records where you can inspect them. Each table line shows the number of records and the number of errors. Choose Apply Package, or Apply Data for a single table. Business Central then writes the rows into the real tables in processing order, and it validates as it goes.
Rows that fail stay behind with an error text. Usually a related code does not exist, or the field rejects a value. Fix the row in the package record, or correct the source and import again. Then reapply. Applying again updates existing records, so you can run a package more than once.
Work through errors together →- ✓Related record missing
- ✓Field value not allowed
- ✓Wrong processing order
- ✓Mandatory field left empty
- ✓Number series conflict
Limits of configuration packages in Business Central
Packages suit setup and moderate volumes of master data. Very large tables are slow to apply and awkward in Excel. For high volumes, split the data into several packages. Or use another route, such as the cloud migration tool or an API load.
Never load posted documents or ledger entry tables directly. Those records must come from posting. Otherwise the ledgers stop agreeing with each other. Load journal lines and post them instead. You can also export a whole package as a file and import it elsewhere. That is a neat way to copy setup between environments.
Choose the right migration route →- ✓Ledger entry tables
- ✓Posted documents
- ✓Very large data sets
- ✓Ongoing integrations
- ✓Data needing transformation logic
Questions about configuration packages in Business Central
What is the difference between a package and a configuration template?
A package moves data in bulk. A template holds default field values, such as posting groups, and applies them when someone creates a new customer, vendor or item. They work well together. For example, a template can fill fields that your spreadsheet leaves empty. So use a package for the rows and a template for the defaults.
Can a package copy setup from sandbox to production?
Yes. Build the package in the sandbox with the setup tables you changed. Export it as a package file, import it in production and apply it. Check the differences first, because applying overwrites matching records in the target company. So rehearse the apply on a sandbox copy of production before you touch live data.
Why does Apply Package report errors on rows that look correct?
Most often a related table was not loaded first, so a code on the row does not exist yet. Set the processing order, apply the parent tables, then reapply. Trailing spaces and option values in another language are the next most common causes. Check the error text on the row, because it names the field that failed.
Do packages run the business logic on each field?
For fields marked to validate, yes. The field's validation code runs as if a user typed the value. That helps with defaults and checks. But it can overwrite other columns. So the field order and the choice of which fields validate both matter. Test a small sample first and look at the result before you apply the full file.
Who should own packages during a project?
Usually a consultant builds the package structure, and a named person in your business owns the content of each sheet. That split works because the structure is technical. But the customer list, item data and open balances are decisions only your team can make. A clear owner for each sheet keeps configuration packages in Business Central on track.
Book a discovery call
Let's talk through your move to Business Central.
A focused call with a senior consultant. We learn how your business runs today, give you an honest view on whether Business Central fits, and outline scope and next steps before you commit to anything.
What happens after you send the form