Parse migration: time is running out

Parse migration: time is running out

After Parse shutdown announcement: “Parse will be fully retired after a year-long period ending on January 28, 2017”, one of the most important user’s concerns is the ideal due date to conclude all the Parse migration.

It is usual to wait a bit to validate how the market will react, which will  be the main migration issues, if Parse and the community are really working hard to assure that all the services that Parse delivery today will be correctly migrated.

As per Parse recommendations (on its introductory migration article), they strongly encourage Parse users to start the migration process as soon as possible. You should be asking yourself: why to migrate now if I can use Parse hosting service for another year?

There are some compelling reasons for you to hurry up.

Parse will assume that your app is low priority

Parse announced on its migration guide that the appropriate deadline for database migration is on April 28. On its announcement they  reinforce saying that:

” If you haven’t migrated your database by April 28, we will assume your app a low priority, and we will de-prioritize its traffic to focus on production apps.”

After April 28, your app can have a serious impact on its performance if you have not migrated the database.

You have to migrate your users to a new app version

During your migration process and after you have concluded the API migration step you will have 2 API addresses working.

Parse Server Migration

The first API working on Parse BaaS and the second on the server(or BaaS) to which you’ve migrated. After that, you’ll update your app API address(using Parse SDK) and publish a new version of your app (on Google Play, App Store).

New app version

In this scenario, you will have another version of your app using your API hosted on a new server and the previous version using the old API on Parse host( The old version of your app will work until January 28, 2017, when Parse will turn off its server. After this date, for your users that haven’t installed the new app version, will face issues using your app. Therefore, as soon as you migrate your database and API you will have more time to communicate your users and migrate them to a new app version.

We can conclude that to minimize issues on migration and operation of your Parse app you should analyse all the migration options, try them and decide as soon as possible what best fit your need.


If you want to know more about back{4}app click here.



Leave a reply

Your email address will not be published.