Sage 200 (formerly Sage Murano)

Sage 200 is the name now used for the ERP that for years was sold as Sage Murano: the vendor completed the rebrand and no longer distributes it under the previous name, although many companies in Spain still search for it by that name. We keep supporting that installed base and migrating it to the current version.

If your company implemented Sage Murano years ago, moving to Sage 200 does not mean changing product: it is a version upgrade. Even so, it is worth reviewing configuration, custom developments and existing integrations beforehand so you don't carry obsolete settings into the new environment.

Sage X3 covers the next level: mid-sized companies with several entities, multi-currency, multi-site. We recommend it when the client has already outgrown the functional ceiling of Sage 200 and needs more complex financial orchestration.

Sage 200 covers most SMEs: a single company or a few, with the functional depth it already has today. Sage X3 comes into play when there are several consolidating entities, operations across several sites or countries, or a transaction volume that starts to hit the technical limit of Sage 200. It isn't a question of turnover but of organisational complexity: we have migrated mid-sized companies with a single entity to X3 because they needed multi-site batch traceability, and kept groups with several entities on Sage 200 because their operation stayed simple. We assess it case by case during functional analysis, before recommending anything.

The full comparison and the modules of Sage X3 are on its own page. And if you're coming from Sage 50 and have outgrown it, that page also explains when it makes sense to move up to Sage 200.

Sage 200 and Sage X3 already offer a module or update for Verifactu (RD 1007/2023, with the technical specifications of Orden HAC/1177/2024), with an adaptation deadline before 1 January 2027 for companies subject to Corporate Income Tax and before 1 July 2027 for the rest. That the module exists doesn't mean it is properly configured for your company: we review invoice series, transaction types, the cryptographic chain and the connection to the AEAT.

For mandatory B2B e-invoicing (Ley 18/2022, developed by RD 238/2026), the exact date still depends on a ministerial order that hasn't been published, but it's worth having the technical integration with the EN 16931 format ready before the deadline arrives. We coordinate this adaptation with the Verifactu and electronic invoicing page, and you can calculate your exact deadline with the Verifactu checker.

Sage 200 doesn't operate in isolation. We integrate it with CRM (HubSpot, Salesforce or Dynamics) so the sales pipeline and invoicing share the same customer data; with Power BI and Qlik for dashboards over financial and operational data without exporting to Excel; with Microsoft 365 so Teams, Outlook and SharePoint talk to the ERP; and with online banking for automatic reconciliation of payments and collections. When standard integration doesn't cover a specific process, we solve it with ERP + operational copilot: agents that read and write in Sage 200 for repetitive tasks.

Support doesn't end at go-live. We maintain Sage 200 and Sage X3 with fortnightly enhancement sprints, a direct channel for incidents — without going through the vendor's generic support — and a review of the configuration whenever tax or labour rules change. If your current implementation was done by another provider, we start by auditing the configuration before touching anything: we don't migrate based on assumptions.