Stable operation
Most talk about go-live. We talk about what happens after.
Most companies we meet have skipped 2-3 upgrades. Not out of laziness. Because nobody took responsibility for operations after go-live. The result is a system that slowly falls behind while Microsoft updates twice a year. The longer you wait, the bigger the jump.
Three ways to keep BC healthy
Continuous updates
Microsoft releases Wave 1 in April and Wave 2 in October, plus monthly security patches. We run them in your test environment first, validate against your extensions and customisations, and perform the production update on an agreed day. You will not notice it.
Automated tests
We translate your critical business flows into automated test scenarios: goods receipt, order invoicing, VAT reporting. When Microsoft releases an update, the tests run before it hits production. Read about our test method →
Controlled upgrade
Schultz was on NAV 2009. We lifted them step by step to BC in the cloud without losing business logic. That method also works from newer NAV versions or BC on-prem. Read about our upgrade process →
What does waiting cost?
Here is what it means in practice when updates are postponed.
BC must run undisturbed
When webshop, reporting and third-party apps pull directly from BC, the system is loaded. ODS offloads BC by collecting data in one place. Apps pull from there, not from BC. The result is a system that runs stable, even when things are busy.
Prices, inventory, customers and orders are synchronised from BC to ODS, and apps and channels read from there. Transactions are sent back asynchronously, so BC stays unloaded.
Hvad kunden oplevede
"CURABIS har udvist stor fleksibilitet i forhold til ændringer i tidsplanen og har hjulpet med flere ydelser end oprindeligt planlagt, herunder ekstra test, uden at miste momentum i projektet." Schultz A/S NAV 2009 til BC i skyen