Overview
If equipment was created as a Location but should belong under another Location as an Asset, ask Mobaro to review a conversion. For example, a Location called “Pump 1” could become an Asset under “Plant Room”.
Only Mobaro administrators can perform this conversion. An organization Super User or a User with Assets › Administrate cannot perform it themselves.
At a glance |
|
Who can do this | Your organization prepares the request; Mobaro administrators perform the conversion. |
Where | Help in the Backend, or Mobaro Support |
Works on | Backend (web) |
Availability | Contact your CSM |
🛑 Critical: Conversion cannot be undone. The original Location is archived by the conversion and disappears from normal Location lists. Agree the destination and review the effects before Mobaro proceeds.
Check that conversion fits
Use conversion when the existing Location and its history should become an Asset under another Location. The conversion creates a new Asset; it does not merge the Location into an existing Asset.
If you only need to move an existing Asset, follow Linking Assets to Locations. If you only need to change how equipment inspections are scheduled, see Move equipment checks to Asset-driven Schedules. These are separate tasks.
Prepare and send the request
1. Identify the source and destination
Provide the organization name, the exact Location to convert, and the Location that should become its parent. Include links or Mobaro IDs where available, especially if names are repeated.
The parent must be a different, existing Location in the same organization. A Site, Area, Location Group, or existing Asset cannot be selected as the conversion destination.
2. Describe the work that depends on it
List important Schedules, active or unfinished Checklists, and Assignments. Include work that reaches the Location through a Location Group.
Identify the teams that must retain access at the destination, including Schedule assignees.
Mention scanner labels, Location Properties, Notification Rules, Dashboard filters, integrations, and any RideOps use.
Tell Support about active Downtime. Open or blocking Downtimes prevent conversion; resolve them through your normal operating process before conversion is attempted.
3. Contact Mobaro Support
Click Help in the Backend, or email [email protected]. You can also coordinate the request with your Customer Success Manager. See Contact Information for the available channels.
Use this request template:
Information | Include |
Organization | Name and link or ID, if available. |
Location to convert | Exact name and link or ID. |
Parent Location | Exact name and link or ID in the same organization. |
Reason | Why this should become an Asset. State whether an Asset already exists for the same equipment. |
Dependencies | Schedules, unfinished work, teams, labels, reports, integrations, and operational use. |
Preferred timing | Date, time zone, and any operating restrictions. |
Review contact | The person in your organization who will review the proposed change and check the outcome. |
4. Agree the review and timing
Ask Mobaro to review the Schedule impact with you before converting. The preview identifies directly affected Schedules and active occurrences. It does not replace a review of access, Location Group targeting, labels, or reporting.
Agree how any affected work will continue and when devices should sync. Submit pending work where possible. Requesting a conversion does not schedule it automatically or confirm a completion date.
Check the completed conversion
Find the new Asset under the agreed parent Location and check its existing child Assets.
Test access with a representative User from each affected team.
Check current and upcoming work, Schedule assignees, and Assignments.
Find representative historical Results using the destination Location and relevant Asset filters.
Test scanner labels and Checklist logic. Review Notification Rules, Dashboard filters, and integrations.
If something is missing, reply to the same Support request with the affected item, User, and example. Avoid creating replacement records until the change has been checked.
Best practices
Use one reviewed source-to-destination list for multiple conversion requests.
Choose timing around active work and device synchronization.
Keep the agreed mapping and conversion date for later reporting.
Frequently asked questions
Can I get a Role permission to convert a Location myself?
No. Location-to-Asset conversion is restricted to Mobaro administrators. Giving User Assets › Administrate or Super User access does not enable conversion.
Can I convert a Location into an Asset in another organization?
No. The source and parent Locations must belong to the same organization. Ask Support to review your wider restructuring goal if it involves multiple organizations.
Can I use conversion to combine a Location with an existing Asset?
No. Conversion creates a new Asset. Tell Support about an existing Asset for the same equipment before requesting conversion, so the proposed structure does not introduce a duplicate.