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 #0018 · Microsoft First-Party Products

Microsoft Great Plains eEnterprise

A major mid-market ERP product was absorbed into Microsoft's Great Plains portfolio after the acquisition of Great Plains Software, illustrating how enterprise software products can disappear through consolidation rather than failure.

Status
Acquired then discontinued
Year
2003
Founded
1999
Funding
Great Plains IPO in 1997; acquired by Microsoft for approximately $1.1 billion in 2001

The Idea

Great Plains Software developed business management applications for small and mid-sized companies.

The company’s portfolio expanded significantly during the 1990s, eventually covering financial management, distribution, manufacturing, project accounting, human resources, payroll, supply chain management, and other business processes.

One of its important products was eEnterprise.

eEnterprise was positioned as a scalable business management platform for mid-market organizations, particularly companies with more demanding financial, distribution, and multinational requirements.

By the late 1990s, eEnterprise had become an established product within the Great Plains portfolio.

Its positioning was different from the simpler accounting products aimed at smaller businesses.

It was designed for organizations that needed a broader ERP capability and more scalability.

The Rise and Fall

Great Plains was itself acquired by Microsoft.

Microsoft completed the acquisition of Great Plains Software in April 2001 for approximately $1.1 billion in stock. At the time, Microsoft stated that Great Plains would continue developing, marketing, and supporting its business applications, including Dynamics, eEnterprise, and Solomon.

Initially, eEnterprise continued as an active product.

In June 2001, Microsoft Great Plains announced eEnterprise Release 6.0 with expanded financial and distribution capabilities, positioning it as a global business solution for mid-market organizations.

This is important because it shows that Microsoft did not acquire Great Plains and immediately abandon eEnterprise.

The product continued receiving investment after the acquisition.

The change came later as Microsoft began consolidating overlapping applications.

What Happened to the Product

Microsoft eventually decided to combine product lines rather than maintain multiple overlapping ERP applications.

In March 2003, Microsoft Business Solutions announced Great Plains 7.5. The new release explicitly combined the former Microsoft Business Solutions-Dynamics and eEnterprise applications into a single solution.

Microsoft released Great Plains 7.5 in April 2003 and described it as an integrated solution drawing from the strengths of the former Dynamics and eEnterprise applications.

This effectively ended eEnterprise as a standalone product identity.

The important distinction is that its functionality did not simply disappear.

Capabilities from eEnterprise were incorporated into the consolidated Great Plains product.

The customer therefore moved from:

Great Plains eEnterprise

to:

Microsoft Business Solutions-Great Plains

rather than being forced to abandon the entire functional area.

Why It Changed

The eEnterprise story was primarily driven by portfolio consolidation.

Microsoft inherited multiple business application products through its acquisition of Great Plains and the earlier development of its own business applications.

Keeping several products with overlapping functionality would have increased development, support, training, partner, and marketing costs.

A consolidated product offered Microsoft a simpler way to serve the mid-market.

The strategy also allowed Microsoft to combine technology and functionality from different product lines rather than forcing every acquired product to remain independent.

For eEnterprise, this meant that the product’s individual identity was no longer strategically necessary.

The technology and functionality were more valuable as part of a larger product.

The Legacy

eEnterprise is therefore a useful example of a different type of enterprise software “failure.”

The product itself was not necessarily unsuccessful.

It had customers, continued receiving enhancements after Microsoft’s acquisition of Great Plains, and contained capabilities that Microsoft considered valuable enough to incorporate into the next generation of its ERP offering.

What disappeared was the standalone product.

The progression was roughly:

Great Plains → eEnterprise → Microsoft acquisition → Great Plains 7.5 consolidation

This is fundamentally different from a product that is simply abandoned because it cannot find a market.

Lesson: In enterprise software, a product can disappear because it succeeds inside another product.

For customers, product consolidation can be less disruptive than outright retirement when the successor retains the capabilities they depend on. For vendors, however, the process can mean that individual product identities become less important than the functionality they contribute to the overall portfolio.


Sources

  • Microsoft, “Microsoft to Acquire Great Plains”: Microsoft
  • Microsoft, “Microsoft Completes Acquisition of Great Plains”: Microsoft
  • Microsoft, “Microsoft Great Plains Enhances eEnterprise Offering”: Microsoft
  • Microsoft, “Microsoft Business Solutions Highlights Applications That Help Companies Transform the Way They Do Business”: Microsoft
  • Microsoft, “Microsoft Business Solutions Releases Great Plains 7.5”: Microsoft
  • Microsoft, “Acquisition History”: Microsoft