














































Hippo CMMS is a maintenance management system founded in Winnipeg, Canada, in 2004 for small and mid-sized organizations. iOFFICE acquired it in November 2019, and it is now part of Eptura, which has carried its core functionality into Eptura Asset and no longer sells Hippo as a standalone product, while existing customers still sign in to their environments. Teams use Hippo for work orders, preventive maintenance schedules, equipment records with manuals and warranties, parts inventory with barcode scanning, inspection logs, vendors and invoicing. A predictive maintenance product reads assets and locations through Makini's Unified API, so each monitored unit maps to the equipment record in Hippo. When it detects a developing fault, it can create a work order where the connection permits writes, so the job lands in the technicians' queue. Inventory optimization tools compare parts stock with open purchase orders and vendors, where the connection exposes them, and OEM vendors review the equipment they supplied to plan spare parts and service visits. A Hippo user signs in through Makini Link, embedded in the vendor's product or sent as a magic link, so credentials never pass through the vendor's application. Data then syncs on an interval set by the Makini plan, not in real time. What a connection exposes depends on the customer's setup and the connecting account's permissions, so agree on that user with the customer's administrator. Because Eptura is moving Hippo customers to Eptura Asset, confirm which system each customer uses and plan to reconnect after their migration.
Have any questions? We’re here to help You
Hippo CMMS is being replaced by Eptura Asset: Eptura, which now owns Hippo, says Hippo CMMS is evolving into Eptura Asset. Eptura Asset is the former ManagerPlus, renamed in 2023, and combines CMMS with enterprise asset management. Existing Hippo customers can still sign in at v6.hippocmms.com, so your customers may run either system for some time.
Hippo CMMS support now runs through Eptura's customer support portal, and the Hippo CMMS section of the Eptura Knowledge Center points users to the Eptura Asset Knowledge Center. Eptura's Hippo page still describes work orders with repair history, preventive maintenance, parts with schematics, manuals and warranties, barcode scanning, inspection logs, vendors and invoicing for current users.
Hippo CMMS has no API reference on Eptura's public Hippo pages, so vendors usually reach Hippo data through a connector. With Makini, your product calls one REST API and Makini handles the Hippo side. Makini's Hippo page lists work orders, assets, purchase orders, stock, vendors, accounts, locations, sites and organizations among its models, where the connection exposes them.
Hippo CMMS keeps repair history on each equipment record, so closed work orders give a failure record per unit. A reliability product can count repeat jobs per asset and location, and an OEM vendor can spot supplied units that need frequent service. Inspection logs add context where the connection exposes them, so check a first sync before building reports on them.
A Hippo CMMS connection does not carry over to Eptura Asset; Makini lists Eptura Asset as a separate integration, so the customer reconnects through Makini Link. Your product keeps reading the same unified models, but record IDs will likely differ, so rematch assets by name, barcode or location. Keep write logic built only for Hippo simple, since customers are moving off it.
Makini's /sync-status endpoint returns the state of each Hippo CMMS connection: last successful sync, status (in progress, completed or failed), error messages and next scheduled sync. Workflow runs are logged, and the Makini dashboard shows sync status across connections. When a Hippo sync fails, check whether the user's password changed or the customer has already moved to Eptura Asset.
