The SaaS version of CloudM Migrate does not require complex cloud virtual machine (VM) setup or installation. Everything is provided to you with CloudM Migrate Hosted.
1. Initial Setup and Login
As part of Hosted setup, a unique customer token URL is created that identifies your instance. Opening it prompts a sign-in via Google or Microsoft.
Use the customer token URL once only, ideally. It is the long link created for your instance and is only for the first sign-in. Every login after that should go through migrate.cloudm.io. Do not bookmark or share the long link.
Important: The first person to sign in becomes the primary user of the instance, so it matters who clicks the link. It should be the intended primary migration user, using an account associated with the destination platform. Choose an account that will not change during the migration: not one that will be disabled, renamed, or have its permissions altered. A dedicated service account or an administrative account is the safest choice.
Signing in begins the initiation of your Hosted setup, which takes approximately 5 minutes. Once it is complete you are ready to go, and additional users are granted access from Advanced > Administrate. From then on, sign in at migrate.cloudm.io, not the customer token URL.
Where that infrastructure physically runs, and what it means for data residency, is covered in Choosing Your CloudM Migrate Deployment: Hosted vs. Self-Hosted.
2. Standard Login Process
Once your initial setup is complete, follow these steps to access your CloudM Migrate Hosted instance at any time:
- Navigate to the CloudM Migrate Hosted login page: https://migrate.cloudm.io/
- On the login page, select either Sign in with Google or Sign in with Microsoft.
- Authenticate using the same account you used during the initial setup.
3. Granting Access to Other Users
If you need to grant access to other team members or administrators, you can manage user access control within the platform. Once they have registered, they log in via migrate.cloudm.io; they do not need the customer token URL. For detailed instructions on adding or managing users, please refer to our knowledge base article Administrate (User Access Control).