All Collections
Product Updates
Places 2.0 Transition to Locations Plugin
Places 2.0 Transition to Locations Plugin

The process to transfer places 2.0 data to Locations.

Tim Tietz avatar
Written by Tim Tietz
Updated over a week ago

Introduction

As our product suite evolves, we are constantly working towards providing our users with enhanced features. In line with this, we would like to inform our valued clients about important changes concerning our Places 2.0 and Locations Plugin.

Phasing Out Places 2.0

We have been running the Places 2.0 plugin concurrently with our Locations Plugin for a significant period. However, we have made the decision to deprecate Places 2.0. This means:

  • Developer Support for Places 2.0 will cease.

  • No further Bug Fixes will be released.

  • Enhancements for Places 2.0 are no longer planned.

  • Customer Service (CS) and Account Management (AM) Support will not be available.

  • Updates and additional Enhancements will be halted.

Despite its wide usage, we've observed that the Places 2.0 plugin does not meet the needs of many clients, prompting a shift towards our more advanced Locations Plugin.

Benefits of the Locations Plugin

The Locations Plugin allows users to showcase various points of interest or locations. Key features include:

  • The ability to create multiple categories for sorting locations, provides users with a refined search experience.

  • Detailed information about each added location, offering insights and data for your users.

Migrating Data from Places 2.0 to the Locations Plugin

For those who wish to transition from Places 2.0, the Locations Plugin offers a seamless migration process:

  1. Export and Import via CSV: Users can transfer their data by exporting from Places 2.0 and subsequently importing the data into the Locations Plugin using a CSV file.

    • Potential Issues and Solutions:

      • Duplicate Locations: Some users have noticed duplicate entries upon exporting from Places 2.0. If you encounter this, ensure you delete any duplicate instances within the CSV file before importing.

      • CSV Loading Issues: If your CSV fails to import correctly into the Locations Plugin, inspect the file for any extra spaces or formatting anomalies. Continuous issues? Don't hesitate to contact our support team at support@buildfire.com.

We understand the importance of smooth transitions, and our team is here to support you through this change. If you have questions or require assistance, please reach out to our dedicated support team.

Step 2: Above the list of your places, click on 'Export CSV'

Step 3: Navigate to your Locations feature.

If you have not created a new location feature, navigate to App Components -> Marketplace and search for 'Locations'. Add the feature by clicking on the plus button.

Step 4: Go to the Locations section and click on 'Bulk Action'

Here you have the option to download a template, export, or import a CSV file.

Step 5: Click on 'Import' and select the exported CSV file.

You have now successfully imported locations.

We understand the importance of smooth transitions, and our team is here to support you through this change. If you have questions or require assistance, please reach out to our dedicated support team.

If you should have any questions on the migration process from places 2.0 to locations or any questions about the locations plugin please contact us at support@buildfire.com and we will be more than happy to help address any inquiries you may have.

Did this answer your question?