Skip to content

Migrating Mobile Development Kit App From SAP Business Technology Platform Neo to Cloud Foundry Environment

In this document we walk you through the steps to be followed to migrate Mobile Development Kit app from SAP Business Technology Platform Neo to Cloud Foundry Environment, and enhance it further.

In general, landscape migration is followed to migrate SAP Business Technology Platform Neo to Cloud Foundry environment:

  • Creating Sub-Accounts, Organizations, and Spaces
  • SAP Cloud Connector setup must be copied to point to the Cloud Foundry account
  • Identity provider settings need to be replicated and so on

Before we get started it's essential that you get familiarized with the following changes:

These changes are typically more beneficial, providing you with advanced features. Understanding these changes prior to migration will ensure a smooth and efficient transition process.


  1. Migrate mobile Application configuration from SAP Mobile Services Neo to Cloud Foundry environment

    The application can either be recreated manually or the application configuration in Neo can be exported and later imported into Cloud Foundry. Due to the differences in mobile services in Neo and Cloud Foundry, only a part of the application configuration can be imported into Cloud Foundry, and other parts of the configuration must be recreated manually. Please refer to the below documentations for more information:

    If you had previously deployed the Mobile Development Kit metadata (app definitions) to the SAP Mobile Services Neo app update, the same needs to be done for your application configured in SAP Mobile Services Cloud Foundry. To deploy the Mobile Development Kit metadata, you can use one of the following options:


    Refer to this document Migration From SAP Web IDE to SAP Business Application Studio for more information.

    1. Reset/Re-onboard Mobile Development Kit client

    2. Before the application is reset to onboard with the new Cloud Foundry mobile application, users need to ensure that there is no unsynchronized data left in their local offline databases by performing a sync within the application. When the application is reset any unsynchronized data will be lost.

    3. The Mobile application URLs of SAP Business Technology Platform Neo and Cloud Foundry environments are different. In Cloud Foundry, each mobile application has its own unique hostname to connect, as shown on the APIs page of an application. Furthermore, the OAuth specific URLs of Neo and Cloud Foundry are also different. In order to connect to the mobile application configured in Cloud Foundry environment, Mobile Development Kit client must be reset and it has to be onboarded again.
    4. If you have built your branded Mobile Development Kit client by providing mobile services connection settings in .mdkproject, you need to update the BrandedSettings.json with new connection details and rebuild the client.
    5. If override functionality is enabled in the client, users can scan the new on-boarding QR code connecting to SAP Mobile Services in Cloud Foundry environment. The on-boarding QR code can be found in SAP Mobile Services app configuration (under SAP mobile service cockpit > Mobile Applications > Native/MDK > {app_name} > APIs tab) or in SAP Business Application Studio (right click on and open it in Application Editor > QR Code).

Last update: August 23, 2023