Application Migration


We have made it possible to export template, user, and track data to another GpsGate Server using Archiving. While this does not cover full server migration yet, it makes it easier to migrate one or several applications and related data to another server. Archiving is not intended for backup. For back up, please read this guide.


Using Archiving, you could export track data to a folder, FTP server, or Amazon S3 storage, and then import it to a server of your choosing.

Now it is possible to archive other types of data as well. New additions are:

  • Application data including reports and POIs
  • User data including Device Mapper information.

Furthermore, it is possible to set up Archiving so that it exports data directly to another GpsGate Server instance.

  • Note: if you use a GpsGate Cloud hosted server, contact support first.


  1. Login to Site Admin
  2. Go to Plugins tab.
  3. Set the Repository URL to:
  4. Under My Plugins tab, make sure that Archiving is installed and up to date.
  5. If you are using Cleanup, Reporting and PointsOfInterest plugins, make sure that they are up to date, too.

Setting up Direct Export

To set up direct export to another GpsGate Server, you will need access to both the source and the destination server at the same time. Log in to Site Admin application of each server and follow these steps.

On the destination server…
Make sure that the destination server has all the plugins that are installed on the source server and that their versions are the same. Otherwise, you may corrupt your target server in the worst case.
Any custom variables created on the source should be created at the destination as well.

On the source server…
Set up a new Export Rule via SiteAdmin > Archiving > Export Rules > Add Rule. For a one-time transfer of all available data, choose a Manual Export Rule.

On the Export Rule settings page, specify the name of the rule.
Specify Application Tags defining which applications are taken into account when exporting data.

Now check the Direct option in Destination settings. When you choose this option, an ExportRuleKey will be generated.

  • On Path input the destination server’s URL without the “.../SiteAdmin/...” part. e.g., and click on Test button to check that everything is alright.


Other Export Rule options:

  • Make sure to keep Export Application Data checked to actually export the applications themselves to the destination server.
  • Keep Export Users checked to export the users and add them to the right applications.
  • Keep Export Tracks checked to export track data from the specified period to the other server. Alternatively, uncheck this to start anew on the other server and only work with newly received data. Either way, do not forget that you will need to reconfigure the devices to send the data to the new server.

Do not save the Export Rule yet!

Back on the destination sever…
Create a new Import Rule on the destination server via SiteAdmin > Archiving > Import > New.
After specifying the rule name, select the Direct option in the Source section of the Import Rule.
Now copy the ExportRuleKey generated in the Export Rule on the source server to the ExportRuleKey field of this Import Rule.


For the migration case, contact support for advice on license migration and checking/unchecking the Use Licenses option.

If you’re migrating data to a freshly created server instance, you don’t need to worry about the Handle Username Conflicts option. However, if there are existing users there this option will determine how to resolve the potential collisions given that the usernames must be unique.


Check Import Reports to import Report Definitions and Reports.
Application Tags under Reports are useful when you are setting up a Reporting Server - do not check these when fully migrating applications and users to another server.
You can filter the imported tracks on the import side as well, but for the server migration case, just expand the period enough to accept all exported data, or uncheck the Import Tracks option if you are not migrating track data.

After setting these, save the Import Rule, and then enable it by clicking on the slider on the Import Rule list.


Back on the source server…
Specify the Path to the destination server and click Test to ensure that it works as expected.

Now you can save the Export Rule.

After the export is completed successfully, the included data should be available on the destination server. Here is a complete guide for merging two servers.