Moving from OMN2/3

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.

After your routes and waypoints have synced, OMN4 may offer to import your existing OMN2/3 data if your OMN4 library is empty and legacy data is available. Accepting opens the import workflow below; it does not import everything without a preview. The offer is remembered on that device. If you decline, you can still choose Import Legacy Data later.

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.
Check Import to: for the exact new Legacy Imports folder name.
Check the Activity OMN4 should use when a selected route or track has an unknown or missing Activity. Your account default is already selected; choose another Activity if needed.
Continue with the import and wait for it to finish.

A legacy import runs as a background job, and only one import can run at a time. Let OMN4 finish syncing before you start an import, and sync again once it has finished. If an import is already running, wait for it to finish before starting another.

OMN4 keeps recognised Activities. The selected fallback is used only for items that cannot be matched, and is retained if the background job retries or resumes.

OMN2/3 line styles are not carried across. Imported routes and tracks look the way their OMN4 Activity says, so to change how they look, change the Activity's settings or give the imported items a different Activity. See Activities Explained.

A route's point symbol is the exception. The symbol a route's points shared in OMN2/3, or the fact that they were hidden, becomes the Route's own Symbol (or No symbol). Change or reset it in the Route's Properties.

A GPX file you exported from OMN2 or OMN3 and import with Import is different: it brings across its line colour and width, distance markers, direction arrows, hidden route point symbols, symbol size and map labels where OMN4 has an equivalent. These become the Route's own values (marked * in Properties), so they stay when you change the Activity's settings. Use Reset appearance in the Route's Properties to make it follow its Activity. See GPX Import and Export.

Why Are My Imported Routes Green?

OMN4 starts every account on Walking, and Walking's routes are green. Items that OMN4 could not match to an Activity are given the fallback Activity chosen at import, which is usually Walking.

To check one imported route, open its Properties and look at its Activity. To restyle the whole import in one go, see Restyle Your Imported Routes.

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 OMN 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.

Import An Older Anquet ADF File

If your data is in an .adf file from Anquet software that predates OMN2/3, use Import to select that file. On desktop, Import Folder can also include ADF files. This reads files you already have, rather than retrieving your account's legacy cloud data. See Import Older Anquet ADF Files for the steps and limitations.

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 you do not pick an existing legacy folder, OMN4 uses a folder called OMN4 Export.

If OMN4 says legacy import or export is unavailable, 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
a route's shared point symbol, or the fact that its symbols were hidden

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
OMN2/3 line styles (colour, width, pattern); imported items use their Activity's appearance
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.