Body
You have requested your workspace to be migrated into the UNLV Enterprise Slack Organization. This article covers everything we need from you and what to expect at each stage of the process.
Updated: March 2026 | Audience: Primary Workspace Owners
What We Need From You
Please reply to your migration notification email with the following information and both file exports attached. We cannot begin analysis or schedule your migration without them.
Workspace Information
Include the following in the body of your reply email:
- Primary Workspace Owner name
- Workspace name
- Workspace ID — to find your Workspace ID, select your workspace name > Settings & administration > Workspace settings, then select the About tab. The Workspace ID is listed under the workspace name.
- PHI/HIPAA data — will this workspace be used to store, transmit, or discuss Protected Health Information (PHI) or data subject to HIPAA compliance requirements? (Yes / No)
Member List Export
We use this to identify any email address conflicts before migration. Users signed in with an email address that does not match their Okta account will need to be corrected before migration can proceed.
- Select your workspace name > Settings & administration > Manage members
- Select Export in the top-right corner of the members list
- Select Export as CSV and save the file
- Attach the CSV file to your reply email
Channels List Export
This is a self-serve export that only you can run from your own workspace.
- Select your workspace name > Settings & administration > Workspace settings
- Select the Export tab at the top of the page
- Under Channel audit report, select Export
- Save the file and attach it to your reply email
Actions to Complete Before Migration
Once we send you the workspace analysis spreadsheet, please work through the following items. We will flag specific things that need your attention in that email.
Email Conflicts — No Action Needed Yet
Some users in your workspace may be signed in with an email address that does not match their official Okta account. We know this is not always visible to you as a workspace owner. Once we run the pre-migration checklist in Slack Grid, we will identify any conflicts and send you a list of affected users with the steps needed to resolve them. No action is needed from you on this until you hear from us.
- Resolve any duplicate usernames or channel name conflicts identified in the analysis spreadsheet
- Review your custom emoji and rename or remove any that conflict with emoji already in the Grid
- Export your workspace audit logs now if you need them — these will no longer be accessible from your workspace after migration
- Make a note of any custom profile fields you have configured — these are not carried over during migration and will need to be recreated in the Grid org after migration
- Ask your workspace members to update their Slack desktop and mobile apps to the latest version before migration day
- Once the migration is scheduled, do not make further changes to workspace settings
Audit Logs Cannot Be Accessed After Migration
Workspace-level audit logs are not accessible once migration completes. If you or your team need them for compliance, legal, or historical purposes, export them before the migration window opens.
Your Role During Migration
There are three things we need from you on and around migration day.
Approve the Migration Request
Once we submit the migration request, Slackbot will send you a direct message asking you to approve it.
The migration cannot be scheduled until you approve the Slackbot request. Please action it promptly when it arrives.
Post User Notifications in #general
You will need to post two notifications to your workspace's #general channel. We will provide the copy for both.
| Notification |
When to Post |
| First notice — what is happening and when |
At least 2 weeks before migration |
| Final reminder — confirming exact timing |
1–2 business days before migration |
Assign Smoke Test Resources
On migration day, please have the following people available to run post-migration smoke tests. We will provide a checklist.
- One workspace admin
- One non-admin standard member
Key Dates & Deadlines
Specific dates will be confirmed in your migration notification email. Replace the bracketed placeholders below for each workspace cohort before publishing.
| Milestone |
Timing |
| Submit workspace information and file exports |
[DEADLINE] |
| Receive and action the workspace analysis spreadsheet |
After deadline |
| Approve migration request from Slackbot |
When received |
| Post first user notification in #general |
At least 2 weeks before migration |
| Post final user notification in #general |
1–2 business days before migration |
| Migration window |
[TARGET DATE] |
| Post-migration smoke tests |
Migration day |
Need Additional Help?
We will be scheduling a short onboarding call with each workspace owner before migration begins. In the meantime, if you have questions about your workspace migration, please submit an IT Help Desk support request.