This how-to explains how to migrate your app from a Mendix Cloud v3 node to a Mendix Cloud v4 node.
It will teach you how to do the following:
Migrate your licensed app from Mendix Cloud v3 to v4
Before starting this how-to, make sure you have completed the following prerequisites:
Have a Mendix Cloud v4 node available (to request a licensed v4 Cloud Node, contact your Customer Success Manager (CSM))
Have the Technical Contact role for both your existing v3 and available v4 Cloud Nodes
Create a new temporary Free App without a sandbox environment – instructions for unlinking a Free App from a sandbox are here: Licensing Apps
3 Migrating the App
To migrate your app from a v3 node to a v4 node in the Mendix Cloud, follow the steps in the sections below.
3.1 Linking the New Free App to the v4 Node
First, link the new temporary app to the cloud v4 node.
To learn how to do this, see Licensing Apps.
3.2 Copying Data from v3 to v4
Before migrating, you need to copy the data from the v3 node to the v4 node. After copying, test your app and correct errors if needed. Repeat this until all the errors are solved.
3.2.1 Backing Up
Transfer the backup data of the app on Mendix Cloud v3 to the app on Mendix Cloud v4 by follow these steps:
Download a backup from your app hosted in Mendix Cloud v3 (for details, see How to Download a Backup).
Upload the downloaded backup to your app hosted in Mendix Cloud v4 (for details, see How to Restore a Backup).
3.2.2 Downloading and Uploading the Deployment Package
Download the deployment package of your app hosted in cloud v3 and upload the deployment package to the app hosted in Cloud v4.
To download a deployment package, follow these steps:
Go to Environments of the v3 app.
Click Details for a Deployment Package.
Click Download Package.
To upload the deployment package, follow these steps:
Go to Environments of the v4 App.
Below the Deployment Package Repository, click Upload.
Browse and select the downloaded deployment package from your device.
3.2.3 Configuring the New App
Before starting your app in Mendix Cloud v4, make sure it has the same configurations as the v3 node. You can find the node settings on the Environment Details page under Model Options, Network, Runtime, and Maintenance.
3.2.4 Testing and Repeating
Now that the app on Mendix Cloud v4 contains your data and is configured, deploy the deployment package to an environment and start your app.
To learn how to do this, see How to Deploy the App to an Environment.
3.3 Offboarding the v3 Node
Your app is now running in Mendix Cloud v4. If everything works correctly, submit a request at Mendix Support to offboard the v3 node. This means that the app will be detached from the node.
With the node removed, the app will still remain in the Developer Portal as a Free App.
Make sure you have downloaded the latest backup and deployment package before offboarding the node.
3.4 Linking the App to the v4 Node
After the v3 node has been offboarded, follow these steps to link the app to the v4 Node:
In the Developer Portal, go to Apps and select the app that has been detached from the v3 node.
Once you are in the app, go to the Environments tab in the left menu.
Click select a node.
Select the v4 node by clicking Use this Node and link it to your app. The currently linked (temporary) app will be unlinked automatically. The temporary app can be deleted.
For more information, see Licensing Apps.
3.5 Changing the App URL
To change the App URL (if you are not using a custom domain) you will need to contact Mendix Support. You will need to provide the following information:
- URL for the new app, which is available from the Environments page for the new (v4) app
- URL for the old app, which is available from the Environments page for the old (v3) app
- App ID for the new app, which is available from the General page for the new (v4) app
- App ID for the old app, which is available from the General page for the old (v3) app
3.6 Changing a Custom Domain
If you have a custom domain set up, you will need to change this. Instructions for doing this are here: Custom Domains.