Overview
Converting a Location to an Asset changes its structure, access context, work, and reporting. Mobaro administrators perform the conversion after you agree an existing parent Location in the same organization.
Use this guide to review the effects before conversion and check the outcome afterward. Conversion is different from moving an existing Asset or changing a Schedule target.
At a glance |
|
Who can do this | Your organization reviews the effects; Mobaro administrators perform the conversion. |
Where | Locations, Assets, and your Mobaro Support request |
Works on | Backend (web) |
Availability | Contact your CSM |
🛑 Critical: Conversion cannot be undone. Do not assume every Schedule will continue on the new Asset or that historical reports will keep the original Location attribution.
What is moved or retained
Item | What happens |
New Asset | A new Asset is created under the chosen parent Location. It copies the source Location’s Name, External ID, and stored Custom Scanner Code. |
Original Location | It is archived by conversion. It no longer appears in normal Location lists and cannot be edited there. This is not a general-purpose Location archive feature. |
Existing Assets | Assets at the source move to the parent Location. Top-level Assets become children of the new Asset; their existing nested structure is retained. |
Results | Completed, resumable, and external Results recorded against the source are reassigned to the parent Location. Results without an Asset receive the new Asset; existing Asset links are retained. |
Assignments | Assignments targeting the source are reassigned to the parent Location. Those without an Asset receive the new Asset; existing Asset links are retained. Both open and closed Assignments are included. |
Activity history | The new Asset records its conversion. Moved Assets record Location and, where applicable, parent changes. |
Historical Results are retained, but their Location attribution changes. Review saved filters and reports that use the old Location or its Location Groups. Filter by the new Asset for work newly attached to it, and by the relevant child Assets for work that already had an Asset link.
How Schedules are affected
Mobaro previews directly affected Schedules and active scheduled occurrences before conversion. Review the three outcomes:
Before conversion | Outcome |
The source is the only entry in Targets, and Asset scheduling is enabled. | The source is removed and the new Asset is attached. |
The source appears alongside other Targets. | The source is removed. The conversion does not automatically add the new Asset for that Schedule. Review how its work should continue. |
The source is the only Target, Asset scheduling is unavailable, and there are no existing Asset targets. | The Schedule is left targeting nothing. Agree replacement targeting before relying on it for work. |
Existing Asset targets are retained. The source is also removed from explicit exclusions. Active occurrences whose end time is still in the future are updated, including occurrences already in progress. Ended occurrences are not retargeted by this conversion step.
Schedules that reach the source through a Location Group need a separate review. The source is removed from Location Groups, and those Schedules are not automatically changed to target the new Asset. They are not listed merely because of that indirect relationship in the direct-target preview.
Automatic Asset attachment depends on the organization’s Scheduling functionality for assets access. Conversion does not enable it. Ask your CSM and use Asset-driven Assignments and Schedules to check targeting and assignees.
Access and configuration checks
User access: the new Asset and moved Assets use the parent Location’s access. Source Location memberships are not copied to the parent. Check the affected teams and assignees; assignment alone does not grant Location access.
Location Groups: the source is removed; the destination is not automatically added to the same groups. Check group-based access, work, and reporting.
Notification Rules: direct source targets are removed from Activity Summary and Work Forecast rules. The destination is not automatically substituted. Review recipients and rule scope.
Location-specific settings: conversion does not copy Location Properties, opening hours, geographic settings, or RideOps configuration onto the new Asset. Review the destination’s setup. Asset Checklists use their Location’s Properties.
Reports and integrations: the Asset has a new Mobaro ID. External ID is copied, but this does not automatically remap external systems, saved Location filters, or links.
Scanner labels and operational history
A stored Custom Scanner Code is copied. A default scanner code based on the old Location’s Mobaro ID is not automatically changed into the new Asset’s ID. Test existing labels after devices sync; do not assume every printed code will keep working. Check Scanner Question validation as well as navigation. See scanner-code troubleshooting.
The converted Asset has a View Operational Log action in the Backend Assets list. It reads historical operations from the original Location. This does not transfer the source’s RideOps configuration or make the new Asset operational automatically.
Open or blocking Downtimes prevent conversion. Ask Mobaro to review RideOps and operational requirements before converting an operational Location; historical log access is not a replacement for the future operating setup.
Best practices
Agree the Schedule changes, access, and parent Location before conversion.
Sync devices and submit pending work where possible at the agreed changeover. Refresh devices afterward and verify available work.
Check representative Results, Assignments, labels, and reports after conversion. Record the source, new Asset, parent Location, and date.
Frequently asked questions
I cannot find historical Results under the old Location. Were they deleted?
Conversion reassigns those Results to the parent Location. Search there and use the appropriate Asset filter. Results with an existing Asset keep that link; Results without one use the new Asset. Contact Support with an example if a Result is still missing.
The new Asset is visible to me but not my team. What should I check?
Check the team’s access to the parent Location. Membership at the old Location is not copied. Also check Schedule assignees and their eligibility to complete work at the destination.
Can I leave unfinished work on offline devices during conversion?
Coordinate it with Support. The backend includes handling for late Result submissions referencing a converted Location, but that is not a guarantee for every device or workflow. Sync and submit pending work where possible, then verify remaining work after conversion.
The preview says no Schedules are affected. Is there nothing else to check?
No. The preview focuses on direct source targets in Schedules and active occurrences. Still review Location Group targeting, access, labels, Notification Rules, integrations, and reporting.