Case study: how we fix Dynamics 365 customizations

How Sewan Cleaned Up 97% of Core-Breaking D365 Customizations

Sewan logo

How We Fix Dynamics 365 Customizations Without Downtime

The Challenge

Sewan needed to fix Dynamics 365 customizations that a previous provider had built by changing the standard core of Microsoft Dynamics 365 Finance & Operations instead of extending it. As a result, every Microsoft update carried a real risk: a routine service update could break a process the business depended on. Each update meant extra testing and the fear of a production incident. Over time, Sewan lost confidence that the platform could carry the business. That is when Sewan asked us to step in.

The Business

Sewan is a cloud and telecom operator serving business customers. It moves fast, and it needs its ERP to keep pace. D365 F&O runs Sewan’s finance and operations, so the system’s stability is a business issue, not just an IT one. With the core altered, the platform that should have supported growth had become a threat to continuity. Sewan’s trust in it was at an all-time low.

The Goal

Sewan gave us a clear mission: remove every customization that altered the D365 F&O core, as quickly as possible, without disrupting daily operations. Where Microsoft’s standard features could now do the job, we would use them. Where custom logic was still needed, we would rebuild it as an upgrade-safe extension. Success would be easy to check: a clean core that takes Microsoft updates without fear.

Click to enlarge
01

Map the Dynamics 365 customizations to fix

First, we listed the existing customizations and traced which ones changed Microsoft's standard objects instead of extending them. For each one, we recorded the business need it served, the processes that depended on it and the risk of touching it. As a result, Sewan got a clear, prioritized list instead of a vague worry, and we knew where to start.

02

Fix Dynamics 365 customizations with standard features

D365 F&O had gained many features since the original code was written. So for each item, we first checked whether a standard feature or configuration now covered the need. Where it did, we moved Sewan to the standard feature and retired the custom code. That is how a standard module came back into use. Every customization replaced this way is one less thing to test with each update.

03

Fix the remaining Dynamics 365 customizations in phases

Next, we rewrote the logic Sewan still needed as extensions, the only upgrade-safe way to customize F&O. We delivered in phases, and tested each one against real processes before release, so operations never stopped. This was the hardest part of the work: keeping today's business running while replacing what sat underneath it.

01

A Core Safe to Update

We cleaned up 97% of the code that altered Sewan's F&O core. Standard features replaced part of it, and the logic Sewan still needs now runs as clean extensions. As a result, Sewan can take Microsoft's service updates without fearing that one will break production. That was exactly the goal Sewan set.

02

Zero Disruption to the Business

We made the change with zero regressions in production and no business downtime. Finance and operations teams kept working throughout. Nobody had to choose between fixing the system and running the company.

Click to enlarge
03

Less Custom Code to Carry

With standard features replacing custom code, and a standard module back in use, Sewan has less code to maintain and test with each update. Standard features also come with Microsoft's documentation, updates and support. So Sewan's team now builds on the product instead of around it, and the platform is ready for what the business needs next.

Related Work

More Dynamics 365 projects with measured results.