Migration Script

Migration process scope

This is a manually activated process which is run once to migrate your configuration from an older connector version to a newer version to avoid having to perform a new setup from scratch.

Migration script from v1.1.1 to v2.0.0

To run the migration process successfully, you will need to have both versions - v1.1.1 and v2.0.0 - of the connector uploaded to the same Mambu Process Orchestrator (MPO) tenant.

Installation and configuration

The migration process requires the folder ID of the previous connector version (v1.1.1) in order to retrieve the data, and the folder ID of the new connector version (v2.0.0) to write the extracted data correctly. It also requires a valid OAuthUrl used to trigger the Refresh Token process. The migration script uses some MPO API calls, therefore you will also need valid authentication credentials; apiKey, mpoUrl, and secret.

Notes

  1. To successfully run the migration script, both the initial and the current version of the connector need to use the same API Key - which is generated during the MPO Setup process
  2. To obtain the ID of the folder in MPO, navigate to the list of your MPO connectors, select the one you need, then click the Information icon. The ID will appear in a new sidebar on the right-hand side of the MPO workspace.

How to retrieve migration folder IDs

Please be aware

To avoid any potential loss of data, the migration script should be run outside of working hours, when there are no actions such as client or deposit account creation being run in Mambu.

MPO setup

Initial configuration

In the MPO environment, go to the Migration process folder (within the v2.0.0 connector folder) and open the Start migration [main process], switch to View mode and click New task. Fill in all the required parameters and click Add task. Wait until the task is processed.

Migration process

Alternatively, you can use the following JSON. Modify it and paste into the Code editor tab.

{
    "apiKey": "",
    "initial_folder_id": "",
    "mpoUrl": "",
    "new_folder_id": "",
    "oauthUrl": "",
    "secret": ""
}
ParameterDescription
apiKeyThis is the same connector API key ID generated during MPO setup. Details on where it was generated can be found at MPO Setup.
initial_folder_idThe identification number for the folder ID of the previous connector version (v1.1.1)
See the Note on how to obtain the folder ID.
mpoUrlMPO environment URL (for example: https://mpo-multitenant.mambuonline.com/) where the API key was generated during the MPO setup process.
new_folder_idThe identification number for the folder ID of the current connector version (v2.0.0)
See the Note on how to obtain the folder ID.
oauthUrlThe oAuth URL, which can be different for each environment used (sandbox or production). Details about the oauthUrl can be found in the Installation and configuration section from nCino Setup
secretThe connector’s secret key for the API key that is currently used and was generated during the setup process.

Mandatory post run steps

For this version, there are some steps required after successfully running the migration script.

  • Firstly, you need to run the Health Check process to verify that the data was properly copied.
  • Secondly, you need to open the new Refresh Token process from Setup > nCino Setup in the v2.0.0 connector folder. Check that the task exists and that it can be found in the Wait for timeout delay node.

Migration script from v2.2.0 to v2.3.0

To run the migration process successfully, it is necessary to have both versions - v2.2.0 and v2.3.0 - of the connector uploaded to the same Mambu Process Orchestrator (MPO) tenant.

Installation and configuration

The migration process requires the folder ID of the previous connector version (v2.2.0), the folder ID of the new connector version (v2.3.0), the MPO instance URL, and the same API key and secret used in both connectors.

MPO setup

Initial configuration

In the MPO environment, go to the Migration process folder (within the v2.3.0 connector folder) and open Start migration [main process], switch to View mode and click New task. Fill in all the required parameters and click Add task. Wait until the task is processed.

Alternatively, you can use the following JSON. Modify it and paste into the Code editor tab.

{
    "apiKey": "",
    "initial_folder_id": "",
    "mpoUrl": "",
    "new_folder_id": "",
    "secret": ""
}
ParameterDescription
apiKeyThis is the same connector API key ID generated during MPO setup. Details on where it was generated can be found at MPO Setup.
initial_folder_idThe identification number for the folder ID of the previous connector version (v2.2.0)
See the Note on how to obtain the folder ID.
mpoUrlMPO environment URL (for example: https://mpo-multitenant.mambuonline.com/) where the API key was generated during the MPO setup process.
new_folder_idThe identification number for the folder ID of the current connector version (v2.3.0)
See the Note on how to obtain the folder ID.
secretThe connector’s secret key for the API key that is currently used and was generated during the setup process.

Mandatory post run steps

For this version, there are some steps required after successfully running the migration script.

  • Firstly, you need to run the Heath check main process [manually triggered] process to verify that the data was properly copied.
  • Secondly, you need to open the new Refresh Token process from Setup > nCino Setup > Refresh Token in the v2.3.0 connector folder. Check that the task exists and that it can be found in the Wait for timeout delay node.