This article explains what you need to check before moving your MIS to a cloud solution so your portal sync continues to run correctly. It covers the API domain change, the existing API key, and how email syncing is affected if your DB connection changes.
⚠️Important: If your domain changes as part of the migration, raise a support case and provide the new domain so the portal connection can be updated and tested.
Prepare for a Cloud Migration
If you are moving your MIS to a cloud solution, check whether the domain will change as part of the migration.
If the domain is changing, raise a support case and provide the new domain.
Ask support to update and test the connection so the sync continues to run successfully after the move.
Keep using the existing API key, as you do not need to create a new one for this change.
Check How Email Syncing Is Affected
Review how your portal currently syncs email addresses from iSAMS.
Confirm whether the portal can still connect to the existing DB connection, as email syncing is only available through the DB connection and is not available in the API.
If the existing server connection will no longer be available after the cloud migration, raise a support case and let the team know so this can be removed from your portal setup.
Keep in mind that any email addresses already synced from iSAMS will remain in the portal, even if the connection used to sync emails is no longer available.