Every Business Central engagement is different, but the questions we get asked before signing are remarkably consistent. Here's what we tell prospective clients — no sales spin, no vague hedging.
It depends on company size, number of users, how many modules you need, and how much of your current process needs to be rebuilt versus reused. A straightforward single-entity implementation is a very different scope from a multi-entity rollout with custom extensions and integrations. We give every prospective client a firm, itemized quote after a scoping conversation — never a rough guess that grows once the project starts.
Most single-company implementations run a few months from kickoff to go-live, depending on data complexity, integrations, and how much user testing you want before cutover. Multi-entity or heavily customized environments take longer. We build the timeline with you during scoping so you know the real schedule going in, not an optimistic one that slips.
Business Central is built for small and mid-sized businesses that have outgrown entry-level accounting software or an aging on-premises ERP, but don't need — or want to pay for — a large enterprise platform. We work with clients across manufacturing, distribution, professional services, and retail, generally from a few dozen users up through several hundred.
No. The discovery call is exactly that — a conversation to understand your current system, pain points, and goals so we can tell you honestly whether Business Central is the right fit and roughly what it would take. There's no obligation attached, and no hard sell if it turns out not to be a match.
Business Central is Microsoft's cloud-capable successor to Dynamics NAV, built on much of the same underlying data model and extension framework. The practical differences are the delivery model — cloud-first rather than purely on-premises — a modernized interface, native Power Platform and Copilot integration, and an ongoing update cycle instead of periodic version upgrades. For most NAV customers, the migration path is more of an upgrade than a rebuild.
Some, in spirit rather than in code. Older NAV and GP customizations were often built directly into the base application, which doesn't carry forward cleanly to Business Central's extension-based model. We review each customization during the assessment phase and rebuild the ones you still need as proper extensions — which also makes them far easier to keep working through future updates.
You choose how much history you want live in the new system versus archived. We typically migrate a defined window of transactional detail plus full master data, and keep older history accessible through reporting or a read-only archive of the legacy system, so you're not paying to carry every historical record into daily operations.
We plan cutover for a scheduled window — typically a weekend or other low-activity period — and rehearse the process beforehand using a full test migration, so the actual cutover is a repeat of something we've already run successfully rather than a first attempt. Staff are trained ahead of go-live so the switch to daily use in the new system is a matter of hours, not days.
Not necessarily. Users who only need to view finished dashboards can often do so through Business Central itself or through report distribution options that don't require an individual Pro license, while a smaller group of report builders and power users hold full Power BI licenses. We size the license mix to how your team actually consumes reporting, rather than defaulting everyone to the most expensive tier.
Yes — this is one of the more common ways clients engage us. If you're already on Business Central, or even still on a legacy system with usable data, we can build Power BI dashboards against your current environment well ahead of any broader project, giving you better visibility immediately rather than waiting on a longer implementation timeline.
Yes. Power BI, reporting, and business analytics is one of our core practice areas in its own right — not a follow-on service that only exists to support a Business Central project. We take on standalone BI engagements: building data models, dashboards, and reporting layers against whatever systems you're already running, ERP work included or not. See Power BI & Business Analytics for the detail.
Yes. One of the more valuable things Power BI does is sit above multiple source systems at once — pulling operational and financial data out of Business Central alongside CRM records, marketing platform data, and web or social analytics, and modeling all of it into a single reporting layer. That's how a sales or leadership dashboard can show pipeline and campaign activity next to actual revenue and margin, instead of living in a separate spreadsheet nobody reconciles. More on this on our Power BI & Business Analytics page.
Refresh frequency is configurable and depends on the use case — some clients want near real-time figures for daily operational dashboards, others are fine with a scheduled refresh a few times a day for management reporting. We set this up based on how time-sensitive each report actually needs to be, since more frequent refreshes carry a real performance and licensing cost.
No — we don't create content, manage ad spend, or run community management, and that's a deliberate line we draw. Digital intelligence is a data and analytics discipline: we take the digital and social engagement data your business already generates — website behavior, campaign response, social interactions — and turn it into structured customer intelligence, then connect that intelligence into your CRM and sales pipeline so sales teams are working qualified, prioritized leads rather than a raw contact list. Details are on our Digital Intelligence & Sales Pipeline page.
It's connected to both. Power Automate and the wider Power Platform sit alongside Business Central and Power BI as part of the same Microsoft data and application stack, and we use them to automate approval workflows, data entry, and system-to-system handoffs that would otherwise be manual — often triggered by conditions inside Business Central or surfaced as alerts inside a Power BI dashboard. It's available as its own engagement or bundled into an ERP or reporting project. See Power Platform & Automation for what that covers.
Our support plans cover issue troubleshooting, user questions, minor configuration changes, monitoring of integrations and scheduled jobs, and guidance through Microsoft's update cycle so new releases don't break your customizations. Higher tiers add proactive system health checks and a set allocation of hours for small enhancements, so support isn't limited to firefighting. Full details are on our Support Plans page.
Response times are defined per support tier and by issue severity — a system-down issue gets prioritized well ahead of a minor how-to question. Exact response targets are set out in your support agreement so there's no ambiguity about what to expect when you raise a ticket.
Yes. Support needs change as your team and system usage evolve, so clients move between tiers regularly — usually stepping up ahead of a busy season or a system change, and sometimes stepping down once things stabilize. There's no lock-in penalty for adjusting your plan.
We operate from five offices — Melbourne (our headquarters), Toronto, Los Angeles, Orlando, and Colombo — which gives us practical working-hours overlap with clients across Australia, North America, and beyond. Projects are staffed with a lead consultant who owns the relationship, backed by a delivery team that can hand off across time zones for support coverage rather than leaving you waiting on a single person in a single office.
Business Central runs on Microsoft's cloud infrastructure with its associated compliance and security controls, and we layer our own practices on top — least-privilege access to client environments, defined data handling procedures for migration projects, and no retention of client data beyond what a project or support agreement requires. We're happy to walk your security or IT team through specifics before you sign anything.
Often, yes. Our five offices are our home base, but Business Central implementation and support work is largely delivered remotely, so we take on clients outside those regions where the time zone overlap and project fit make sense. The best way to find out is to reach out and describe your situation directly.