As we previously shared, the Parse service is shutting down at the end of this month. Specifically, we will disable the Parse service on Monday, January 30, 2017. Throughout the day we will be disabling the Parse API on an app-by-app basis. You can expect any of the following to happen if your app has not been migrated by then:
- you will not be able to access the data browser
- you will not be able to export any data
- your application will no longer be able to access the Parse API (
- your Parse Files will no longer be available for download
- any subdomains (
*.parseapp.com) or custom domains associated with your app will stop serving content
- Cloud Code triggers, functions, webhooks, and all associated functionality will cease working
- your app users will no longer be able to log in, or receive password reset emails
- push notifications will no longer be sent
You will not be able to export or access your data in any way after your app is disabled on January 30, 2017. If you still have data on Parse that you would like to save, you should export your Parse data as soon as possible. This document will guide you through the steps needed to migrate your database, as well as setting up your own open-source Parse Server.
For most apps, the second phase of the migration process is non-trivial, and will require dedicated development time. We recommend the following schedule:
- April 28, 2016: Data migrated to a self-hosted MongoDB (Step 1)
- July 28, 2016: Finish setting up your self-hosted Parse Server (Steps 2-11)
- September 28, 2016: Publish updated app that points to production Parse Server (Step 12)
Following this schedule will give you time to migrate your data and deploy your own Parse Server, as well as train your development team to maintain and scale the service. It will also give your users enough time to update to the new version of your app.
This migration guide assumes the use of Heroku and either mLab or ObjectRocket. These three services are easy to use, especially if you are new to deploying and managing your own backend stack. But, you can elect to use any infrastructure provider that supports Node.js environments.
After completion, you will have the following:
- Parse Server running on your computer, allowing you to develop locally.
- Parse Server running on Heroku or another infrastructure provider.
- Your app's data stored in MongoDB hosted on mLab or ObjectRocket.
- Your app's static files stored in S3 or another hosting provider.
- No dependency on
- Your app's client-side code updated to point to your Parse Server instance, ready to be released.
- No dependency on
api.parse.comfor the new app client.
We highly recommend that you first run through this guide with a development or test version of your app before working with a production app.
Here is a visual overview of the migration steps. Follow the detailed instructions after the diagram to migrate your app.