Migrating Centro Between Slack Workspaces

Overview

Moving Centro from one Slack workspace to another — for example, due to a company rebrand, subsidiary spin-off, or M&A separation — touches three systems: Salesforce, Slack, and the Centro app connecting them. This guide outlines the recommended process, common risks, and best practices.

Before You Start — Key Decisions

• Parallel run vs. full cutover: Will the old and new workspaces run side by side for a period, or is this a hard cutover? This affects licensing needs and your timeline.

• Enterprise Grid vs. individual workspace installs: On Enterprise Grid, you can install Centro at the Grid level (it propagates to all child workspaces) or install it separately per workspace and manage each implementation independently. Centro recommends installation at the workspace level.

• Preserve historical data? Decide whether you need to keep the link between historical Salesforce records (e.g., Cases) and their original Slack channels and conversations.

• Sandbox vs. Production: Confirm early whether you need to install links for both environments, to avoid rework later.

Migration Steps

1. Install Centro in the new Slack workspace.

2. Connect a dedicated automation user to the new workspace (and new Salesforce org, if that's changing too). Use a purpose-built service/system admin account rather than an individual's personal login — this avoids continuity issues later.

3. Assign Centro licenses in the new Salesforce org, if the org is also changing.

4. Migrate Slack users, channels, and messages using Slack's native Import/Export tool (Workspace Settings → Import/Export Data). Budget extra time for complications.

5. Bulk-update Slack User and Channel IDs in Salesforce — new workspace IDs won't match the IDs already stored on your Salesforce records. Please work with the Centro team on matching the new Channel Ids to the existing Channel ids if you want the history to align.

6. Update Salesforce Flows referencing Centro actions. Retrieve Flow metadata (e.g., via Salesforce CLI) and search for Centro action identifiers such as Archive Channel, Create Channel, Invite Members, Rename Channel, and Add Reaction actions to find every Flow that needs repointing.

7. Migrate Centro Forms and configuration to the new workspace. Centro Support can assist with this step.

Risks & Gotchas

• Private channels and DMs do not export or import via Slack's native tool — plan ahead for what happens to that history.

• Channel ID mismatches: if channel IDs differ between the old and new workspace, you'll need an explicit ID mapping to reconnect Salesforce records to the correct channels.

• New or added users: decide whether users added after the initial migration also need to be migrated — this can be handled on its own timeline, independent of the Centro migration itself. Users will need to authenticate their new Slack users to their existing Salesforce User. This is completed using the My Salesforce Connection in the Centro App Home or the user will be prompted if their Salesforce Connection is required.

• Automation user continuity: relying on an individual's login for automation is a common shortcut in sandbox environments that becomes a liability in production. Switch to a dedicated service account before go-live.

Best Practices

• Settle the parallel-run-vs-cutover decision and the historical-data-preservation decision before touching any systems — both affect several downstream steps.

• Treat the Slack Import/Export step as independent of the Centro migration — it can be scheduled on its own timeline.

• Use version control on any retrieved Flow metadata before making changes, so you can track exactly what changed.

• Engage Centro Support early — form migration and bulk ID remapping are things the support team can help with directly.