Complete Premigration Steps
Learning Objectives
After completing this unit, you’ll be able to:
- Define and execute the premigration activities.
- Evaluate migration readiness.
As you prepare your client to migrate, there are a few more premigration considerations.
General Migration Behavior
An essential migration behavior to keep top of mind is anything that exists at the org level supersedes anything from the migrating workspace.
If a customer is upgrading to Enterprise Grid and is only migrating a single workspace into an empty grid, it’s considered a “lift and shift.” There will be no data conflicts and the planning is focused on downtime planning. This is as long as:
- Users aren’t preprovisioned in the empty grid. This creates users in the grid that need matching with the migrating workspace.
- Custom profile fields aren’t set up in the grid instance or the import option is set to Don’t Import.
Email cleanup is the most important task, especially if the migrating workspace wasn't previously using SSO.
Applications (Apps)
In general, Slack does not touch or make changes to the configuration of apps as part of a migration, so they’re expected to continue working as intended post migration. Apps that make use of Slack user groups APIs behave differently and are synced over as IDP groups instead. Apps using the following APIs need reauthentication.
- SCIM API
- Discovery API
- Audit Log
- Admin APIs
Use Slack Connect
Slack Connect channels are supported in grid migrations for all potential use cases. Many migrating workspaces contain at least one Slack Connect channel.
While a migration is running, Slack Connect channels and Slack Connect DMs aren't available to any of the connected organizations. The nonmigrating workspace receives a generic message indicating that the Slack Connect channel or Slack Connect DM is temporarily unavailable. This is visible on both desktop and mobile and will persist for the downtime duration of the migration.
Verified Migrations
When it comes to Slack Connect, Slack can help verify the legitimacy of organizations to help ensure that your client is working with trusted partners. When Slack verifies an organization, a purple check mark appears next to an organization’s name. The customer sees this check mark when they add someone from a verified organization to a channel in their Slack workspace, or when they accept an invite from someone at that organization.
When it comes to grid migrations of workspaces that include Slack Connect channels with verified organizations, the organization's verification status is retained in most cases. If your client is upgrading to Enterprise Grid and plans on migrating several workspaces and wants to remain verified, it’s recommended that they migrate the verified workspaces first to retain its verified status going forward.
Sum It Up
You covered the final steps before migration, including how org settings override workspace settings, migrating multiple workspaces, app behavior, and Slack Connect considerations. Now, it’s time to execute the migration, focusing on readiness, monitoring, issue resolution, and post-migration testing.