Integrations: connect Maintmaster to your ERP

Which systems

Works with the systems you already have

Most integrations connect Maintmaster to an ERP, a warehouse lift, a production system or a reporting tool.

ERP and finance

SAPMicrosoft Dynamics 365IFSInfor M3MonitorVismaJeeves

Warehouse and stores

KardexCompact StoreSupplyPoint

Production

SCADA systemsMachines and sensors

Safety and documents

IAM-FilesComos

Intranet and portals

Your intranetService and supplier portals

Reports

Power BIQlikExcelSQL Server

Sign-in

Microsoft Entra ID

Don't see your system? Every integration runs through a hub: a database, shared files or middleware such as BizTalk. If your system can use one of those, we can connect it.

Ask us about yours

Data flows

What moves where

Every piece of information has one owner. The other system gets a copy, so nobody types it twice.

The most common flows. In the scoping call, you decide which ones you need and which system owns each.

What	Direction	Usually owned by
Articles and suppliers	ERP→Maintmaster	ERP
Stock balances	ERP⇄Maintmaster	ERP
Spare parts used on a job	Maintmaster→ERP	Maintmaster
Purchase requests and orders	Maintmaster⇄ERP	ERP
Costs of maintenance work	Maintmaster→ERP	Maintmaster
Employees	HR system→Maintmaster	HR system
Machine hours, kilometres, produced units	Machine→Maintmaster	Machine or production system
Fault reports	Production system or intranet→Maintmaster	Production system
Jobs and job reports	Maintmaster⇄Other system	Maintmaster
Maintenance data for reports	Maintmaster→Power BI or SQL	Maintmaster

You choose how often each flow runs: every minute, every hour or once a day.

Hosting

Hosted by us, or by you

The integration runs on an integration server. You choose where it lives.

Integration as a service

We host it

An integration Windows server, SQL Server and an SFTP server for secure file transfer.
All in the same Microsoft Azure environment as your Maintmaster.
Nothing to install on your side.

Who looks after it: we do

On your own server

You host it

A light Maintmaster Windows service on a Windows Server in your network: physical, virtual or in a public cloud.
We install, configure and support the integration.
Our specialists need VPN or remote desktop access.

Who looks after it: you run the server (availability, monitoring, patches, antivirus); we support the integration

Just need maintenance data in your reports? With Selection to SQL, you copy the data you choose to your own SQL Server, as often as you like, and use it in Power BI, Qlik or Excel. You set it up yourself.

How a project runs

How an integration project runs

Five steps, from scoping call to go-live. Everything is agreed with you before any work starts.

1
Scoping call
Together we decide what to connect, which way it moves, which system owns it, how often it runs and who is responsible for the data.
2
Agreed scope
One of our integration experts agrees the scope and the plan with you.
3
Set-up
Our integration specialists configure the adapters, with a test and a production version.
4
Test
You test with your own data before anything goes live.
5
Go live
We start the integration and keep an eye on it. Later, you can make many adjustments yourself, in Maintmaster.

Time

How long it takes depends mostly on the ERP side: how quickly your ERP partner can send and receive the agreed data. You get a timeline with your quote, so bring your ERP partner in early.

Good to know

You don't have to wait for the integration to get started. Many customers go live with Maintmaster first, and connect their ERP once the basics are running.

Cost

What it costs

Every integration project is scoped and agreed with one of our integration experts.

No two setups are the same. So we look at your systems and your flows together first, and you know what you get before any work starts.

Talk to an integration expert

For IT

For your IT team

What we need from you, and what we take care of.

Hosted by us: nothing to install. Integration server, SQL Server and SFTP run in the same Azure environment as your Maintmaster.
Hosted by you: a supported Windows Server (physical, virtual or public cloud) and a supported Microsoft SQL Server. SQL Server Express works.
Network: outbound HTTPS (port 443, TLS 1.3 or later) to maintmaster.com and *.maintmaster.com.
Access: VPN or remote desktop for our specialists, with rights to install software, run Windows services, transfer files and create SQL databases.
Exchange: a database, shared files (XML, CSV or text) or your middleware, such as BizTalk.
Independent systems: either side can be updated or replaced without affecting the integration.
Single sign-on: with Microsoft Entra ID. Your own MFA and access policies apply.

Integration Services description Security white paper Single sign-on white paper

PDFs open straight away. No form. All white papers

Customers

How customers use it

MonitorStock in both systems

We had to integrate Monitor that manages inventory, accounting and pretty much everything. The system is integrated but we use Maintmaster as intended.

Anders CarlbergProduction Technician, Svensk Plaståtervinning

Stock balances update in both systems. Spare parts a technician uses are added to the job and updated in Monitor.

Read the story

SAPProduction data system

The ticket then appears directly on the dashboard of the technicians.

Michael RindlerIT administrator, Risse + Wilke

Technicians look up SAP spare parts on site. When an operator reports a fault in the production data system, a ticket is created in Maintmaster automatically.

Read the story

FAQ

Questions we get asked

Something else? Ask an integration specialist.

Do you integrate with SAP?

Yes. We connect Maintmaster to SAP through the same integration hub as any other ERP. The usual flows are spare parts, stock and purchasing, with SAP as the owner of that data. At Risse + Wilke, technicians look up SAP spare parts on site.

Is it a standard connector, or built for us?

Both. We use ready-made adapters, and our integration specialists configure them for your flows and your rules. It is not plug-and-play, and that is on purpose: your ERP is set up in its own way.

Which system is the master?

You decide in the scoping call, one type of data at a time. Usually the ERP owns articles, suppliers, purchasing and costs, and Maintmaster owns jobs, assets and everything technicians record.

What does it cost?

Every integration project is scoped and agreed with one of our integration experts, so you know what you get before any work starts.

How long does it take?

It depends mostly on the ERP side: how quickly your ERP partner can send and receive the agreed data. You get a timeline with your quote.

What do we need from our ERP partner?

Someone who knows your ERP and can make it send and receive the agreed data, through a database, shared files or an API. Plus one contact person for the project.

What happens if we update or change our ERP?

The integration hub keeps the two systems independent, so either side can be updated or replaced without affecting the integration. If you replace your ERP, the new one connects to the same hub.

Can we change the integration ourselves later?

Yes. Our integration specialists do the first set-up. After that, you can make many adjustments yourself, with tools you already know from Maintmaster.

Can we start without an integration?

Yes. Many customers go live with Maintmaster first and add integrations later.

Connect Maintmaster to your ERP. Stop entering everything twice.

Works with the systems you already have

What moves where

Hosted by us, or by you

We host it

You host it

How an integration project runs

Scoping call

Agreed scope

Set-up

Test

Go live

What it costs

For your IT team

How customers use it

Questions we get asked

Tell us what you want to connect

FOLLOW US