The Business Central solution architect role on your project
A Business Central solution architect decides how all the parts fit together before anyone builds them. That covers how many environments and companies you need. It covers which needs standard features, add-ons or custom extensions meet. It also covers how other systems connect and how the design survives updates. Good architecture is mostly invisible. Poor architecture shows up as rework.
Last updated
What a Business Central solution architect designs first
The earliest decisions are structural and hard to reverse. How many production environments you need, given where your legal entities sit. How many companies sit in each. Whether the group shares one chart of accounts and dimensions. Also, how intercompany trade and consolidation will flow.
Next, the architect settles the environment plan around production. Which sandboxes exist, and what is each for? How do changes travel from development through testing to live? A clear path here prevents the familiar situation where nobody is sure which sandbox holds the current build. Each sandbox gets a name that states its purpose.
Sketch your structure together →
- ✓Environments and localizations
- ✓Companies per entity
- ✓Shared dimensions and accounts
- ✓Intercompany and consolidation
- ✓Sandbox purposes defined
Standard, add-on or extension: the architect's call
For every gap the architect weighs three routes. Configuration costs least to own. An AppSource app brings ready features and a publisher who maintains it. In return, you depend on that publisher. A custom AL extension fits exactly and becomes yours to maintain through two release waves a year.
We record each decision with its reasoning. The architect also sets rules for custom work. These cover how to split extensions and how they depend on each other. They cover naming and object ranges. They also say what you must never do, such as logic that blocks posting without a clear message.
Test your build decisions →- ✓Fit with the standard process
- ✓Cost of ownership
- ✓Publisher track record
- ✓Effect on future updates
- ✓License implications
Business Central solution architect: integration design
Few ERP systems stand alone. A web store, a CRM, a warehouse provider, a payroll service and a bank may all exchange data with it. For each connection, the architect first defines which system owns which record. The architect also sets the direction of flow, the trigger and what happens when a message fails.
Business Central offers several ways to connect systems. These are API pages, webhooks for change alerts and Dataverse for the Microsoft business apps. They also include Power Automate for lighter flows and built-in connectors such as the one for Shopify. Choosing the simplest mechanism that meets the need keeps the landscape maintainable. Every interface also gets a named owner.
List your connected systems →- ✓System of record
- ✓Direction and trigger
- ✓Volume and frequency
- ✓Error handling and retries
- ✓Monitoring and ownership
Business Central solution architect: security and data
We design permissions. We do not just collect them. The architect groups duties into permission sets and security groups that match roles. Where finance needs it, the architect separates duties. The architect also limits service accounts for integrations to what they need. A small, named group holds the administrative rights.
Data and performance get the same forethought. Which history you migrate and which stays in an archive. How to post large volumes, such as detailed web orders, without flooding the ledgers. Where telemetry goes, so you can trace problems after go-live. These are cheap to decide early and costly to retrofit.
Ask about design checks →- ✓Role-based permission sets
- ✓Separation of duties
- ✓Migration scope and archive
- ✓Volume handling
- ✓Telemetry destination
How our Business Central solution architect works
On our own projects, a senior consultant holds the architect role from the first workshop. That person signs off the design before the build starts. Besides this, we offer it on its own. That can be a design for a company about to begin. It can also be an independent assessment of an existing system that has grown by accretion.
The output is a solution design document written to be used. It has diagrams of environments and interfaces, the decision record and the rules for extensions. Sessions run remotely, from Phoenix, Arizona, in US business hours. We work happily beside your IT team or another delivery partner.
Commission a solution design →- ✓Environment and company diagram
- ✓Interface catalog
- ✓Decision record with reasons
- ✓Extension rules
- ✓Open risks listed
Business Central solution architect questions
Does a small implementation need a solution architect?
It needs the thinking, if not a separate person. With one company, no integrations and no custom code, a lead consultant covers it. Once several entities, connected systems or extensions are involved, a design step saves rework. For instance, a second company or a new link to a web store can change the whole plan. So a short design check early is cheap. It is also easy to do.
How does the architect differ from a technical consultant?
The architect decides what to build and how the parts relate. In turn, the technical consultant or developer builds it. An architect needs enough technical depth to judge options. The role also needs enough functional depth to know what the business is asking for.
When should the architect be involved?
From the beginning. That means before you create environments and before you buy any add-on. Choices about localization, company structure and integration ownership are the hardest to change. Teams make them early in a project.
Can you assess a design another partner produced?
Yes. We read the design and look at the system in a sandbox if one exists. Then we give written findings. They say what is sound, what carries risk and what we would change. We mean it to help the project, not to find fault.
Does the architect stay involved after go-live?
Often, in a lighter way. New integrations, extra entities and major release changes all touch the design. So many clients bring the architect back for those moments to keep the system coherent. A short design check is usually enough for a Business Central solution architect.
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