Public REST API
The standard route for a new integration. Lets you read and write to the CMMS from your own development, and it’s documented at developers.gmao.cloud.
Integrations
Closed work shouldn’t have to be typed twice
The CMMS knows what was done, how many hours it took and what materials were used. The ERP needs exactly that to invoice. Having a person copy that data across by hand is the most expensive waste in a maintenance operation.
Integrating isn’t dumping data
An integration that just copies records from one system to another ends up creating more work than it saves: duplicates, fields that don’t line up, manual corrections on both sides. What needs deciding before connecting anything is which system owns which data. The ERP owns customers, items and rates; the CMMS owns assets, interventions and consumption. Once it’s clear who owns what, the integration is a technical matter. Before that, it’s a source of problems.
Who GMAO CLOUD talks to
The systems with a connector running today in real installations, and an open route for everything else. Select one to see its page: what travels is not the same in every one.
Prisma
BP
REST API, SOAP, SQL, CSV and FTP
GMAO CLOUD with GMAO CLOUD
We talk to ourselves. If your customer and your supplier both use GMAO CLOUD, each works in their own and the two understand each other: the customer sends its supplier the addresses, facilities, assets, incidents, work orders and documents that concern it, and the supplier sends back the status of each job without leaving its own system. Nobody logs into the other’s CMMS or types anything twice.
Trademarks of their respective owners, used only to indicate compatibility. They do not imply any commercial relationship.
And if your system isn’t on the list
Which is the most common case, because management software out there is so fragmented.
SOAP
For systems that still speak that language, and there are quite a few in industrial environments.
SQL connection
Direct read/write against the other system’s database, when it exposes no interface of its own.
CSV and FTP
File exchange is still the most robust option when the two systems can’t talk in real time.
Shall we look at it with your way of working?
Leave your details and we will get in touch to see whether we fit. No commitment, no lock-in period.
What travels and where
Not every connector does the same thing, and it’s worth knowing that before buying. The most common pattern is that closed work orders go out to the ERP with their hours and materials to become an invoice, and that customers, addresses and items come in from the ERP so you don’t maintain two masters. But some connectors only do one of the two things: Sage X3, for example, imports customers, addresses and items and doesn’t export work orders. That’s why the useful question isn’t "do you integrate with X?" but "what data needs to travel, in which direction and how often?" — and that’s the first thing we clarify in the demo.
How it gets set up
A badly planned integration costs more than doing it by hand. These are the steps that prevent that.
Decide who owns what
Before writing a single line: which data is the source of truth in each system, and what happens when both change.
Map the master data
Customers, addresses and items have to be recognizable across systems. That’s the real work of an integration.
Test against real data
With a narrow subset, watching what lands on the other side before opening the tap all the way.
Keep a trail of what was sent
What was sent, when, and with what result. Without a log, a sync failure only surfaces once an invoice is missing.
Frequently asked questions
What happens if the ERP is down when a work order needs to be sent?
That’s why it matters to keep a trail of every send attempt and its outcome. What couldn’t be sent has to be visible and retriable, because a silent failure is the worst possible scenario: it surfaces weeks later, when an invoice is missing and nobody remembers what happened that day.
Do you integrate with my ERP?
There are connectors in production with Business Central and Navision, SAP, Sage X3, Holded, Factura Directa, QuickBooks, STEL Order, Libra, Golden, Progein, Freematica and Sage 200c, among others. For everything else there’s REST API, SOAP, SQL connection, CSV and FTP, which is how most new cases get solved.
What data travels between the two systems?
The usual pattern is that closed work orders go out to the ERP with hours and materials for invoicing, and that customers, addresses and items come in from the ERP. What exactly travels depends on the connector and on what you decide: not all of them do both things.
Does the integration run in real time?
It depends on the connector and on the system on the other side. Ones that work against an API or a database can run on the spot; ones that exchange files run on cycles. In the demo we decide what fits your operation.
Does GMAO CLOUD replace my ERP?
No, and it shouldn’t. The ERP manages the company and the CMMS manages maintenance. They’re complementary systems, which is why the product integrates instead of trying to replace it.
How long does it take to get an integration working?
What takes the most time isn’t the connection itself, it’s agreeing which data is authoritative in each system and mapping the master data. A standard integration with an existing connector is much faster than a custom one, which is why it’s worth checking first whether yours is on the list.
Tell us what you work with
In the demo we look at your ERP, what data needs to travel and in which direction, before talking about anything technical.