Move Data Between OMN2/3 and OMN4
The OMN2/3 and OMN4 bridge helps you move route, track, and waypoint data while you are moving to OMN4 at your own pace.
Use it when one device is ready for OMN4 but another device still needs OMN2 or OMN3. The bridge is a deliberate import and export workflow. It is not live sync between OMN2/3 and OMN4.
Before You Start
- sign in to OMN4 with the email address you used for OMN2 or OMN3
- use a live internet connection
- let OMN4 finish its first account and sync setup
- keep OMN2/3 available if you still need to move work back to an older device
This guide is about routes, tracks, and waypoints. Your subscription is handled when you sign in to OMN4; it is not moved by these bridge steps.
Import From OMN2/3 To OMN4
- Open Routes, Tracks & Waypoints in OMN4.
- Open the main menu for that view.
- Choose Import Legacy Data.
- Select the OMN2/3 items you want to bring into OMN4.
- Continue with the import and wait for it to finish.
OMN4 adds the imported items to a new folder named Legacy Imports followed by the import date and time. Open that folder to review the imported routes, tracks, waypoints, and folders.
If you import again later, OMN4 creates another new Legacy Imports folder. It does not update the earlier import.
If Import Legacy Data Is Missing
Import Legacy Data only appears when OMN4 recognises your account as an earlier OMN2/3 account.
If you do not see it:
- Check that you signed in with the email address you used for OMN2 or OMN3.
- Let the first OMN4 account setup and sync finish.
- Sign out and sign back in with the original OMN2/3 email address if needed.
- Contact support if the option still does not appear.
Support will need the email address you used for OMN2/3 and the email address currently signed in to OMN4.
Save OMN4 Data Back To OMN2/3
Use Legacy Export when you still need a route, track, waypoint, or folder from OMN4 on a device that is staying on OMN2 or OMN3.
- Open Routes, Tracks & Waypoints in OMN4.
- Select the item or folder you want to send back.
- Open its menu.
- Choose Legacy Export.
- Choose an existing legacy folder or create a new one.
- Export the data.
OMN4 sends a new file to the selected legacy folder. If a file with the same name already exists, OMN4 chooses a unique name.
If OMN4 says there is no AZMaps login linked, sign in with the email address you used for OMN2 or OMN3, or contact support.
Avoid Duplicate Versions
Treat each import or export as a new copy of the data.
- Each import from OMN2/3 creates a new Legacy Imports folder in OMN4.
- Each export from OMN4 creates a new file in OMN2/3.
- OMN4 does not overwrite the original OMN2/3 file.
- OMN4 does not merge changes made separately in both apps.
If you edit the same route in OMN4 and OMN2/3, you now have two separate versions. Pick one version to keep working on, or rename the copies so you can tell them apart.
What Moves
The bridge is for route, track, and waypoint library data:
- routes
- tracks and tracklogs
- waypoints
- names
- legacy folder paths when importing into OMN4
- supported colours, line styles, icons, and map-text settings where OMN4 can translate them
What Does Not Move
The bridge does not move every part of either app.
- offline map downloads
- temporary map and search caches
- OMN4 app settings
- OMN4 cloud sync state
- unsupported visual styling
- very large exports, if the compressed file is over 8 MB
Large exports may need to be split into smaller folders or items.
Folder Structure
Import and export are not perfectly symmetrical.
When you import from OMN2/3, OMN4 can rebuild the legacy folder path under the new Legacy Imports folder.
When you export from OMN4 back to OMN2/3, nested OMN4 folders are flattened into one file in one legacy folder. OMN2/3 does not have the same nested folder structure as OMN4.