Migration Guide (Archive)

As we previously shared, the Parse service was shut down on January 30, 2017.

You will not be able to export or access your data in any way after your app is disabled on January 30, 2017. This document will guide you through the steps needed to set up your own open-source Parse Server. At this point, it is no longer possible to migrate a Parse.com database.

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 *.parseapp.com.
  • Your app's client-side code updated to point to your Parse Server instance, ready to be released.
  • No dependency on api.parse.com for 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.