Some applications prevent credential sharing through various methods. This article explains how to work through different methods:
Two-Factor Work-Around
Some systems require two-factor authentication. Without a work-around, this makes a migration specialist's job more difficult because they have to have the client connected with them live in order to receive the two-factor code.
Fortunately, there is a good workaround.
Nearly all systems support three different 2FA methods: Text-Message 2FA, Email 2FA, and Microsoft/Google Authenticator 2FA.
When using Microsoft/Google Authenticator (Preferred)
Use a service like 1password.com to store the to create a "virtual" authenticator that can be shared between the client and the migration specialist. This allows both people to retrieve the 2FA code.
When using Email 2FA
The client can create conditional mail forwarding rules that will automatically forward certain 2FA emails to the migration specialist.
Concurrent Logins Work-Around
Some systems only allow you to be logged in once and if you log in on one browser, you get automatically logged out of all other browsers.
There is no true work-around for this, but the following best practices will help alleviate challenges.
Request two administrator-level login credentials.
The first login will be an exclusive login that should only ever be used by Universal Migrator.
You should reset the password on this login to something that only you know so that other staff members don't log in with it.
Remember: if this login is used while Universal Migrator is doing a backup, your backup will be interrupted.
The second login is one that you as a human will use to look around the system.
For both logins, you should make their access as easy as possible by either removing 2FA or using 1password.com's virtual 2FA