onCMMS and your ERP

Today the integration between onCMMS and your other systems is done with CSV files: assets come in from your ERP or spreadsheet, and work orders, time and the asset inventory go out whenever you need them. This page explains that exchange, why maintenance needs less integration than it seems, and what we are building next.

What you can do today

  • Load your assets from the ERP: if you can get an asset list out of it, it imports from CSV with a row-by-row report, creating missing sites, locations and categories on the way.
  • Load your work order history: a second CSV template brings past work orders in, so the asset history does not start from zero.
  • Push work out to the ERP, BI or a spreadsheet: work orders, time entries and the asset inventory export to CSV with the filters you applied (dates, site) for accounting, a dashboard or whoever tracks costs.
  • Take everything, whenever: the complete export of a company is a ZIP with every table, the CSV lists and the files. Your data is yours, in reusable formats.

To be clear: that exchange is manual, when it suits you. There are no connectors that keep two systems in sync on their own and no public API yet. Both are on the technical roadmap; the section below says where they stand. If automatic synchronization is a must from day one, write to us and we will tell you plainly whether we fit today.

Why you need less integration than it seems

An ERP runs the company: purchasing, invoicing, stock, payroll. A CMMS runs maintenance: what broke, who fixes it, which inspections are due and what history each asset has. The two worlds touch in very few places, and almost always in one direction.

Where they touchWhat happens in practice
The asset inventoryLoaded once from the ERP by CSV, then it lives in the CMMS, which is where it changes: photos, QR codes, location, history
Maintenance costLeaves the CMMS as CSV (hours per asset and period, with the hourly rate frozen on each entry) and enters the ERP at closing time, not every day
Spare partsA real overlap, but onCMMS does not run a valued stock: consumption is noted on the work order and purchasing stays in the ERP
Contractor invoicesEntirely in the ERP. The CMMS keeps what was done and by whom, not what the invoice cost

That is why most companies run the two systems side by side and do not miss a link: the person who reports a problem from the phone never opens the ERP, and the person closing the books does not need to see a work order.

A monthly export, in practice

  1. On the first working day, open Work orders, filter last month and the site you need, and export to CSV.
  2. Do the same in Reports for time and labor cost per asset.
  3. Import the files into your ERP, your BI tool or a spreadsheet. Column headers are stable, so a saved import mapping keeps working month after month.

People do this into Odoo, Sage, QuickBooks, NetSuite, Business Central and plain Excel or Google Sheets. We name them as destinations, not as partners: there is no connector behind any of them.

What we are building

  1. A public API, the foundation for everything else: without it no integration with anyone is possible. It is the next serious technical step on the roadmap, not an idea.
  2. With the API, anyone can build their own bridge: your IT person, your ERP consultant or an automation tool, without waiting for us to write a connector.
  3. Specific connectors, afterwards and on demand: maintaining one per ERP is expensive (each with its versions, its cloud and its on-premise flavour), so we will build the ones customers actually ask for.

We do not publish dates because we do not promise them. What we do is count how many people ask for each system; that decides the order.

Ask for your connector

Tell us which ERP or BI tool you use and how you work. That is how we learn whether you need a real connector or the CSV exchange already covers you.

Tell us which system you use

Can I bring my assets from the ERP into onCMMS today?

Yes, and it is the normal way to start: export the list from the ERP, fit it to the CSV template and import it. The import report tells you row by row what went in and what failed. If the file resists, write to us and we look at it with you.

Do you have an API?

Not a public one yet. It is the next thing we want to build, precisely because it opens every integration at once instead of one at a time.

Will you build a connector for my ERP?

Maybe, and it depends largely on how many people ask. We do not promise any with a date; we prefer to promise less and deliver. If your case is large and urgent, the Enterprise plan exists precisely to talk about custom development.

What if my ERP already has a maintenance module?

Then try it first: if it works for you, you do not need another tool. People usually come here because that module is too rigid, needs a license for every technician, or cannot be used one-handed from a phone on a shop floor.

Keep reading

Try it before you decide

The demo is open without sign-up, and your company account takes 30 seconds: check whether CSV covers you before waiting for a connector.

Start free