Article
Microsoft Business Central Packages: Finding the Right Fit
Microsoft Business Central Packages: Finding the Right Fit
Modern ERP projects no longer follow a one-size-fits-all model. Businesses vary widely in complexity, ambition and readiness for change, so their ERP implementation should reflect those differences. Microsoft Dynamics 365 Business Central supports this flexibility through scalable implementation packages that can grow alongside your organisation.
In this article, we explain how Microsoft Business Central packages are typically structured, how the T-shirt sizing approach works, what features and benefits you can expect at each level, and how a clear implementation blueprint helps reduce risk and deliver value faster. The goal is simple: help you choose the right starting point without over-engineering or under-investing.
Business Central Packages and T-Shirt Sizing
Most Business Central implementation partners use a T-shirt size model to define scope, effort and cost. Instead of forcing every organisation into the same delivery framework, this approach categorises projects by complexity and scale. The size is not determined purely by company headcount; it also reflects business process complexity, the number of users, required modules, the level of customisation, integration needs, as well as timeline and internal readiness.
The four most common package sizes are:
- Small (S) – Core financials with limited configuration
- Medium (M) – Finance plus supply chain and sales processes
- Large (L) – Advanced operations, warehousing and project management
- Extra Large (XL) – Multi-entity, heavily customised, integration-rich environments
This model makes ERP projects easier to understand and easier to plan. It also supports a phased approach: many businesses start small and expand as their confidence and needs grow.
Small and Medium Packages: The ERP Foundation
Small (S) Business Central package
A Small Business Central implementation is ideal for first-time ERP adopters or organisations replacing fragmented accounting tools. This package focuses on establishing a stable financial and operational core without introducing unnecessary complexity. It provides everything needed to gain immediate visibility into financial performance while laying the groundwork for future growth.
A typical Small package includes:
- Core financial management
- Budgeting and reporting
- Basic inventory control
- Microsoft 365 integration
- Cloud deployment
At this level, Business Central delivers comprehensive financial functionality, including general ledger, accounts payable and receivable, cash flow forecasting, bank reconciliation, budget creation with version control, fixed asset management and multi-currency support (Microsoft, 2024). Reporting and analytics are built in, with dashboards that provide real-time insight into cash position, profitability and overall financial health.
Business Central is cloud-based, users can access the system securely from anywhere, without the need for on-premise infrastructure or ongoing server maintenance. From an effort perspective, Small packages typically range from 10 to 50 implementation days and are often completed within one to three months, depending on data quality, process clarity and organisational readiness.
Medium (M) Business Central package
A Medium package builds on the Small foundation and introduces broader operational control across sales, purchasing and inventory. This is the most common choice for growing SMEs that need tighter coordination between finance and day-to-day operations.
In addition to finance, a Medium package typically includes:
- Sales and purchasing workflows
- Inventory and stock valuation
- CRM-style customer management
- Basic customisations and integrations
Sales and customer management capabilities support the full order lifecycle, from opportunity and quote tracking through to sales order processing, customer communication history and sales forecasting. Inventory management is extended to enable real-time stock tracking, automated reorder points, inventory valuation using methods such as FIFO or average costing, and full integration with sales and purchasing processes.
Medium implementations usually involve 50–100 effort days and take two to four months to deliver. They offer a strong balance between standard functionality and flexibility, enabling businesses to improve operational efficiency and data consistency without introducing unnecessary complexity too early.
Large and XL Packages: ERP at Scale
Large (L) Business Central package
A Large package is designed for organisations with complex operational needs, multiple teams and higher transaction volumes. It builds on the Medium package and extends Business Central into areas where operational efficiency, logistics control and project visibility become critical.
A typical Large package includes:
- Advanced warehouse management covering goods receiving, put-away, picking, packing and shipping across multiple warehouse locations
- Project and job costing with profitability tracking, resource allocation, time and expense capture, and project-based billing
- Multi-location inventory management with real-time visibility and tighter stock control
- Barcode scanning and cycle counting to improve accuracy and reduce manual handling
- Deeper Power BI integration for advanced operational and financial reporting
These capabilities enable organisations to coordinate finance, operations and logistics within a single system while maintaining role-based user permissions and supporting carrier and logistics integrations where required.
Large projects typically run between 100 and 200 effort days and are often delivered over three to six months, depending on the level of change management required and the complexity of integrations involved.
Extra Large (XL) Business Central package
An XL package represents enterprise-level complexity within the Business Central ecosystem.
This level may include:
- Multiple legal entities and business units
- Extensive custom development
- Numerous third-party integrations
- Legacy system migration
- Complex reporting and compliance requirements
These projects exceed 200 effort days and require a strong governance model, phased delivery and close collaboration between the partner and the client’s leadership team.
Why the Right Business Central Package Matters
Choosing the right Business Central package delivers tangible benefits across the organisation. When the implementation scope matches real business needs, teams work more efficiently, processes are better connected and decisions are made faster using real-time data. A correctly sized package also supports growth, allowing new functionality and users to be added without disruption.
Because Business Central is cloud-based, IT overheads are reduced and system maintenance becomes simpler. A phased implementation further lowers risk by enabling gradual adoption rather than a single, high-impact change.
For finance teams, Business Central creates a single source of truth, improves cash flow visibility and automates reporting and compliance. Operational teams benefit from stronger inventory control, fewer manual handovers and better coordination between sales, purchasing and logistics. Seamless integration with Microsoft 365, Power BI (Microsoft, 2025) and the Power Platform extends these benefits without adding disconnected tools.
The Business Central Implementation Blueprint
Regardless of package size, successful implementations follow a clear implementation blueprint.
A typical Business Central project includes the following phases:
- Pre-implementation planning
Define scope, objectives, stakeholders and success criteria. - Requirements gathering
Run workshops to document and prioritise business needs. - System design
Define workflows, data models and integration points. - Configuration and customisation
Configure standard functionality and build approved extensions. - Data migration
Clean, prepare and migrate legacy data into Business Central. - Testing
Conduct unit, integration and user acceptance testing. - Training and change management
Prepare users and support adoption. - Go-live preparation and launch
Execute cutover and stabilise the system. - Post-go-live support
Provide optimisation, support and future enhancements.
This structured approach reduces risk, avoids surprises and ensures the system delivers value from day one.
Conclusion
Microsoft Dynamics 365 Business Central is designed to scale but only if the implementation is sized correctly from the start. The T-shirt sizing package model provides clarity, predictability and flexibility, allowing organisations to invest wisely without locking themselves into unnecessary complexity.
Whether you are a first-time ERP adopter or modernising a legacy system, the right Business Central package helps you move faster, reduce risk and build a platform for long-term growth.
Ready to explore which Business Central package fits your business best?
Talk to Zoosh about a phased, future-proof implementation that aligns with your goals today and tomorrow.
FAQ
1. What are the different Microsoft Business Central packages?
They are structured implementation scopes, often defined as Small, Medium, Large or Extra Large, that align Business Central functionality with business complexity.
2. How long does a Business Central implementation take?
It depends on the package size. Small projects may take 1–3 months, Medium projects may take 2-4 months, while Large or XL projects can run 6-12 months or more.
3. Can we start small and expand later?
Yes. Many businesses begin with core finance and add supply chain, warehousing or custom features as they grow.
4. Does Business Central support customisation?
Yes. Customisations are delivered through upgrade-safe extensions and integrations, not core system changes.
5. Is Business Central suitable for complex businesses?
Yes. With the right package and partner, Business Central supports multi-entity, multi-location and highly integrated environments.
