If your CRM has been customized for years, switching systems usually feels less like a software decision and more like open-heart surgery. The hard part isn’t exporting records. It’s figuring out which workflows still matter, which customizations are just history, and what has to change before bad process gets copied into a new platform.
That’s why migration tools matter most when they help you decide what not to bring over.
Microsoft goes after Salesforce migrations
Microsoft has launched Dynamics 365 Activate, an AI-powered migration tool aimed at companies moving from Salesforce to Dynamics 365. As described by Cloud Wars, it analyzes an existing Salesforce environment and helps determine what should be moved, simplified, or redesigned.
That framing matters because Microsoft isn’t presenting migration as a bulk transfer job. It’s positioning Activate as a way to reduce lock-in by untangling years of custom processes and integrations before they’re recreated elsewhere.
- AI migration analysis. Dynamics 365 Activate is positioned to analyze a company’s Salesforce setup, including data workflows, customizations, and integrations.
- Redesign, not just copy. Microsoft says the tool maps what should be migrated, simplified, or redesigned in Dynamics 365 rather than treating every existing setup as something to replicate.
- Lower-friction switching. The stated goal is to reduce the cost, complexity, and manual effort involved in moving off Salesforce, while lowering migration risk for customers and partners.
- Broader migration plans. Microsoft said Activate starts with Salesforce-to-Dynamics moves and is planned to expand to other CRM and ERP migrations.
The real product is fewer bad carryovers
For business owners, the biggest migration risk usually isn’t technical failure. It’s faithfully rebuilding clutter. Years of exception handling, one-off fields, and workaround automations often survive because no one has time to review them one by one.
A tool that helps separate core process from accumulated noise changes the economics of switching. It can turn a migration from a lift-and-shift project into an operating-model review, where the business gets a cleaner sales process instead of the same confusion in a new interface.
It also raises the bar for CRM decisions more broadly. If vendors can make migration easier, they put more pressure on incumbents to win on current value, not on the pain of leaving.
That matters even if you never move to Dynamics 365. The practical question becomes whether your business has documented its real process well enough to evaluate any platform change without depending on institutional memory.
How Metomorph can support the migration work around the tool
This is where Metomorph fits around the migration effort itself. Imagine your team is reviewing a possible CRM move and needs one place to collect process notes, exported documentation, meeting decisions, and action items. Projects gives that evaluation a single workspace instead of scattering it across chat threads, documents, and email.
Inside that workspace, the knowledge base can hold your current playbooks, field definitions, workflow docs, and partner recommendations so discussions stay grounded in your own materials. When someone asks which approval steps are actually required versus merely historical, the assistant can answer from those documents and cite the source paragraph.
As decisions emerge, organization skills can turn repeatable review work into a standard process. A sales operations lead could create a reusable skill for reviewing each existing workflow: summarize what it does, identify dependencies, flag duplicate steps, and prepare a recommendation for keep, simplify, or retire.
That creates consistency across the migration project. Instead of every manager evaluating legacy processes differently, the team uses the same review method each time, with human approval before recommendations leave the workspace.
The result isn’t that Metomorph performs the CRM migration for you. It helps your team organize the decision-making around migration so fewer legacy habits get carried forward just because they were hard to inspect.
What to do this week
- Before considering any CRM switch, make a keep, simplify, or retire list for your current workflows. Don’t assume every customization deserves a new home.
- Centralize migration notes and source documents in one workspace early. If decisions live across inboxes and meetings, your redesign choices will drift.
- Standardize how your team reviews legacy processes. A repeatable checklist or skill is better than letting each department invent its own criteria.
- Pick one messy sales workflow and document it end to end this week. That gives you a concrete starting point for any future migration discussion.
Explore Projects, Knowledge base, Organization skills in Metomorph.
Source: Cloud Wars, Microsoft Launches Dynamics 365 Activate for AI-Powered Salesforce Migrations (September 23, 2026).