Business Central Configuration Package Worksheet
A Business Central configuration package (RapidStart) loads data table by table, and the order matters: a customer cannot validate without its posting groups, payment terms and country codes. This worksheet gives you one place to list the tables, the sequence, expected volumes and the error budget so the cutover plan is explicit before anyone imports a file.
| Load order | Table ID | Table name | Package code | Source system | Records | Expected error % (%) | Expected errors | Apply method | Owner | |
|---|---|---|---|---|---|---|---|---|---|---|
0 | ||||||||||
13 | ||||||||||
93 | ||||||||||
48 | ||||||||||
592 | ||||||||||
316 |
Table IDs shown are the standard BC base objects: 3 Payment Terms, 15 G/L Account, 18 Customer, 23 Vendor, 27 Item, 5404 Item Unit of Measure. Others you may add: 4 Currency, 9 Country/Region, 14 Location, 204 Unit of Measure, 250 Gen. Business Posting Group, 251 Gen. Product Posting Group, 270 Bank Account, 348 Dimension, 349 Dimension Value. Setup tables, then posting groups and dimensions, must load before master data. Confirm IDs in your own version.
Need a second pair of eyes on your BC data migration plan?
Optional: an expert review of your table list, load order and cutover approach.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
List each table you will migrate with its ID and name, assign a load order, and group tables into packages such as SETUP, FIN and MASTER. Enter record counts from the source system and an expected error percentage based on your data profiling. The sheet computes expected errors per table and an overall rate, which you can compare with the actual Config. Package Errors after each trial import.
- One row per table, in dependency order
- Use trial loads to replace guessed error percentages with real ones
- Export to Excel to share with the data owners
Why load order and validation matter
In a configuration package, Apply Data runs field validation like manual entry, so triggers fire and dependent setup must already exist. Typical order is general setup (payment terms, currencies, countries and post codes, units of measure), then posting groups and the chart of accounts, dimensions, locations, and only then customers, vendors, items and opening balances. Loading master data first produces large error lists that are all the same missing-setup problem.
Reading the error budget
If a table shows a high expected error rate, fix the source data or the mapping before the cutover rehearsal instead of correcting errors one by one in the package. Duplicate keys, blank required fields, invalid option values and unit of measure mismatches are the usual causes. A realistic plan runs at least two full trial loads and reduces the error count each time.
Common mistakes
Teams often import opening balances through the package when a general journal import is cleaner and auditable, and they forget that some tables are better loaded with dataport-style tools or Excel edit in the client. Keep the worksheet versioned and tied to the cutover checklist.
- Loading customers before posting groups exist
- Not freezing source data before the final extract
- Skipping the post-load reconciliation of counts and balances
Frequently Asked Questions
What is a Business Central configuration package?
It is a RapidStart tool that exports and imports table data, including setup and master data, as a package file. You choose tables and fields, import the data, then apply it so validation runs.
In what order should I load tables?
Load basic setup first, then posting groups and chart of accounts, dimensions, then master data like customers, vendors and items, and finally opening balances or journals. Follow table relations.
Can configuration packages migrate transactions?
They are best for setup and master data. Open transactions and balances are usually brought in through journals or dedicated migration tools so they post with proper audit trails.
How many trial loads should I run?
Plan at least two complete rehearsals. Each should reduce errors and give you a timed runbook for the final cutover, with reconciliation of record counts and balances after each run.
If you are migrating from a legacy ERP into Business Central and want help profiling and mapping the data, Netray and our partners can review the plan.
Related Tools
Business Central Posting Groups Setup Worksheet
Map general business and product posting groups to the G/L accounts they should post to before you configure General Posting Setup.
ERP Migration & SelectionNAV to Business Central Upgrade Assessment
Answer ten questions about your Dynamics NAV environment to see how ready you are to upgrade to Business Central and what to tackle first.
Microsoft DynamicsBusiness Central Year-End Close Checklist
Work through preparation, subledger, inventory, closing and post-close steps for a clean Business Central fiscal year end.
More Microsoft Dynamics tools
See all- Business Central API v2.0 URL Builder
- Business Central Permission Set Design Worksheet
- Business Central Data Migration Field Mapping Worksheet
- Business Central Chart of Accounts Mapping Worksheet
- Business Central Implementation Statement of Work Template
- Business Central Functional Design Document Template
- Business Central User Acceptance Test Script Template
- Business Central Go-Live Cutover Plan Template
- Business Central License Cost Calculator
New to Microsoft Dynamics NAV and Business Central on-prem? Start with the Microsoft Dynamics NAV and Business Central on-prem guide and toolkit.
Keep exploring
Free tools
- Business Central License Cost CalculatorEstimate Business Central monthly and annual subscription cost from your user mix and your own price per user, with a chart of cost growth.
- Business Central Licensing Cost CalculatorEnter user counts and your per-user prices to see monthly and annual Business Central subscription cost with an optional discount.
- Business Central Item Setup Options ReferencePlain-language meaning of the item card options in Business Central that drive costing and planning, with guidance on when each fits.
ERP fixes and how-tos
- Business Central Item Templates and Customer TemplatesCreate and use item templates and customer templates in Business Central to default posting groups, costing method and dimensions on every new record.
- Standard Costing in Business Central: Setup, Expected Cost and VariancesStandard costing in Business Central: costing methods, setting standard cost, the Standard Cost Worksheet, variances and expected vs actual cost.
- Business Central Manufacturing Setup: Items, BOMs, Routings and Production OrdersSet up Business Central manufacturing: Manufacturing Setup, work centers, production BOMs, routings, item settings, manufacturing policy and demo data.
AI on your ERP
- AI for Dynamics 365 Business Central in Discrete ManufacturingGrounded AI for Dynamics 365 Business Central discrete manufacturers: production orders, planning worksheets, routings and costing, on a private LLM.
- AI for Business Central manufacturing operations, beyond CopilotAI for Business Central manufacturing beyond Copilot: grounded answers on production orders, routings, and capacity via APIs v2.0, on-prem capable.
Integrations
- How to add WhatsApp to Microsoft Dynamics 365 Business CentralHow to connect WhatsApp to Dynamics 365 Business Central: API v2.0 or custom API pages, webhooks, template messages, and two-way replies that post back safely.
- How to add AI agents to Dynamics 365 Business CentralHow to add AI agents to Dynamics 365 Business Central: API v2.0 and custom API pages as the tool layer, approval gates, SaaS vs on-prem, and build options.
Software
- Microsoft Dynamics 365 Business CentralDynamics 365 Business Central explained for manufacturers: modules, APIs, AL extensions, deployment, strengths, limits and alternatives for small and mid-size firms.
- Microsoft Dynamics 365 Finance and Supply ChainDynamics 365 Finance and Supply Chain Management explained for manufacturers: modules, data entities, OData, deployment, strengths, limits and alternatives.