When Salesforce announced it was sunsetting legacy Chat, a support team that depended on it daily needed a fast, clean, invisible transition. Here's how that migration was led from audit to adoption, ahead of schedule and without disrupting a single SLA.
Salesforce announced it was sunsetting its legacy Chat feature, and for the support organization, that was a big deal. Chat handled a large volume of daily inquiries, and any disruption to it would have put SLAs and the customer experience directly at risk.
Leadership was clear about what they needed: the transition to Salesforce's Messaging platform had to be fast, clean, and invisible to customers. No dropped conversations, no degraded response times, no chaos for the agents who relied on the tool every single day.
I was asked to lead the move from Chat to Messaging. This wasn't a simple migration of flipping a switch from one tool to another. The new platform required rethinking how support flows worked, rebuilding automations from the ground up, and making sure the team could adopt the new experience without friction.
That meant owning the technical migration end to end while also owning the human side of it: making sure agents felt prepared, not blindsided, by the change.
I started by auditing the entire Chat setup, including routing logic, workflows, and automation, to understand how the system was actually supporting the team day to day. Once I had a clear picture of the dependencies, it became obvious this wasn't just a lift-and-shift. It was an opportunity to improve.
To avoid surprises at go-live, I ran multiple UAT sessions with the support team using real examples pulled from their day-to-day work. During those sessions, we surfaced a handful of edge cases and were able to resolve them quickly, well before they could become a problem in production. That gave the team real confidence the transition was going to work, not just a promise that it would.
The next thing I focused on was enablement. A technically perfect migration still fails if the people using it every day aren't ready for it. I put together quick reference guides, recorded short how-to videos, and hosted a live Q&A so agents could ask questions and raise concerns in a low-pressure setting before go-live.
The finished migration had three components:
Audited the legacy Chat configuration end to end, then simplified overly complex routing logic, removed outdated automations that no longer matched how the team worked, and introduced smarter routing rules that the old setup couldn't support.
Multiple rounds of user acceptance testing with the support team, built around real examples from their daily queues. Surfaced edge cases early and resolved them before go-live, giving the team confidence the new platform would hold up under real conditions.
Quick reference guides, short how-to videos, and a live Q&A session that gave agents a low-pressure space to ask questions and raise concerns before the switch went live.
The project rolled out smoothly and finished ahead of schedule. The team avoided any service disruption during the transition, which protected the SLAs that leadership was worried about going in.
Just as importantly, the support team transitioned without being overwhelmed. Because the rebuilt routing was simpler and smarter than what it replaced, and because agents had real preparation through UAT and enablement, the move to Messaging felt like an upgrade rather than a disruption, exactly what leadership had asked for: fast, clean, and invisible to customers.
Whether you're scaling a CRM, rescuing a troubled implementation, or looking for a Salesforce consultant to join your team, I'd love to connect.