How to Migrate GPS Trackers to a New Platform: A Reseller’s Step-by-Step Guide

Having to move from one platform to another involves moving your devices, data and customer accounts from one tracking system to another, typically by exporting your data, pointing each device at a new tracking server, importing history, and then checking to see if everything reports. Most reseller fleets can make the change, in stages, with a successfully tested rollback with minimal or no disruption to customers.

Disclosure: Fleet Stack is a self-hosted white label GPS tracking system, which could be a migration to our system. The following steps are system independent and will work on any system in which you move them.

Key takeaways

There are five phases of migration – plan and audit, export data, stand up the new platform, repoint devices, and finally, verify and cut over.

Both the device and the server address that it reports to remain constant. Repointing is a configuration change that is typically sent either over the air or via SMS command.

Export data prior to handling devices. Ensure that you can export device, vehicle, user and position history in CSV or in a database dump.

Move in phases and maintain the old site until the new one is tested; have a rollback.

The server address for the domain name (fqdn) may be better than using a standard domain name, but this will depend on the type of device and its DNS support and firmware – test first to ensure it works as expected when you move.

What's driving a reseller to move to new GPS tracking platforms?

Typically, resellers change platforms for some of the following reasons, and each of these reasons will determine the plan:

Cost: per device cloud cost has increased as fleet has increased and is now higher than one-off licence. Read our article on Self Hosted GPS Tracking vs Cloud GPS Tracking.

Control and branding: you want a domain of your own, a data location of your own and reseller accounts branded to your name.

Features or support: The platform doesn't have a feature or support has been dropped.

Lock-in risk: You don't want to be locked into the database's terms.

Regardless of the cause, the process is the same. This is the process for the remainder of this guide.

What's the best way to transfer GPS trackers to another platform? (5 steps)

Go through these 5 steps one by one. Every one has a definite exit check prior to moving to the next.

Plan and audit (Step 1).

Write down all the devices (IMEI, model and protocol), all the customer accounts and all the information you should retain. Write down the reporting interval and sensors at use for each device. Set batch sizes (e.g. 10 at first, 50, then the rest) and let the customers know beforehand.

Export your data:

Export all of the data from the previous platform – devices and vehicles, users, geofences, position history, etc. – in an open format like CSV or a database dump before changing any device. If the platform has an API only, then write the import/export script. Double check the files are open and have what you expect; this is also the backup record you can expect if something goes wrong.

Step up and set up the new platform

Step 4: Open the works up to the sky.

Install or provision the new platform, make your reseller/customer account structure, set up branding and your domain, and make sure it decodes your devices' protocols (GT06, Teltonika, Queclink and so on). See our GPS tracker protocols guide for details on how protocols and compatibility work, and our list of supported devices. Copy the data from Step 2 and check some of the data.

Configure devices to point to the new server (step 4):

All the device has to do is change its target address and port to that of the new server. Unlike traditional trackers, most of them let you add a new server over the air or even via SMS and you do not physically touch the car. Test one device first and verify a connection and report before sending a command to a batch.

Domain vs IP: If your devices have been set up with a domain (such as track.yourbrand.com) instead of just an IP address, then repointing can be a change in your DNS settings instead of a command on your device. The feasibility of that doing a clean cut will depend on the DNS support provided by each device, DNS caching and reconnection behaviour as well as the firmware and test it on a sample before depending on it.

Verify, cut over and decommission (Step 5):

Ensure the services are correct, cut over and decommission.

Verify positions, ignition and key sensors receive the correct position at the new platform for each batch and alerts and reports operate as expected. Until a batch is verified, run the old platform in parallel—when the batch is in trouble, go back by repointing old devices. After all the batches are confirmed, and customers are on the new dashboards, de-commission the old platform and discontinue billing on it.

What is the best way to migrate without any impact on customer systems?

While a device is offline for a few minutes as it re-connects to the new server, there is no guarantee that there will be no downtime, but you can limit disruption to minutes per device, and no data loss:

If a device is offline after repointing, first check the server address, port and SIM data session, our guide to why a GPS tracker goes offline covers the common reasons for this occurrence.

Pre-migration checklist

Before you repoint any one device, check each one of these to confirm:

Here are some common pitfalls in migration that you should try to avoid:

Frequently asked questions

Is it necessary to go through all the vehicles to move a GPS tracker?
Usually no. The device remains in the vehicle as most trackers will accept a new server address by an over-the-air or SMS command. Only physical visit is needed if a device cannot be reconfigured remotely.

Will historical data be lost if switching platforms?
If you export it first, not if you don't. Before repointing, export device, vehicle, user and position history as CSV or as a dump from the old platform to a new platform; or export it as a database dump and import it to a new platform. Save a copy of the export file.

What is the timeframe for a GPS Platform migration?
This is dependent upon fleet size, device models and the quality of data you have. A small fleet can be moved in a day or two and larger fleets can be staged over days or weeks in batches. Plan in batches NOT single cut-over dates.

Is it possible to migrate without the customers knowing about it?
Often, yes, for the dashboard experience, if you set up their accounts and branding first. Devices are temporarily disconnected during the reconnection process, so migrate these in non peak times and in groups to minimize that to minutes.

Are the GPS devices same to the new platform?
No, but if the new platform is able to accommodate the devices protocols. It's the server that changes, the hardware remains. Check protocol support prior to relocation. Read our GPS tracker protocols guide.

Are there any issues regarding compliance to AIS-140 during migration?
The registration of a device and its hardware certification (AIS-140) do not change as a result of migration. Verify that the new configuration does not result in a loss of the required functions or loss of registration; check our AIS-140 compliance guide.

Converted to a self-hosted platform.

When moving to a per-device fee reduction or to ownership of the data, the typical end point is a self-hosted platform where ownership of the database and operation of the platform is under your own domain. For a cost comparison, read our self hosted GPS tracking software vs cloud GPS tracking page; for the full reseller model, see our white label GPS tracking software page. Our list of the basic options for top white label GPS platforms is provided for comparison of destinations.

Fleet Stack is a white label GPS tracking solution. This guide does not specify any platform; check the exact export, device-configuration and compliance procedures for your platform and device model prior to migration.