So the claim is a zero-downtime, one-weekend migration for 200 users from Slack to Teams. I'll admit, my immediate reaction is to ask for the bill. Not the project plan, but the actual Azure consumption spike or the AWS Data Transfer costs they conveniently left out of the "success story."
Everyone talks about the "how" but glosses over the "how much." You moved 200 users. Fine. But did you factor in the soft costs of re-training, the productivity dip in week one, and the inevitable "where's my file from 2022?" support tickets that will plague your helpdesk for months? That's the real TCO.
You mention a full breakdown. Let's see it. I'm particularly skeptical about the data migration. Did you truly migrate all channel histories, DMs, and files, or just the last 30 days to hit your weekend goal? If you did move everything, I want to see the toolchain and the storage egress costs. Using the native Microsoft migration tools? How many terabytes of file data sat in S3 or Blob Storage as a staging area, and for how long? That's not free.
And the cutover. "One weekend" implies a hard switch. What was the fallback plan when the third-party migration tool choked on your 500GB of GIFs in the #memes channel? Did you have Slack Archive access as a contingency, or were you just praying? The post-mortem on *that* meeting must be a masterpiece of avoided accountability.
I believe it's possible. I just don't believe it was as seamless or as cost-neutral as these walkthroughs typically suggest. Prove me wrong. Show me the FinOps dashboard for that month, with the unblended cost attribution for the migration project itself. Then we can talk about the "full breakdown."
- cost_observer_42
cost_observer_42
You're absolutely right to demand those numbers. The cloud egress fees alone can turn a "successful" migration into a budget nightmare the following quarter. I'd be especially interested in the final bill from their migration-as-a-service vendor, if they used one.
Your point about the productivity dip is the most critical soft cost, often excluded from ROI calculations. We tracked support ticket volume after a similar, smaller move. Tickets for "lost" files and "how do I" questions didn't peak until week two, after the initial goodwill wore off. That's when the real cost in lost seller hours hits.
And on the data scope, I'm equally skeptical. Migrating "all" files often means a broken link repository in the new system. Did they preserve the full thread context and permissions, or just dump terabytes into a single Teams-connected SharePoint library that's now unusable?
Method over hype