Bramvia — Business Central Experts
For US companies: NAV migrations, AL development and ERP rescue from a European Business Central team
A US company still on Dynamics NAV, or with a Business Central project that stalled, doesn't always need another local VAR. What it needs is AL capacity, migration experience and a team that works while yours sleeps. How we do it, what it costs, and where the time zone helps instead of hurting.
Short answer: if your company runs Dynamics NAV in the US or Canada, has a Business Central project that stalled, or needs AL development your current partner can't staff, you don't necessarily need another local VAR. You need capacity: people who read fifteen-year-old C/AL, rewrite it as clean AL extensions, migrate data without breaking the close, and deliver. We do exactly that with team members in several US states and senior consultants and AL developers in Europe — one US client running for two years — and the combination works in your favor: local hours when you need a conversation, and a European cycle that delivers overnight what your team reviews in the morning. Rates are European, not Bay Area. And we work in parts, each one invoiced only after you accept it — the only sensible terms for a remote supplier you haven't met.
Why a US company works with a European Business Central team
1. The NAV installed base is large and the people who know it are leaving. Thousands of US companies still run NAV 2013-2018, heavily customized, maintained by consultants who are retiring. Microsoft has confirmed the end of the road: extended support for NAV 2018 ends in January 2028. Finding a US consultant who wants to read old C/AL is hard and expensive; it is what we do every week.
2. AL capacity without hiring. Many US partners have more work than developers. We work white-label or directly, taking the development backlog: extensions, integrations, reports, upgrades. Your partner keeps the relationship; we bring the hours.
3. US presence plus a European cycle. We have team members across several US states, so there is someone in your hours when a conversation is needed. And Central Europe runs 6 hours ahead of Eastern Time, so the development cycle starts when your night ends: you review in the morning what was delivered while you slept. For a backlog, that is a full extra cycle every day.
4. Cost. European senior rates for AL development sit well below US and Canadian metro rates for the same seniority. The saving is real and it isn't offshore-quality: same Microsoft stack, same language, same time-zone culture of written documentation.
5. AI in the implementation itself. We use AI to read legacy code, map to standard, clean data and generate tests from your real documents — 35-40% fewer hours for the same scope. That compounds with the rate difference.
What we do for US companies
| Service | What it means in practice |
|---|---|
| NAV → Business Central migration | Object inventory, C/AL to AL conversion, data migration validated against your live system, phased go-live with NAV read-only as a safety net |
| AL extension development | Clean extensions that survive the two annual updates; code in your repository |
| Project rescue / second opinion | Independent 5-day audit when an implementation stalls |
| Integrations | Shopify, EDI, WMS, banks, CRM, Avalara/Vertex — over APIs and OData, no direct SQL |
| Power BI and reporting | The four included apps plus consolidated multi-company views |
| AI agents | Payables, sales orders and expenses switched on over one measured process, with governance |
| Development backlog as a service | Monthly capacity for partners and for internal IT teams |
| Licensing | Business Central licenses supplied through our US partner network, including Bridge to Cloud 3 enrolment |
Licenses and sales tax: covered
Two questions US companies always ask, answered plainly:
Licenses. We work with partner organizations in the US, so we can supply Business Central licenses — including enrolment in Microsoft promotions such as Bridge to Cloud 3 (30% off for qualifying NAV customers, through December 2027), which has to be declared through a CSP partner. You don't need a separate vendor for the license and another for the work.
US sales tax. We configure and integrate Avalara (and Vertex where preferred) with Business Central: nexus rules, exemption certificates, address validation, filing feeds. Where your case needs something the standard connector doesn't cover, we build it as an AL extension. What we don't do is give tax advice — that stays with your CPA, as it should.
Where we fit best
Our strongest work is technical depth and capacity: migrations, AL development, integrations, reporting and project rescue, with people on both sides of the Atlantic. Some engagements are direct with the end client; others run alongside a US partner who keeps the relationship while we deliver the build. Both work — tell us which you prefer.
Credentials you can verify
Microsoft Certified: MB-800 (Dynamics 365 Business Central Functional Consultant Associate) and MB-820 (Dynamics 365 Business Central Developer Associate). Seven Business Central apps published under our Abadyn brand. NAV 2009 → Business Central SaaS migrations in production. Named references under NDA.
The two-year client
We have been working with a US distribution company for two years: Business Central inventory reconciliation, custom AL objects, and ongoing development. It is the kind of relationship this model produces — technical, continuous, remote, with the client's team keeping full control of the functional decisions. Named reference available on request under NDA.
How the engagement works
- Free assessment (5 working days): your system, customizations, integrations, and the backlog. No cost, no commitment.
- Scope split into parts, each with written acceptance criteria.
- Each part invoiced only after you accept it. No upfront payment, no retainers you can't cancel.
- Everything is yours: code in your repository, documentation with every delivery, tenant in your name.
- Written communication by default — decisions in writing, not lost in a call at 6am your time.
FAQ
Can you supply the licenses, or do we need another vendor? We can supply them through our US partner network, including Bridge to Cloud 3 enrolment for qualifying NAV customers. One vendor for license and work.
Do you work with our existing US partner? Often, yes — white-label or as a named subcontractor. Your partner keeps the client relationship; we deliver the development.
How do you handle support across time zones? Team members in the US cover your business hours; the European team overlaps with your morning. Response windows are agreed in writing in the support agreement, and for development the overnight cycle is the advantage.
What about US sales tax? We configure and integrate Avalara (or Vertex) with Business Central — nexus, exemption certificates, address validation, filing feeds — and build extensions for anything the standard connector doesn't cover. Tax advice stays with your CPA.
Do you work with Canadian companies too? Yes. The work is the same — NAV migrations, AL development, integrations, rescue — and Business Central's Canadian localization (GST/HST/PST, bilingual documents) is Microsoft's own. Time zones are even friendlier from Toronto and Montreal than from the West Coast.
Can you sign our NDA and security requirements? Yes — NDA before we see anything, work in your tenant, and code in your repository.
How do we start without risk? Send us one thing that's stuck: a report that never got built, an integration nobody wants to touch, a migration assessment. Small first part, paid after acceptance.
Running NAV, stuck on a project, or short of AL capacity? Free assessment, no commitment — in English, and with your first reply within one working day.