9 signs that D365 implementation was done poorly

Implementation of the Microsoft Dynamics 365 ERP system is a project that involves every department in the company and requires many months of intensive work. Sometimes it’s not immediately obvious that something is wrong. Below we present 9 signs that something may have gone off track and is worth fixing.

A long period of “firefighting” after go-live, a flood of recurring issues, lack of stability, and the feeling of being “stuck in tickets.” This is a classic sign that implementation errors are taking their toll after launch.

Key steps are handled in Excel, “shortcuts,” or auxiliary systems, and decisions are not based on a single, centralized source of truth.

Omitted legal and tax requirements (e.g., E-Invoicing, SAF-T, split payment, white list) lead to delayed go-live, document recording issues, and user resistance. Additional red flags include the lack of automatic NBP exchange rate handling with delay and taxpayer validation.

Inconsistent master data, errors in the opening balance, and issues with settlements after data transfer - all result from insufficient migration testing and data quality checks.

Testing is limited to individual screens instead of end-to-end scenarios, with no integration, regression, or performance tests; users are brought into UAT too late.

A high number of code modifications, no extension guidelines, and no update maintenance plan - this is a recipe for a fragile system and costly upgrades.

No approved application blueprint, unclear role of D365 in the ecosystem, inconsistent or duplicate integrations and data flows.

Missing roles like Solution Architect, unclear division of responsibilities, and minimal training or instructions - users don’t “get” the solution even from the testing phase.

Poorly managed environments (Dev/Test/UAT/Prod), no refresh/sync procedures, plus suboptimal licenses and user roles - this signals high maintenance costs and team workflow bottlenecks.