Hippo Migration FAQs

Many-to-one Work Orders 

In Hippo there was allowance for many assets to be included on a single work order. This did not allow for any distinct reporting of what occurred on any of the individual assets within that work order. Howerver, in Eptura Asset, there is a required 1-to-1 relationship between assets and work orders. 

With this change, there may be some PMs which need to be updated by the customer. We recommend watching the following webinar starting at the 15:30 mark Q2 2025 Eptura Asset Onboarding Masterclass (26th June) which walks through the process of de-duping the PMs to set up singular facility-wide PMs.

Character Limitations 

In Eptura Asset, there are character limits in certain fields, such as Purpose and Maintenance Plan Name. These fields have a reduced character limit. The Work Order History export from Hippo will have the full name, but you will need to keep within the character limits.

Inactivation vs. Deletion

Eptura Asset is set up to inactivate data that is no longer relevant or if there are Assets that have been disposed of by your company. Inactivating that data is a best practice compared to deletion, so the delete function is not available to ANY users of Eptura Asset. 

If data needs to be cleared out, this can be done by our Professional Services team.

Custom Fields (Column Chooser)

Any information that did not transfer over directly one-to-one from Hippo has been created as a Custom Field, which can be accessed on the main grid via the Column Chooser and Saved Views.

Locations and Vehicles are now Assets 

You no longer have separate grids for Vehicles, Equipment, and Locations, these are now found under the Asset module inside of Eptura Asset. This allows for more comprehensive reporting and looks at each of these assets as being a distinct unit with its own maintenance record.

Leading Numbers on Assets and Parts 

These were added to make sure every Asset and Part was unique, which is a requirement in Eptura Asset. 

There was a script that was run on all customer databases to remove the leading numbers where possible. If there is more than one of the same records (e.g. Oil Filter) it will remove the leading numbers from the first record and leave the numbers on the other records. 

The resolution for these duplicate records is creating Unique IDs for all the duplicate records, which will allow the removal of the leading numbers. This is a manual process that needs to be completed by the customer due to lack of restrictions from Hippo.