A CMMS implementation is ready to expand when a technician can complete a real task and the next person can retrieve useful evidence. Importing thousands of assets is an intermediate step, not the outcome.
Define a bounded first workflow
Choose one site, a small set of important assets and one recurring task. Name the planner, technician and reviewer. Write the evidence the reviewer needs: asset identity, procedure, observations, time, parts where relevant and verification. Agree what would make the workflow unsuitable before expanding it.
Prepare the asset register
Keep a copy of the original export. Choose stable asset codes and site codes; do not use a changing display name as the only identifier. Separate manufacturer, model and serial number. Declare meter units explicitly: hours, kilometres and miles must not be mixed.
In PreventiveHQ, download the current CSV template from the asset import screen. Use that template’s headers and allowed values rather than assuming another vendor’s export has the same schema. Start with a small batch that includes representative meters, locations and optional fields.
Preview and correct before committing
Upload the CSV for preview. Review row-level errors and the proposed records. Correct duplicate codes, unknown sites, invalid statuses and malformed values in the source file, then preview again. Keep the rejected file and corrected version so the migration owner can explain what changed.
Do not blindly retry a commit after a timeout. Check the asset register and import result first. Verify a sample of created records against the original file, including meters and site ownership. Asset import does not imply automatic import of every vendor’s work-order history, attachments or custom fields.
Install the first maintenance task
Open the template library, adapt a relevant checklist and install it in the workspace. Select the real asset, first due date and repeat interval only after the responsible person has reviewed the procedure. An optional recurring plan creates future work; it does not establish that the interval is technically appropriate for the equipment.
Use the scheduling workflow to test calendar or meter triggers. For a meter-based plan, verify the units and the next service threshold before entering a new reading.
Validate execution and recovery
Have the technician find the job using their actual role and device. Capture the required responses and complete the work with actual time and verification. Correct an intentional noncritical data-entry mistake through the supported workflow. Check that unauthorized roles cannot change the plan or see another organization’s records.
If a required field forces the technician to invent information, correct the task design. An inspection with no defect should not require an invented failure cause. If a real defect is found, create and assign corrective work so it remains visible.
Review the pilot and expand deliberately
At the next operating cycle, verify that due work appeared, the team returned to the system and the reviewer used the history. Record support time and unresolved blockers. Expand the asset set only after those checks pass.
Before a purchase decision, inspect pricing, user and site capacity, security information and CSV export. Keep an owner for data corrections, procedure changes and access removal. The implementation remains an operating responsibility after the first import.
Prepared by the PreventiveHQ product team. Revised 6 September 2026. Worked examples are illustrative, not customer results.