Operating a mobility business is anything but static, and often an overhaul of the subaccount structure is necessary; with that, you might need to move zones between different subaccounts.
If you need to move any zones (Parking zones, No-go zones, Parking stations, etc.) from one subaccount to another, the process consists of three main steps:
Export → Delete → Import
This ensures that the zones are removed from the original subaccount and recreated under the correct new subaccount.
NB! Just importing zones that were exported from a specific subaccount into another one would not work, because the system would identify an identical zone already in the system and update the existing one instead of creating a new one. That is why deleting the previous zone is needed in this case.
For instructions on how to create and maintain zones, you can check our Zone maintenance article.
Make sure you are currently working in the subaccount where the zones are located. You can then export the zones either individually (pressing the "⋮" button under each zone and exporting it) or in bulk using the export button (
):
The resulting export file(s) will have a GeoJSON extension.
Navigate to the target subaccount and try uploading the zone:
If you try to import the zone without deleting the existing one, you'll see this message telling you that the existing zone has been updated:
That is why it's important to delete the existing zone from the previous subaccount before importing it into the target subaccount.
One the zone is deleted from the existing subaccount, the upload task should be successful:
The same approach can be taken for all the zone types. In the case of the "Parking stations", the only caveat is that the format of the resulting export file will be either CSV or XLSX, but the import file can only be a CSV file. Ensure that the existing parking stations are exported in CSV format so it's easier to import them afterwards.