Your Integration Roadmap to the Sage Ecosystem

"We Use Sage." A Guide to What Your Customer Really Means.

In our last post, we explained why Sage is a fragmented federation of acquired products. Now, it’s time to map that federation.

When a customer says, "We use Sage," they could mean a 20-year-old desktop program or a brand-new, multi-tenant cloud platform. Your integration strategy depends entirely on knowing the difference.

This post is the decoder ring. We map out Sage's two distinct portfolios, the established desktop world and the high-growth cloud world, so you can pinpoint exactly what your customer is using.

The Legacy Champions (The Desktop World)

This portfolio is the foundation of Sage's market share. These products are powerful, deeply entrenched, and regionally specific.

• In North America (US & Canada): The market is dominated by Sage 50 US (formerly Peachtree), Sage 50 Canada (formerly Simply Accounting), and Sage 100 US (formerly MAS 90/200).
• In the UK & Ireland: The key product is Sage 50 UK & Ireland (formerly Sage Line 50).
• In Mainland Europe: The fragmentation is even deeper. Key markets have their own "local champion" products:
  • France: Sage 50 (from Ciel) and Sage 100 (from Saari, a separate acquired product from Ciel).
  • Germany: Sage 50 and Sage 100 (distinct German products).
  • Spain: Sage 50 (from Contaplus) and Sage 200 (from the Logic Class line, later marketed as Murano).

The integration challenge for this portfolio is significant. These are distinct codebases that often lack modern, server-side APIs.

The Modern Growth Engine (Mapping the Cloud Portfolio)

This is where Sage's strategic focus and investment sit. For SaaS companies, this is the future-proofed opportunity. But "cloud" is not one platform. The cloud portfolio has its own fragmentation.

North American-Focused Cloud

• Accounting (Mid-Market): Sage Intacct, the flagship API-first platform, now expanding globally.
• HR (Mid-Market): Criterion, acquired October 2025 to bolster US HCM and payroll, now being rebranded to Sage HCM.

European-Focused Cloud

• Accounting (Pan-European SMB): Sage Active, the cloud-native product for France, Germany, and Spain.
• Accounting (UK Mid-Market): Sage 200 UK, notable for a well-supported REST API that (unusually for Sage) does not require Developer Programme membership to build against.
• The Legacy Exception: Sage 100 Germany. Unlike its API-hostile namesakes in the US and France, the German Sage 100 exposes an OData API, though access is tied to a specific licensing tier.

The Global Cloud Portfolio (Products for All Markets)

• Accounting (Small-Biz): Sage Business Cloud Accounting (formerly Sage One). A competitor to Xero. Note that the Sage Accounting API covers the UK, Ireland, and Canada; the South African product with the same name runs on a separate codebase and API.
• HR (Global SMB): Sage HR (formerly CakeHR).
• HR (Global Mid-Market): Sage People (formerly Fairsail). A HCM built on the Salesforce platform.
• ERP (Global Mid-Market): Sage 300 (formerly Accpac).
• ERP (Global Enterprise): Sage X3 (originally the Adonix ERP, acquired in 2005). A customizable ERP for manufacturing and distribution.
• CRM (Global): Sage Sales Management (formerly ForceManager).

Your Integration Strategy Is Not for "Sage"

The Sage ecosystem is really two complex ecosystems. The legacy desktop world is fragmented by region. The cloud world, where Sage is focusing its future, is fragmented by region, market segment, and technology.

The cloud portfolio alone is a mix of a dozen distinct platforms. Knowing this map is the first step. The next is understanding the technical implications. In our final post, we get into the API playbook and show you why integrating with Sage Intacct is a completely different project than integrating with Sage Active or Sage 100 France.