ERP/CRM Postmortem Files

Postmortem notes on startups, ISV apps, and ERP/CRM solutions - what happened, why they changed, and what can be learned from their journey, within and beyond the Microsoft ecosystem.

PROFILE #0015 · Microsoft First-Party Products

Microsoft Dynamics C5

A Danish accounting system that became one of the country's most widely used business applications eventually reached the end of its product life as Microsoft moved customers toward Business Central.

Status
Shutdown
Year
2026
Founded
1994
Funding
Developed by Damgaard Data; later part of Navision and Microsoft

The Idea

Dynamics C5 began in Denmark as Concorde C5, a business management system developed by Damgaard Data for smaller companies.

The product was introduced in 1994 as a successor to the company’s earlier Concorde products. It was built around technology derived from Damgaard’s Concorde XAL platform, but was designed for a different market: smaller businesses that needed accounting and business management software without the complexity of a larger ERP system.

C5 became particularly successful in Denmark. Its relatively simple architecture, flexibility, and ability to be customized made it attractive to small and medium-sized businesses and created a large local partner ecosystem.

The product also benefited from a broader trend that helped many European ERP vendors grow during the 1990s: businesses were moving from standalone accounting software toward integrated systems covering finance, sales, purchasing, inventory, projects, and other business processes.

C5 was therefore not an unsuccessful product.

It became an important part of the Danish business software market.

The Rise and Fall

The first major change came through corporate consolidation.

Damgaard Data merged with Navision in 2001. Microsoft subsequently acquired Navision in 2002, bringing C5 into Microsoft’s business applications portfolio.

The product was renamed several times as ownership and branding changed, eventually becoming Microsoft Dynamics C5.

Microsoft continued releasing new versions for many years. Dynamics C5 2012, for example, was released in January 2012 and remained under mainstream support until January 2019. Later versions continued the product line, with Dynamics C5 2016 becoming the final major version in the traditional C5 product family.

The problem was not that C5 suddenly stopped working.

The bigger issue was that Microsoft increasingly had another strategic direction for the small and mid-sized business market.

Rather than maintaining several generations of separate ERP products indefinitely, Microsoft was consolidating its business applications around the Dynamics portfolio and, increasingly, cloud-based Business Central.

This created a long transition period for C5 customers.

The product remained usable and supported, but its strategic future became increasingly limited.

What Happened to the Product

Microsoft eventually stopped treating C5 as a product for continued long-term development.

Dynamics C5 2016 reached the end of support on April 14, 2026. Microsoft lists the product under its fixed lifecycle policy, marking the end of a product line that had evolved for more than three decades from the original Damgaard technology.

However, Microsoft did not simply leave C5 customers without a migration path.

Business Central includes a dedicated C5 Data Migration extension that can migrate customers, vendors, items, general ledger accounts, and historical financial entries from Dynamics C5 2012.

Microsoft has also provided a transition path from Dynamics C5 2012 to Business Central on-premises through its Dynamics product transition policy.

More recently, Microsoft introduced a Business Central Basic Experience extension specifically aimed at customers coming from Dynamics C5. The extension provides a simplified set of business capabilities while allowing C5 data to be migrated into Business Central. Microsoft currently makes this option available to customers in Denmark and Iceland.

This makes the end of C5 more accurately described as a product retirement and migration story rather than a sudden product failure.

Why It Changed

C5 illustrates the lifecycle problem faced by mature ERP products.

A successful ERP can accumulate a large installed base, partner ecosystem, customizations, and customer-specific processes. That makes the product valuable, but it also makes modernization expensive.

Microsoft eventually had to decide where to invest its development resources.

Maintaining an older, regionally focused ERP alongside newer products created additional technology and product-management complexity. Business Central offered Microsoft a more unified platform for small and medium-sized businesses, with ongoing cloud development and a broader international ecosystem.

From Microsoft’s perspective, moving customers toward Business Central created a more sustainable product strategy.

From the customer’s perspective, however, the decision created a migration project.

That difference is important.

A vendor can consider a product strategically obsolete even when customers still consider it perfectly adequate for their day-to-day operations.

The Legacy

The end of Dynamics C5 does not erase its importance.

C5 was part of a generation of European ERP products that were built around local accounting requirements, strong reseller networks, and extensive customization.

Its history also connects several generations of the Microsoft ERP portfolio:

Damgaard Data → Concorde C5 → Navision/Damgaard → Microsoft Dynamics C5 → Business Central migration

The product itself is reaching the end of its lifecycle, but much of the customer knowledge, business data, partner expertise, and functional requirements that accumulated around C5 can continue in newer systems.

Lesson: A successful ERP can still reach the end of its life. Product retirement is not necessarily evidence that the original product was a failure. Sometimes it simply means that the vendor’s technology strategy has moved on.

For customers, the important lesson is to distinguish between software that still works and software that still has a strategic future. Those are not always the same thing.


Sources

  • Microsoft Learn, “Dynamics C5 2012 - Microsoft Lifecycle”: Microsoft Learn
  • Microsoft Learn, “Ending Support in 2026”: Microsoft Learn
  • Microsoft Learn, “Using the C5 Data Migration Extension”: Microsoft Learn
  • Microsoft Learn, “Basic Experience Extension”: Microsoft Learn
  • Microsoft Learn, “Dynamics 365 Business Central 2020 Release Wave 2 - Ordering and Product Line Transition”: Microsoft Learn
  • Microsoft, “Microsoft Business Solutions Group Delivers on Microsoft Dynamics”: Microsoft