From QuickBooks Desktop to IES: A Real-World Transition Story

<span id="hs_cos_wrapper_name" class="hs_cos_wrapper hs_cos_wrapper_meta_field hs_cos_wrapper_type_text" style="" data-hs-cos-general-type="meta_field" data-hs-cos-type="text" >From QuickBooks Desktop to IES: A Real-World Transition Story</span>

For many accounting professionals, QuickBooks Desktop was more than just software—it was the foundation of how they delivered value to clients.

For over 15 years, Jacob Weberman built his practice around it. Supporting mid-sized and large businesses, he relied on Desktop for its stability, deep reporting capabilities, and ability to handle complex workflows.

But as Intuit shifted its focus toward cloud-based solutions, that foundation began to change.


The Turning Point: When Desktop Was No Longer Enough

As development slowed for QuickBooks Desktop and innovation shifted to QuickBooks Online, a gap began to emerge.

While QuickBooks Online improved over time, it still lacked key capabilities many larger clients depended on, including:

  • Advanced reporting
  • Scalable data handling
  • Inventory depth
  • Flexible custom field structures

For firms supporting more complex organizations, this created a difficult choice:

  • Stay on Desktop and risk stagnation
  • Move to ERP and take on added complexity

Exploring ERP—Without Leaving the Ecosystem

Rather than immediately transitioning clients to ERP platforms, Weberman began exploring alternatives while staying aligned with the Intuit ecosystem.

That moment came when Intuit introduced Intuit Enterprise Suite (IES)—a new platform designed to bridge the gap between QuickBooks and full ERP systems.

First Impressions: Early but Directionally Significant

Initial exposure to IES came through early-stage demos. The product was not fully developed—features were incomplete, and some capabilities were still in progress.

However, two features stood out immediately:

  • Multi-entity consolidated reporting
  • Transaction-level dimensions (similar to advanced custom fields)

These capabilities addressed long-standing limitations and positioned IES closer to mid-market ERP functionality.

Even at an early stage, it signaled a shift:
👉 Intuit was beginning to address more complex business needs.


A Real-World Use Case: Where IES Filled the Gap

The turning point came with a long-time client—a publishing company—attempting to move from QuickBooks Desktop to QuickBooks Online.

The migration exposed a critical issue:
👉 Their workflows depended heavily on custom field tracking, which did not translate effectively into QBO.

Instead of forcing a workaround or jumping to ERP, the solution became IES.


Implementation and Expansion

The initial deployment began with:

  • 5 entities
  • A focus on reporting and workflow continuity

After introducing consolidated reporting to leadership, the impact was immediate.

The client expanded from:
👉 5 entities → 17 entities

This validated a key use case:

IES could support organizations that would otherwise move directly to ERP platforms.


Product Maturity Through Real Use

Early adoption also meant encountering limitations:

  • Bugs
  • Incomplete features
  • Permission structure challenges

Rather than abandoning the platform, continued engagement—including direct feedback to Intuit—led to improvements over time.

As updates rolled out:

  • Workflows became more stable
  • Features matured
  • Confidence in the platform increased

Where IES Fits Today

Today, IES is being used across:

  • Multi-entity organizations
  • Professional services firms
  • Industry-specific use cases (early-stage, especially construction)

It continues to evolve, with ongoing development addressing gaps such as inventory functionality.


When IES Makes Sense

IES may be a strong fit for organizations that:

  • Have outgrown QuickBooks Online
  • Need multi-entity visibility and reporting
  • Want to avoid full ERP complexity
  • Prefer to remain within the Intuit ecosystem

Where It May Fall Short

IES may not be the right solution for businesses requiring:

  • Advanced manufacturing or supply chain capabilities
  • Deep inventory management (currently evolving)
  • Full ERP-level operational control

The Bigger Insight

This story highlights a broader shift in the market:

👉 The emergence of “in-between platforms”
Solutions that extend beyond accounting software—but stop short of full ERP complexity.

For firms and clients, this creates a new decision layer:

  • Not just which ERP to choose
  • But whether ERP is needed at all

Final Takeaway

IES is not a replacement for ERP—but for the right use case, it can delay or even eliminate the need to make that jump.

For accounting firms navigating client growth, that distinction matters.

 **This article is an adaptation of an article originally published on Insightful Accountant. 

Jacob Weberman
About the Contributor

Jacob Weberman

Jacob Weberman is the president and founder of On Track Bookkeeping & Accounting Inc., a firm based in Monroe, New York, which offers comprehensive bookkeeping services. Under his leadership, On Track specializes in the setup and maintenance of bookkeeping systems—particularly using QuickBooks—and provides services ranging from initial software configuration to payroll, accounts payable, account reconciliation, and ongoing financial reporting. What began as a solo operation has grown into a full-service team, helping businesses of diverse sizes and industries manage their books and stay on track financially. On Track offers all these valuable services with the highest level of professional expertise, allowing business owners to focus on growth and greater productivity.

Blog Post CTA

Stay Updated on ERP & Business Software

Get the latest insights, comparisons, and resources delivered straight to your inbox.

Join the Conversation

Share your thoughts and comments on this article.