CloudMigrator will move as fast as it can, throttling and speeds are highly dependent on local resources and the source and/or destination APIs. If you wish to lower the speed of a migration (API quotas are being reached or exceeded for example), then you can manipulate your CloudMigrator configuration to do so. It is best to contact support if you require additional assistance with this.
Users are handled via "threads", the number of users migrating is entirely dependent on the APIs and number of available threads between machines. So, technically, this could be an unlimited amount of users, but the platform APIs would more than likely throttle the migration.
As many as you like! CloudMigrator is scalable and can be run across an unlimited number of servers.
This is dependent on the platforms you're migrating from/to. G Suite, for example, has API quotas which can be reached/exceeded if too many requests are made. This can then cause an exponential back-off, which results in migration speeds to drop and a possible increase in errors. Exchange/Office 365 uses EWS to migrate, which has similar quotas. API quotas can usually be topped up by a request directly to the provider.
You can run CloudMigrator as many times as you require, however, it is important to bear in mind that Email, Calendar, Tasks and Sites changes between the initial/first/bulk migration and subsequent or final/delta migrations will not be migrated. We have a recommended migration approach outlined in our KnowledgeBase.
CloudManager has a global automatic synchronization that occurs every 48 hours. This cannot be changed currently. CloudManager also performs an automatic synchronization every 24 hours for Groups & Contact changes that have been made.
Depending on the number of changes made, this time frame can vary. We expect most changes our customers make to take place between half an hour to potentially 2 hours. If you’re making large changes or have a very large organisation unity, then this can be expected to take longer.
Most changes made in CloudManager take effect immediately e.g. name changes. However, for things like email signatures or group memberships, these are involved in our global sync. Additionally, changes made on the Google platform since the last sync are also brought across, such as brand new users. (NOTE: we typically advise to create users in CloudManager to avoid this type of behavior)
Unfortunately no, this cannot be done.
Go into the OU where the email signature change was made. Open the 3-dotted menu in the top right hand side of the OU panel. You should be able to see an option on the far left in the dynamic menu saying “Sync Email Signatures”. This will start the process.
This is dependent on the number of users being affected and how much data is within the signature that needs to be pushed through to each user. We’d expect most changes to take place somewhere between 30 minutes and 2 hours.