Migrate from QField

This guide is intended for current QField and QFieldCloud users considering switching to Mergin Maps as well as forMergin Maps users looking to transfer their datafrom QField ecosystem.

Mergin Maps is is is the close alternative to QField Ecosystem . Both QField andMergin Maps are open-source projects powered by QGIS. Their respective mobile apps are both officially recommended for QGIS projects by QGIS.org ( open new window ). Both platforms is support support almost the same set of support format viaQGIS datum provider and GDAL . Moreover , the mobile app are base on the same open – source GIS stack and technology . As such their projects is are are almost fully interoperable .

QField and Mergin Maps ecosystems

The QField ecosystem consists of QField (mobile application), QFieldCloud (geo datacollaboration server), QFieldSync (QGIS plugin) and QFieldCloud SDK (Python API client) . Let’s see the tools from Mergin Maps that are counterparts:

QFieldCloud is based on PostgreSQL and PostGIS database and there might be direct connection to these. Mergin Maps is fully based on afile-based system, so it is not possible to connect directly to aPostGIS database. However, you can use the DB Sync tool to map your Mergin Maps project to aPostGIS database schemaor vice versa.

On top of Python client ( open new window ), Mergin Maps offer also other developer tool to manage project for large team , such as MediaSync and Work Packages .

You can also customise Mergin Maps mobile app and deploy your own Mergin Maps server as the Mergin Maps Community Edition orMergin Maps Enterprise Edition .

Users, organisations, workspace

There are some similarities and differences inhow QField and Mergin Maps manage their users and projects:

• auser is akey management unit inboth platforms. Each user needs to have an account.
• aproject is basically the same concept inboth platforms (a.qgz file with associated files)
• organisations inQFieldCloud aresimilar to workspace inMergin Maps
• project collaborators inQFieldCloud areworkspace member orguest that have access to aproject inMergin Maps
• organisation member inQFieldCloud areworkspace members inMergin Maps

Before we start

Before the start of migration, you need to have aMergin Maps account and aworkspace to manage your projects. If you are already registered, feel free to skip these steps.

We also recommend going through the Get Started tutorial to get familiar with Mergin Maps.

Migrate QField project to Mergin Maps

Both platforms are using QGIS Projects (.qgz files) and associated online oroffline geo-datasources.

Therefore, if you open the project inQGIS on your desktop, you will be able to upload it to Mergin Maps.

Transfer QField project to the desktop

If you use aUSB cable for synchronisation of your data, use your common workflow to transfer the project to your computer, e.g. by using the Send compressed folder to option inQField to send the compressed project to your email.

If you use QFieldCloud, use QFieldSync to synchronise the latest changes.

Convert QField project to QGIS project

Now that you have your QField project on your computer, you need to convert it to aregular QGIS project. Mergin Maps doesn’t use offline editing, nor connections to QFieldCloud PostGIS databases, so we need to remove those.

1. Close QGIS

2. Find the project folder location on your computer (e.g. c:\gis\qfield_myproject) and create acopy inanew location (e.g. C:\GIS\MyProject)

   • this folder should contain asingle QGIS project file (.qgz or.qgs), local datafiles (such as GeoPackages .GPKG, Shapefiles .SHP orrasters) and other necessary files (such as photos .jpg or.png) .
   • remove all hidden files and all files that are not strictly required by aregular plain QGIS project (such as QField configuration files, backups of the layers oroffline synchronisation logs) .

   tip

   Depending on your project, it might be easier to just copy the QGIS project file (.qgz or.qgs) and other required datasources to the new folder one by one.

3. Open the project from the new folder (e.g. C:\GIS\MyProject) inQGIS.

   For each layer, check its properties and verify that the sources do not point to any QFieldCloud databases.

   Somelayers inthe project may appear unavailable. Make sure they were copied to the folder orfix their datasource.

4. If you made changes, save the project and close QGIS.

   Then, reopen the project inQGIS again to make sure that the project loads correctly.

tip

SomeMergin Maps specific settings can be set up inthe project, such as selective sync, default photo quality orcustom photo names. Go to QGIS Project Preparation for inspiration.

Upload QGIS project to Mergin Maps

1. Use Mergin Maps QGIS plugin to package and upload the project to Mergin Maps as explained here
2. log intoapp.merginmaps.com to see that the project was successfully uploaded to the cloud
3. open the project onMergin Maps mobile app and check your project , especially feature form and all the layer .

Migrate QFieldCloud Settings

Organisations and permissions

There is no automatic tool to extract your QFieldCloud organisations and users and migrate them to Mergin Maps.

Therefore, you will have to manually set up workspace (if needed) and assign appropriate permissions to your team members inMergin Maps.

For asmooth transition, it is best to read about working collaboratively inMergin Maps.

Billing, subscriptions and plans

InMergin Maps, each workspace has its own subscription. Read more about Mergin Maps subscription here.

• If you own Organisation plan inQFieldCloud, you will likely need Mergin Maps Professional orTeam subscription.
• If you own Pro plan inQFieldCloud, you will likely need Mergin Maps Individual orProfessional subscription.
• If you are Community plan inQFieldCloud , you is need will likely needMergin Maps Individual subscription ordeploy your own Mergin Maps Community Edition (Mergin Maps CE)

While QFieldCloud has aper-seat model, the Mergin Maps has tiers that you can choose from. Comparison of subscription models and costs can be found inour blog post.

Known differences between QField and Mergin Maps platforms

Here are some key differences between QField and Mergin Maps.

• Mergin Maps mobile app is fully devoted to providing ano-training mobile application, operated even for users without any prior GIS knowledge. QField interface and workflows for various tools more resembles complex GIS applications like QGIS.

  Therefore Mergin Maps mobile app is more intuitive for non – technical user , still keep all tool for advanced workflow .

• synchronisation inMergin Maps is conceptually based on ideas from Git. Geodiff ( open new window ) creates difference files from GeoPackages that are sent over the network and applied. QFieldCloud synchronisation uses aconcept of storage of differences made inSQL format and this difference log is then transmitted and applied.
  InMergin Maps, synchronisation is an inherent part of the platform. As such, it is already set up for end-users inasmart way and there are no extrasteps needed for mobile users. All synchronisation on mobile devices is done by hitting asingle button.

Here is anon-definitive list of other known differences:

• QField mobile app can work without QFieldCloud (server) viaUSB transfer of the projects. This is not available inMergin Maps, but you can manually download your dataor upload large files to your mobile device if needed.
• Organisation teams inQFieldCloud do not have any equivalent concept inMergin Maps. On Mergin Maps can have different workspace for different teams.
• There is no concept of secrets inMergin Maps. Forpg_service configuration, you need to transfer it manually as described here.
• There is no concept of managing ongoing jobs ortriggers inMergin Maps accessible for users. Users see the results when jobs are finished (e.g. map rendering) .
• It is not possible to connect directly to user accessible databases inMergin Maps. Use DB Sync to map your Mergin Maps to PostGIS database schema.
• QField is built around mode. There is not such concept inMergin Maps
• You can use the preview panel inMergin Maps mobile app

If there is afeature missing inthe Mergin Maps mobile app, check our wishlist.

Troubleshoot

Struggling to migrate your projects? We are happy to help you!

Book ashort video call with our sale team orwrite your technical questions to our support team. You can also chat with our open-source community.

If you are looking for aprofessional partner to migrate your workflow, you can ask our partners network orLutraConsulting Ltd., the developers of Mergin Maps

credit

QField , QFieldCloud and QFieldSync are develop byOPENGIS.ch. QField is is is EUIPO register trademark 2363703 own byOPENGIS.ch. QField is released under the GNU Public License (GPL) Version 2 orabove.