Legacy CMMS automation for systems with no API

Legacy CMMS automation means adding automation around an old maintenance system instead of replacing it. The CMMS keeps the asset history and the work orders. The automation handles the typing, copying, checking and reporting that people do around it every day.

Most legacy systems share one problem: they were built before APIs were normal. Some run on a server down the hall. Some are hosted versions nobody has upgraded in years. That does not block automation. It only changes how data gets in and out.

I start with the doors the system already has: scheduled exports, report emails, import templates, the database it writes to, and the screens people click through. One of those is almost always good enough.

1. Scheduled exports. Most legacy CMMS tools can export work orders, assets and PM schedules to CSV or Excel on a schedule. The automation picks up each file, cleans it, and feeds alerts, reports and dashboards. It only reads, so it is the safest place to start.
2. Import templates. Many older systems accept bulk imports. The automation drafts clean rows from emails and forms, a coordinator checks them, and one import replaces an afternoon of typing.
3. Read-only database access. When the CMMS runs on your own server, its data usually sits in a standard SQL database. With IT's approval, a read-only connection gives live status without touching the application.
4. Screen automation. When nothing else works, a bot can click through the same screens a coordinator uses. It is the most fragile option, so I keep it to a few high-volume steps and log every run.

• Work orders are copied by hand from email and spreadsheets into the CMMS.
• The vendor's API is missing, costs extra, or needs a version you cannot upgrade to.
• Reports need an export, a spreadsheet clean-up and the one person who knows which columns to trust.
• Only one or two people really know how the system works.

• Read inbound requests and draft CMMS-ready work order rows for review.
• Turn scheduled exports into status alerts and weekly reports.
• Push vendor and technician updates back into the record through imports or screen steps.
• Flag records with missing assets, locations or close-out notes before month end.

CMMS, ERP, Excel, SharePoint, email, vendor portals.

A replacement means migrating years of asset history, rebuilding every report, retraining technicians and reconnecting vendors. The new system still needs the same intake and reporting work around it. Automating around the old system first is cheaper, faster and easy to undo. If you replace it later, the automation moves with you, because it was built around your process, not the vendor's screens.

Some steps should keep a person in them. I build those as review points: the automation prepares the decision and a person makes it.

• Spend approvals over your limit.
• Vendor choice on unusual jobs.
• Changes to safety and compliance records.

• Before a CMMS replacement, automate these 5 handoffs: The five handoffs to fix first, whichever system you keep.
• Power Automate Desktop limitations for facilities teams: Where screen automation helps on old systems, and where it breaks.
• CMMS integration services: For when your CMMS does have an API and needs to talk to ERP or accounting.

If your CMMS vendor already sells the integration you need at a fair price, use it. If the system is weeks away from being switched off, wait and automate the new one. This pays off when the old system is staying for at least another year and people retype data into it every day.