Action Required Service Updates

IBM Cloud Mobile Foundation: Migration from Deprecated Plans to New Plans

Share this post:

Mobile Foundation Service: Migrating from deprecated plans

In February 2018, we announced the deprecation of Developer, Developer Pro, and Professional Per Capacity pricing plans for Mobile Foundation Service. These plans will be sunset as of February 28, 2019, as announced. The new pricing plans are based on the simple metrics of number of client devices or applications, which allows you to start small and grow and also makes it easier to estimate and predict spending. If you are still on a deprecated plan, immediate action is required to migrate to one of the new plans as per the guidelines and steps below.

Migration Plan

The migration plan for users on each of the deprecated plans are as follows :

  1. Developer (Deprecated): Users on this plan can migrate to Developer (new) plan with the click of a button as specified in “Migration Steps” section. The new Developer plan has a limitation of 10 daily client devices and is not meant for production usage. If you wish to migrate to a production plan (Professional Per Device or Professional 1 Application), refer to the section “Migration from Developer (Deprecated) to Production Plans”.
  2. Developer Pro: Users on this plan can migrate to one of the production plans (Professional Per Device or Professional 1 Application) with the click of a button as specified in “Migration Steps” section.
  3. Professional Per Capacity: Users on this plan can migrate to one of the production plans (Professional Per Device or Professional 1 Application) with the click of a button as specified in “Migration Steps” section.

Migration Steps

In order to migrate your Mobile Foundation instance follow the steps below

  1. Log in to IBM Cloud to see the cloud dashboard view. View the detailed dashboard by clicking on View all.
  2. Click on the Mobile Foundation service instance that needs to be migrated.
  3. Click on the Plan tab on the left navigation pane to go to the plan view.
  4. Select the appropriate plan (as described in the migration plan section) and click on the Save button to upgrade to the new plan.

Migration from Developer (Deprecated) to Production Plans

There is no auto migration from Developer (Deprecated) plan to Professional Per Device or  Professional 1 Application plans. If you wish to move from Developer (Deprecated) plan to Professional Per Device or  Professional 1 Application, follow the steps given below:

  1. Export the application configurations and adapters from the Developer (Deprecated) instance.
  2. Create a new production instance using either the Professional Per Device or Professional 1 Application plan.
  3. Import the application configurations and adapters into the new instance. Since this new instance comes with a different URL, the mobile client application need to be updated. If you wish to retain the same URL, rename your Developer (Deprecated) service instance and the associated server app. Unmap the route assigned to the server app. While creating the production instance, use the original name of the developer instance. This ensures the new instance gets the same URL.

Follow the instructions for exporting and importing application and adapter configurations using Mobile Foundation console or refer to other options to do the same.

Need help?

Reach out to us on Slack or open a support ticket for help with migration issues.

Learning Resources

 

Senior Offering Manager

More Action Required Service Updates stories
April 30, 2019

Introducing IBM Analytics Engine v1.2 and Announcing the Deprecation of IBM Analytics Engine v1.0

We are excited to inform you about the new version of IBM Analytics Engine v1.2 that will be available starting May 15, 2019. Along with this release, Analytics Engine v1.0 will be retired.

Continue reading

April 23, 2019

Announcing the Deprecation of the Watson Machine Learning JSON Token Authentication Service

We’d like to inform you about the deprecation of the Watson Machine Learning JSON Token Authentication service. This method of authentication will be retired on May 30, 2019.

Continue reading