Tips on using your Garmin Zümo XT/XT2
Depending on the route planner (and its associated algorithm for route calculation), settings, and the maps used, routes may deviate from the original plan. Routes from Basecamp usually work well, but when using a different system such as MyRouteApp or downloading a route from someone else, things can sometimes go wrong (which you find out while driving).
To make sure, that doesn't happen to me anymore, I choose to work only with tracks and convert them to routes on the XT/XT2. This way, the chances of the route being different from the track and/or being interpreted differently by the XT/XT2 are minimized. Additionally, you have the option to display both the track and the route during (or before) the ride, making any deviations immediately visible.
The only downside of using a track instead of a route is the fact that you will lose the option to create mandatory stops in your route (via-point), which can also be used to find out how far away the next stop is. However, this functionality is not offered by all route planners and requires a cable to get the route on the XT/XT2.
The XT works with Garmin Drive and Explore. The XT2 works with the Tread-app and Explore (the data is in the same cloud). This guide is primarily written for the XT2, but 90% is also relevant for the XT.
All steps are explained in detail below.

You can use any tool as long as you can export tracks and POIs as GPX. I personally use the format GXP 1.1 preferably without routes (only track and POIs), to avoid confusion. Possible routeplanners: MyRouteApp.com, Kurviger.de, RouteYou.com and Calimoto.com.
Create your routes in MRA (see the many online tutorials).
TIP: Add Points of Interest (POIs) per route. You can add them in MRA via 'Points of Interest' by adding them from a list, or manually add them by clicking on the 'Manage' tab under Points of Interest.
When using certain keywords in the naming of your waypoints, you can also add the appropriate icons to it for your XT/XT2. Use my POI2PIC tool to extend your GPX with icons.

Warning: When importing GPX files with POIs via Explore, the names of the POIs are truncated to 20 characters (annoying limitation). When importing via the Tread app (Option 2), this limitation does not apply!
Warning: To prevent sync problems, it is advisable to have your Tread app and XT2 turned off while working with Garmin Explore. Only start them after closing Garmin Explore.

Note: The preview image of the route in MRA can differ from the route planner (especially for routes with off-road sections). This in a bug and can be ignored.

When the Tread app is started by MRA:
Note: Instead of converting your track to route on the XT2, you can also do this in the Tread App (including moving the route to the right collection).
Warning: If you use Garmin Explore for the XT2, make sure Bluetooth is disabled for Explore and start the Tread-App for synchronising with the XT2.

Note: Garmin has developed Explore for the XT and Tread for the XT2. Garmin's track record regarding software development for both the tools and the XT/XT2 is not great. New bugs and issues frequently occur after an update (never update the XT/XT2 right before you go on a trip). My advice is to use the tools as Garmin intended, as this minimizes the risk of problems (so use Explore for the XT and Tread for the XT2).
Ensure that the Tread app is open on your phone, to be able to sync the tracks and POIs to your device (only XT2).










The XT2 is a bit awkward and creates the route in the 'Unorganized' collection instead of the collecion where the Track is located. This can be resolved:
Note: It is important that both the track and the route are in a "visible" collection, so you can see both at the same time (this is why it is useful to place them in the same collection).








NEXT STEP: Enhance the POIs on your routes with nice icons using my POI2PIC tool!
It's good to know that if you take a wrong turn and let your Garmin 'recalculate', it will search for the next via-point (intermediate point). This can cause unpredictable behavior if your via-points are not well-placed. However, it could also result from Garmin's interpretation of your route (this also explains route differences between various navigation systems). When converting a track to a route, you don't experience this unpredictability, but it does come with certain limitations if you need to resume the route halfway. This is because this route only has two via-points (start and end), which often causes you to be directed toward the end quickly (via the shortest route). This can be easily resolved:
Finally, a few tips:
NEXT STEP: Enhance the POIs on your routes with nice icons using my POI2PIC tool!