Microsoft Dynamics 365 Activate – When Leaving Gets Cheaper, The Exit Plan Becomes The Control

Publication Record

Evidence current through: Thursday, November 19, 2026, at 12:50 a.m. UTC (7:50 p.m. ET and 4:50 p.m. PT on Wednesday, November 18), which is 12:50 a.m. UTC on Thursday, November 19, 2026.

The Salesforce migration in Dynamics 365 Activate is generally available, while its SAP ECC steps and Salesforce in Copilot are in preview, and the note reads each at the status Microsoft gave it by the time above. Developments after that time are not reflected. Times in the text are given in UTC.

Research Note In Two MinutesNote synopsis · AI drafted · Analyst reviewed

Drafted by AI from the full research note and reviewed by a Greyhound Research analyst before publication. The analysis and conclusions are Greyhound Research’s own.

At Microsoft Ignite on November 17, 2026, Microsoft made two moves on the same day that point in opposite directions. Dynamics 365 Activate, its tool for moving companies off Salesforce onto Microsoft’s own customer software, became generally available, meaning fully released. Microsoft also put the same tool’s first steps for leaving SAP ECC, SAP’s older finance and operations software, into private preview. Then, with Salesforce, it announced Copilotforce, which brings Salesforce data and actions into Microsoft Copilot for companies that stay with Salesforce.

Greyhound Research’s position is that Microsoft is selling the exit and the stay at once, and that both roads end at Copilot. For buyers, the value of Activate is less the migration than the discovery report it produces. A priced, tested plan for leaving changes every renewal conversation with Salesforce and SAP, and with Microsoft, whether or not the company ever moves. Greyhound Research reads this as the familiar economics of switching, changed at one point. The cost of finding out what leaving involves has fallen, while the cost of rebuilding what makes the old system fit the business has not, so the early gain goes to buyers who price the exit rather than those who rush it.

Three findings carry the argument. First, Microsoft has published no price for Activate, and its own words for customized software are “move, simplify, or redesign,” so much of the work is rebuilding, not moving. Second, the SAP tool is in private preview while SAP’s mainstream maintenance for ECC ends at the end of 2027, so it is a planning aid, not yet a path. Third, the speed figures behind the launch are partner forecasts and company claims, and none comes with a method.

The note sets out a ten-move Greyhound CXO Runbook, with seven exhibits, seven tables, and six questions for Microsoft. None of the moves waits on Microsoft. The first three are simple to state. Commission the discovery before the next renewal. Put the exit plan on the renewal table. Test a sample of records and processes before trusting any timeline.

The evidence has limits. Activate has no public documentation beyond Microsoft’s announcements and a partner page. Microsoft’s pages disagree on the SAP tool’s status, and Salesforce and SAP are read here only through their own announcements. Greyhound Research names the signals that would change its view within twelve months. Until they arrive, the advice holds: run the discovery, price the exit, and keep press-release timelines out of contracts.

In This Research NoteSection guide · AI drafted · Analyst reviewed

Seventeen sections in eight parts, each with a short summary. Select a title to go straight to that section. Each section opens with a Greyhound Spotlight, the one fact in it a reader would not expect, and twelve end with a block named The Deeper Read, which holds the fuller argument and the passages it rests on. Select any line in that block to open its full text.

  1. Part 1What Ignite Changed
  2. 1.1What Microsoft Announced: One Exit Released, One In Private Preview, One Way To Stay

    The Salesforce migration tool is generally available, the SAP ECC tool is in private preview, and Salesforce in Copilot is in preview. None has a published price.

  3. 1.2Two Signals At Once: Microsoft Sells The Exit And The Stay In The Same Week

    Activate moves customers off Salesforce and SAP. Copilotforce keeps Salesforce in place. Both put Copilot in front of the work, and neither has a published price.

  4. Part 2The Exit
  5. 2.1Activate For CRM: Leaving Salesforce Now Starts With A Report

    Activate reads a Salesforce estate, recommends what to keep or change, and runs the move, with people checking the result. Microsoft has written the first steps, not the price or the proof that nothing was lost.

  6. 2.2The SAP ECC Clock: A Private Preview Against A 2027 Deadline

    SAP’s mainstream maintenance for ECC ends at the end of 2027, with paid extended maintenance to 2030 and a narrow option to 2033. Microsoft’s ECC tool is in private preview.

  7. 2.3Data And Process Fidelity: Records Move, Logic Is Rebuilt

    Data records move. Custom code, workflows, and business processes are decided case by case and often rebuilt. Microsoft does not say how history and audit trails are carried.

  8. Part 3The Stay
  9. 3.1Copilotforce: Staying With Salesforce, Inside Microsoft’s Front Door

    Salesforce in Copilot lets sellers use Salesforce from Copilot under Salesforce’s own permissions. Who pays for what, and who answers for a wrong update, is not written.

  10. 3.2The Front Door: Both Doors Lead To Copilot

    Whether a company leaves Salesforce or stays, Microsoft’s plan puts Copilot where work starts. The incumbent keeps the record, or Microsoft takes it.

  11. Part 4The Money
  12. 4.1Renewal Leverage: The Discovery Report Is The Bargaining Chip

    A priced, tested exit plan changes renewals with Salesforce, SAP, and Microsoft alike, whether or not the company moves. Each vendor has its own counter-claim.

  13. 4.2The Speed Claims: Five Months Is One Customer’s Forecast

    The launch rests on five speed and scale claims from Microsoft, two partners, and SAP. None has a published method, and the largest is a forecast for a project still running.

  14. Part 5The Risks And The Counter-Argument
  15. 5.1Risks To Watch: Where A Cheaper Exit Can Still Go Wrong

    Five risks, from rules lost in the move to paying twice to stay, each with an early warning in the buyer’s own documents and an owner.

  16. 5.2The Strongest Objection: Most Companies Stay

    The fair counter-case: large CRM and ERP moves are rare, Microsoft needs Salesforce, and a vendor-built assessment favors its maker. All three hold. The conclusion that the exit plan has little value does not.

  17. Part 6What To Do, By Role
  18. 6.1The Greyhound CXO Runbook: Ten Moves Before The Next Renewal

    Ten moves for the CIO, business applications leads, procurement, the CFO, the chief data officer, enterprise architects, and the board, each naming the assumption it corrects and who decides.

  19. 6.2Questions For Microsoft: What Buyers Will Ask Next

    Six questions only Microsoft can answer, on price, the SAP timeline, what moves, where data sits during a move, coexistence licensing, and accountability. Each is tied to a Runbook move.

  20. Part 7The Final Greyhound Standpoint
  21. 7.1Dynamics 365 Activate: The Final Greyhound Standpoint

    Microsoft sells the exit and the stay, and both end at Copilot. The exit plan is the buyer’s control. The limits of the evidence, and the signals that would change the view within twelve months.

  22. Part 8Appendix, Sources, And Disclosures
  23. 8.1Appendix: The Evidence Register, Source By Source

    Every source behind this research note, with when it was read and where it is used. Passages quoted in The Deeper Read are not repeated here.

  24. 8.2Sources And References: Every Document Behind Every Claim

    Twenty-two sources in four classes, from Microsoft’s announcements to Salesforce’s, SAP’s, and other companies’ own statements, the media, and the research this note builds on.

  25. 8.3Disclosures: Independence, Financial, Intended Use, Methodology, Authoring, And Copyright

    Independence first, then the Financial Disclosure, intended use, research method and its limits, authoring, and copyright terms.

Where To Start, By RoleReader guide · AI drafted · Analyst reviewed

Part 1What Ignite Changed

What Microsoft Announced: One Exit Released, One In Private Preview, One Way To Stay

Greyhound SpotlightMicrosoft’s own partner page still called the Salesforce migration tool a limited public preview after the Book of News called it generally available.

Microsoft’s Ignite summary lists two business application moves that face in opposite directions. The first is Dynamics 365 Activate, which Microsoft calls an implementation and migration platform. Its Salesforce migration is now generally available, and its first SAP ECC steps are in private preview, a test release open only to invited customers. The second is a set of Salesforce links into Copilot, Teams, and Microsoft’s data platform, announced jointly with Salesforce.

Greyhound Research reads the release as the moment a long courtship became a product. Microsoft has pursued Salesforce and SAP customers for years with offers and partner programs, and what is different now is that the pitch comes with a released tool a buyer can run on its own estate. Greyhound Research expects a price, and possibly migration funding, to be published once the SAP steps are ready to sell, since vendors tend to set terms when a scenario is complete. The effect that is easy to miss is on paperwork. When two Microsoft pages describe one tool differently, the contract, not the web page, should record the status the buyer is paying for.

Table 1 sets each item beside its status and what Microsoft has not yet written. A pilot is a trial with a few selected customers.

Greyhound Research · Table 1 · Status ledger

One exit released, the other in private preview, and no price for either

Microsoft’s Ignite 2026 items for leaving Salesforce and SAP ECC and for staying with Salesforce, by status, November 19, 2026.

Greyhound Research’s judgment: sign only on the two released rows, and treat every preview as a roadmap until it has a price.

Generally availablePreview or pilotContext
OfferingStatusWhat Microsoft has writtenNot yet written
Dynamics 365 Activate for CRM, Salesforce to Dynamics 365Generally available“For CRM, the Salesforce migration experience is now generally available.”Public preview from September 9, 2026Price, and what converts versus what is redesigned
Activate for ERP, SAP ECC discoveryPrivate previewAnalyzes processes, configurations, customizations, and dependenciesThe Book of News says rolling out over the coming weeksRelease date, price, ECC releases and modules in scope
Activate for ERP, requirements, configuration, and data migrationPrivate previewCarries project context from assessment through implementationRelease date, price
Salesforce in CopilotPublic previewPlugin with 38+ prebuilt sales skills, under Salesforce permissionsLicensing on each side, release date
Sales Cloud in TeamsPilotPipeline, quota, deal alerts, and briefings in TeamsOpen beta later this yearLicensing, release date
Data federation, OneLake into Salesforce Data 360Generally availableQuery OneLake data from Data 360 without copying itThe reverse direction is in public previewLicensing for queries across both platforms
Dynamics 365 Sales, Customer Service, and ERP apps plugins for CopilotGenerally availableMore than 57 customer experience and more than 39 finance and operations skillsContext: the front door after a move
Entra Agent ID for agents on connected platformsRolling outAgents on eleven platforms, Salesforce Agentforce and SAP among them, receive a Microsoft identityMicrosoft says the rollout completes in DecemberContext: Microsoft’s directory across vendors
Against this: The Salesforce migration moved from public preview in September to general availability at Ignite, so the CRM half is a released product, not a roadmap.
Source: Microsoft Book of News (November 17, 2026), Dynamics 365 Blog (Teper, September 9 and November 17, 2026), Microsoft Source joint release (November 17, 2026), Microsoft Community Hub (Agent 365, November 17, 2026), Microsoft partner tools page.

Table 1 lists Microsoft’s Ignite 2026 items for leaving and staying with incumbent CRM and ERP vendors by status, and shows two generally available rows that can be signed, four previews or pilots, and no published price. Generally available: Dynamics 365 Activate for CRM, which moves customers from Salesforce, and data federation from OneLake into Salesforce Data 360. Private preview: Activate for ERP, SAP ECC discovery, and requirements, configuration, and data migration, which the Book of News says is rolling out. Public preview: Salesforce in Copilot. Pilot: Sales Cloud in Teams. Context: the Dynamics 365 Sales, Customer Service, and ERP apps plugins for Copilot, generally available, and Entra Agent ID for agents on connected platforms, rolling out to December. Statuses are as Microsoft published them through November 19, 2026.

Table 1. One exit released, the other in private preview, and no price for either. Data as of November 19, 2026. © Greyhound Research.

Only two rows can be signed with full terms today: the Salesforce migration and the data link from Microsoft’s data platform into Salesforce. The SAP tool, Salesforce in Copilot, and Sales Cloud in Teams are previews or pilots. Microsoft’s own pages also disagree on the SAP tool, which one calls private preview and another says is rolling out. Budgets should rest on the generally available rows until Microsoft publishes terms for the rest.

Greyhound Standpoint:

Greyhound Research judges that Ignite turned Microsoft’s long-running interest in Salesforce and SAP customers into a released product on one side and a promise on the other, and that buyers should plan on the two halves differently. The CRM tool is generally available, which means Microsoft stands behind it on its standard terms. The ERP tool is a private preview, which means its scope, timing, and price can still change before anyone should rely on it. Anyone who has followed enterprise software through several release cycles has seen previews narrow, slip, or change their licensing on the way to release, and that pattern is the reason to keep the two apart in a plan.

Microsoft deserves credit for releasing the Salesforce tool rather than announcing it again, and for labeling the SAP steps plainly as a preview. The limit is that Activate has no public documentation beyond announcements and a partner page, and two Microsoft pages disagree on the SAP tool’s status. A published price, a scope list, and one consistent status would move this reading toward full confidence.

Until then, business applications leads should treat the Salesforce tool as available and the SAP tool as a roadmap, and procurement should ask for the price, the status of each step, and the scope of what moves, in writing, at the first planning review that budgets for either.

The Deeper Read · About 2 minutes

Select a question to open the full answer

1What exactly did Microsoft announce for Activate?

The CRM half. Microsoft opened a public preview of Activate for companies moving from Salesforce on September 9, 2026. At Ignite, the Book of News says the Salesforce migration experience is generally available, and Jeff Teper, Executive Vice President of Microsoft Apps and Agents, writes the same.

The ERP half. The same post says requirements analysis, configuration, and data migration for SAP ECC are in private preview. The Book of News describes the ERP capabilities as starting to roll out on November 17 and continuing over the coming weeks. Microsoft’s partner page, read on November 18 and again on November 19, still describes a limited public preview of the Salesforce tool. In September, Teper wrote that Salesforce was the first migration scenario, with further CRM and ERP scenarios to follow.

What the partner page tells a buyer. A partner page that still says limited public preview after the Book of News says generally available is most likely a page not yet updated, not a change of plan. It still matters, because partners scope and price work from their own pages. A buyer should confirm with Microsoft and with the partner that the statement of work rests on the released product and its standard terms.

In the source’s own words

  • Microsoft’s Book of News, Dynamics 365 ActivateFor CRM, the Salesforce migration experience is now generally available.Source
  • Microsoft’s Book of News, Dynamics 365 Activatewhich start rolling out today and continue over the coming weeksSource
  • Dynamics 365 Blog, Teper on November 17Requirements analysis, configuration, and data migration are also available in private previewSource
  • Microsoft partner tools pagePartners can sign up to the limited public previewSource
  • Dynamics 365 Blog, Teper on September 9Salesforce is our first migration scenario, with additional CRM and ERP migration scenarios to follow.Source
2What exactly did Microsoft and Salesforce announce together?

Three links. The joint release describes Salesforce in Copilot as a plugin in public preview with more than 38 prebuilt sales skills, says Sales Cloud in Teams is in pilot with open beta later this year, and says data federation from Microsoft OneLake into Salesforce Data 360 is generally available. Data sharing in the other direction, from Data 360 into OneLake, is in public preview.

The name. The release calls the partnership Copilotforce. Salesforce used the same pattern in August, when it announced Claudeforce with Anthropic.

In the source’s own words

  • Microsoft Source, joint release, November 17Salesforce in Copilot is available in public preview (beta) beginning today.Source
  • Microsoft Source, joint release, November 17Sales Cloud in Teams is in pilot with enterprise customers, with open beta coming later this year.Source
  • Microsoft Source, joint release, November 17Data federation from Microsoft OneLake into Salesforce Data 360 is generally availableSource

↑ Back to the section guide

Part 1What Ignite Changed

Two Signals At Once: Microsoft Sells The Exit And The Stay In The Same Week

Greyhound SpotlightOn the same day, Microsoft issued a joint release with Salesforce and promoted a tool for moving customers off Salesforce.

A buyer reading Ignite could take away two opposite messages. One says leave Salesforce and SAP for Microsoft’s own business software. The other says keep Salesforce and reach it through Microsoft Copilot. Both are true at once, and they are not a contradiction. Microsoft wins something either way, and the buyer’s job is to see what.

For buyers, the practical meaning is that the vendor across the table now sells both outcomes, so its account team gains whichever way the decision goes. That is a change from the classic CRM contest, in which a rival’s pitch was simply to win the record. Competing and partnering at once is old in enterprise software, from databases that ran on rivals’ hardware to applications sold through rivals’ clouds. The likely next step, in Greyhound Research’s view, is for similar pairings to appear between other assistants and other systems of record. The consequence that gets less attention is internal. Two roads invite two sponsors inside the buyer, and without one owner a company can end up funding both.

Exhibit 1 sets the three offerings against what each does to the software a company already runs. The incumbent is the vendor a company uses today. A system of record is the software that holds the official version of the data.

Greyhound Research · Exhibit 1 · Two signals, one front door

Every road keeps Copilot in front of the work

What each of Microsoft’s three Ignite 2026 business application offerings does to the CRM or ERP software a company already runs.

Greyhound Research’s judgment: the real choice is who holds the record, because Copilot takes the front door on every road.

YesIn previewNot publishedNoCRM Activate for CRM · ERP Activate for ERP · CF Copilotforce
What it does to the incumbent
Activate for CRM
Activate for ERP
Copilotforce
1Reads and maps the incumbent estate
CRMYes
ERPIn preview
CFNo
2Moves data off the incumbent
CRMYes
ERPIn preview
CFNo
3Keeps the incumbent as the system of record
CRMNo
ERPNo
CFYes
4Puts Copilot in front of the work
CRMYes
ERPYes
CFIn preview
5Has a published price
CRMNot published
ERPNot published
CFNot published
Against this: Copilotforce leaves Salesforce’s permissions in charge of every record and action, so the front door does not decide what a user may do.
Source: Greyhound Research analytical model, not measured data. Greyhound Research reading of Microsoft’s Book of News, Dynamics 365 Blog, and the Microsoft and Salesforce joint release.

Exhibit 1 is a matrix of five effects against three offerings, Activate for CRM, Activate for ERP, and Copilotforce, and shows that all three keep Copilot in front of the work while none has a published price. Reads and maps the incumbent estate: yes for Activate for CRM, in preview for Activate for ERP, no for Copilotforce. Moves data off the incumbent: the same. Keeps the incumbent as the system of record: only Copilotforce. Puts Copilot in front of the work: yes for both Activate offerings, through the Dynamics 365 plugins, and in preview for Copilotforce. Has a published price: not published for any of the three, shown as a tinted row. The marks are Greyhound Research analysis, not measured data.

Exhibit 1. Every road keeps Copilot in front of the work. Current through November 19, 2026. © Greyhound Research.

Each road keeps Copilot in front of the work. Activate replaces the system of record with Microsoft’s, while Copilotforce leaves Salesforce’s in place and puts Copilot in front of it. None of the three has a published price. The exhibit is Greyhound Research’s reading of each company’s announcements, not a vendor claim. It shows that the choice is less between Microsoft and Salesforce than over who owns the record behind the front door.

Greyhound Standpoint:

At Greyhound Research, we believe the two signals are one strategy, and that reading them as a contradiction would lead buyers to the wrong question. Microsoft wants Copilot to be where work starts. It can get there by replacing the incumbent’s record with Dynamics 365, or by sitting in front of Salesforce’s record through Copilotforce, and it gains on either road. That is not unusual. Large platform vendors have long competed with a rival in one product line while partnering with it in another, and customers have done best when they handled each relationship on its own terms. The arrangement also reflects well on Salesforce, which keeps its record and its permissions in place while reaching users where they already work.

The consequence for buyers is that two decisions which used to travel together now come apart: which system holds the record, and which tool is the front door. Each carries its own price, its own contract, and its own exit. The reading rests on the companies’ announcements, and neither company has published prices that would show how the two roads compare in cost. The view would change if published terms tied the front door to the record, because the two choices would then travel together again.

CIOs should take the record decision and the front door decision as two separate items at the next architecture review, rather than letting one renewal settle both.

The Deeper Read · About 1 minute

Select a question to open the full answer

1How does each offering treat the incumbent?

Replace it. Microsoft describes Activate for CRM as helping customers migrate from Salesforce to Dynamics 365, and Activate for ERP as starting with SAP ECC. Both end with Dynamics 365 as the system of record, and Microsoft calls Copilot the new front door to Dynamics 365.

Sit in front of it. Under Copilotforce, Salesforce stays the system of record. The joint release says Salesforce continues to govern access and business actions, and the Book of News says sellers work within their existing Salesforce permissions.

In the source’s own words

  • Dynamics 365 Blog, Teper on November 17We began with Dynamics 365 Activate for CRM (generally available), helping customers migrate from Salesforce to Dynamics 365.Source
  • Dynamics 365 Blog, Teper on November 17Copilot is the new front door to Dynamics 365 and plugins make Copilot work for your business.Source
  • Microsoft Source, joint release, November 17Salesforce continues to govern access and business actionsSource
2Does Microsoft also help customers keep SAP?

Yes, on Azure. The Book of News lists Azure Workload Center, in preview, to extend agentic operations to Oracle and SAP. SAP names Microsoft among the partners for agent-to-agent links between Joule, SAP’s assistant, and outside agent frameworks. Microsoft offers agentic operations for SAP on Azure to some customers and a way off SAP to others.

What the hedge tells a buyer. Microsoft offers SAP customers a way to run on Azure and a way to leave, and offers Salesforce customers a way to stay and a way out. A vendor that sells every road is signaling that the road itself is open to negotiation. The buyer’s leverage lies in deciding which road it is on before the account team proposes one.

In the source’s own words

  • Microsoft’s Book of News, Azure agentic operationsextend agentic operations to Oracle and SAP through Azure Workload CenterSource
  • SAP News Center, May 12, 2026enabling bidirectional agent-to-agent interoperability between Joule and external agent frameworksSource

↑ Back to the section guide

Part 2The Exit

Activate For CRM: Leaving Salesforce Now Starts With A Report

Greyhound SpotlightMicrosoft has not published a price for Activate in any document read for this note.

Moving a company off one CRM onto another has usually started with months of discovery. Consultants list every data object, custom field, workflow, and connection before anyone can say what the move will cost. Activate does that first pass with AI agents and hands the result to the project team. The output is a report on the company’s own estate, and that report has value of its own.

What is new is who pays for the first look. Discovery has usually been sold as the opening phase of a migration contract, so a company had to half commit before it could see the cost. A tool from the destination vendor moves that look earlier, to the point where a buyer is still deciding. Greyhound Research anticipates that other application vendors will answer with assessment tools of their own, since none will want a rival to hold the only map of its customers’ estates. A less obvious effect falls on partners. If the first pass is automated, partner value shifts toward judgment and redesign, and statements of work should be priced that way.

Exhibit 2 follows Activate’s steps from reading the Salesforce estate to proving the move worked, and marks which ones Microsoft has written down. Configuration means setting up the new system’s options and rules.

Greyhound Research · Exhibit 2 · The path of a Salesforce move

Microsoft has written the first steps and left out the proof

Five steps of a move from Salesforce to Dynamics 365 with Activate, read against Microsoft’s announcements, November 19, 2026.

Use the discovery now. Do not sign off a move until the buyer holds its own proof that nothing was lost.

Written by MicrosoftPartly writtenNot written
1Discover WrittenRead the Salesforce estate and map itWritten. Profiles data and entities, maps relationships and dependencies, flags customizations.Open. Whether the buyer owns and can export the report.
2Recommend WrittenDecide what to keep, simplify, or redesignWritten. Helps teams decide what to preserve, simplify, or redesign.Open. How the recommendations weigh staying on Salesforce.
3Configure and move WrittenSet up Dynamics 365 and move the dataWritten. Automated migration with built-in guardrails, in a Microsoft-hosted experience.Open. Where the data sits during the move, and for how long.
4Validate Partly writtenPeople check the work before go-liveWritten. Validation by implementation project teams.Open. What the team checks, and against which acceptance criteria.
5Reconcile and price Not writtenProve nothing was lost, and know the costWritten. None in the documents read.Open. A reconciliation report and a published price.
Against this: Microsoft says Activate processed over six billion records in early engagements, and Comcast credits its discovery with a clearer view of its Salesforce estate, so the first steps are in use.
Source: Greyhound Research analysis of the Dynamics 365 Blog (Teper, September 9 and November 17, 2026) and Microsoft’s Book of News. The steps and grades are Greyhound Research’s.

Exhibit 2 sets out five steps of a move from Salesforce to Dynamics 365 with Activate as a numbered list, and shows that Microsoft has written the first three, part of the fourth, and not the fifth. Step one, discover, is written: Activate profiles data, maps dependencies, and flags customizations. Step two, recommend, is written. Step three, configure and move, is written as automated migration with built-in guardrails in a Microsoft-hosted experience. Step four, validate, is partly written, as validation by implementation project teams without stated criteria. Step five, reconcile and price, is not written in any document read. The steps and grades are Greyhound Research analysis.

Exhibit 2. Microsoft has written the first steps and left out the proof. Current through November 19, 2026. © Greyhound Research.

Microsoft has written the first steps clearly. The tool reads the estate, recommends what to keep or change, and runs the move with what it calls built-in guardrails. People on the project check the work. The last step is missing from every document read. No Microsoft page says how a buyer proves that records, rules, and history arrived intact, or what the tool costs.

Greyhound Standpoint:

Greyhound Research holds that the discovery report is the most valuable thing Activate produces, and that buyers should commission one whether or not they intend to move. The reason is economic. The first months of a CRM project have usually gone to consultants listing objects, fields, workflows, and integrations, and that cost has kept many companies from pricing an alternative at all. A tool that does the first pass at lower cost turns an expensive question into an affordable one. The migration itself deserves more caution. A familiar pattern from the move of customer software to the cloud is that record counts reconciled at go-live while reports, approvals, and integrations revealed gaps weeks later.

Microsoft deserves credit for writing the early steps clearly and for keeping people on the project in the review. What its documents do not yet show is how a buyer proves that records, rules, and history arrived intact, or what the tool costs. A vendor-built assessment also reflects its maker’s view of the destination, so a second reviewer who does not sell Dynamics 365 is a sensible check. A published reconciliation method would strengthen the case for the move itself.

Business applications leads should require a written reconciliation of every record and rule before signing off any move, and should treat the stated guardrails as a claim to test at the pilot gate.

The Deeper Read · About 2 minutes

Select a question to open the full answer

1What does Activate do, step by step?

Discovery and recommendations. Microsoft’s September post says Activate analyzes an existing Salesforce CRM environment, profiles data and entities, maps relationships and dependencies, and flags customizations that need attention. It then helps teams decide what to preserve, simplify, or redesign.

The move. The same post describes automated migration execution with built-in guardrails in a Microsoft-hosted experience. The Book of News says Activate is built on Success by Design, Microsoft’s implementation method, and that project context carries forward from assessment through implementation.

In the source’s own words

  • Dynamics 365 Blog, Teper on September 9It will analyze an existing Salesforce CRM environmentSource
  • Dynamics 365 Blog, Teper on September 9automated migration execution with built-in guardrailsSource
  • Microsoft’s Book of News, Dynamics 365 ActivateDynamics 365 Activate is built on Success by Design, Microsoft's implementation methodology.Source
2What does a named customer credit?

The discovery. Microsoft’s September post says Comcast wanted to accelerate its migration assessment and gain a clearer view of its Salesforce landscape. Sathish Arumugam, Manager, Software Dev and Engineering at Comcast, credits the discovery capabilities with greater visibility into that landscape and with more informed planning decisions. The quote speaks to the assessment and the plan, not to a completed move, which is the part of Activate this note values most.

What a discovery quote tells a buyer. The named customer credits visibility and planning, which is the part of Activate a buyer can test without committing to a move. The quote says nothing yet about cost, duration, or what arrived intact. A buyer should read the reference the same way, as evidence that the discovery is in use at a large company, and ask for a reference that has completed a move before relying on the migration itself.

In the source’s own words

  • Comcast’s Sathish Arumugam, Dynamics 365 Blog, September 9Dynamics 365 Activate's discovery capabilities helped accelerate our migration assessmentSource
  • Comcast’s Sathish Arumugam, Dynamics 365 Blog, September 9The insights enabled our teams to make more informed planning decisionsSource
3Who checks the work?

People, by Microsoft’s account. Teper’s Ignite post says Activate brings agentic capabilities to the work, with validation by implementation project teams. A partner quoted in September says its approach is human-led and AI-accelerated. Greyhound Research’s October note on Oracle’s agentic implementation held that the person who signs off agent-drafted configuration is signing off authority, and the same applies here.

In the source’s own words

  • Dynamics 365 Blog, Teper on November 17Activate brings agentic capabilities to that work, with validation by implementation project teams.Source
  • Dynamics 365 Blog, partner quote, September 9Human-led, AI-accelerated is core to how we operate at congruentX.Source
  • Greyhound Research, Oracle agentic implementation notethe person who signs off the configuration is signing off the authoritySource

↑ Back to the section guide

Part 2The Exit

The SAP ECC Clock: A Private Preview Against A 2027 Deadline

Greyhound SpotlightSAP’s option to run ECC until 2033 is not a later deadline for everyone. SAP calls it not a prolongation, and ties it to a move under RISE with SAP.

SAP ECC runs finance, supply chain, and manufacturing for many of the world’s large companies. SAP has said since 2020 that mainstream maintenance, its standard support and updates, ends for ECC’s current releases at the end of 2027. After that, customers can pay for extended maintenance to the end of 2030. SAP wants them to move to S/4HANA, its newer system, and offers its own tools to help.

For most ECC customers the clock matters more than the tool. End-of-support dates have long shaped ERP spending, and the familiar pattern is a late rush in which partner capacity, not software, sets the pace and the price. A second destination with an agent-assisted path could ease some of that pressure, though only once it leaves preview. Greyhound Research expects demand for experienced ECC teams to tighten as 2027 approaches, whichever destination companies choose. The point that tends to be overlooked is that the decision and the move are separate events. A company can settle its destination this year and still need the paid years after 2027 to finish the work.

Exhibit 3 sets SAP’s dates and Microsoft’s Activate steps on one calendar, from SAP’s 2020 decision to the end of its narrow 2033 option. Extended maintenance is paid support after standard support ends.

Greyhound Research · Exhibit 3 · The SAP ECC clock

Microsoft’s ECC tool arrives a year before the first deadline

SAP’s maintenance dates for SAP ECC and Microsoft’s Activate steps, on one calendar, 2020 to 2033.

Too late to finish a move before 2027, early enough to price the choice. Use it to decide, not yet to migrate.

A date or decision fell in this yearDates as SAP and Microsoft published them
2020SAPSets end of 2027 and end of 2030
2021Quiet
2022Quiet
2023Quiet
2024SAPCommits to S/4HANA until 2040
2025SAPAdds a 2031 to 2033 option for RISE customers
2026BothSAP agent tooling in May. Activate CRM in September. ECC preview in November
2027DeadlineMainstream maintenance ends
2028Quiet
2029Quiet
2030DeadlineExtended maintenance ends
2031 to 2033OptionTransition option, on conditions
2033 option: RISE with SAP, SAP ERP private edition by end of 2030, SAP HANA onlyActivate for ERP: private preview, no release date
Against this: Extended maintenance to 2030 and the 2033 option give many ECC customers more time than the headline date, at a price and on SAP’s terms.
Source: SAP News Center (October 30, 2024, RISE with SAP updated March 7, 2025, and May 12, 2026), SAP spokesperson (January 28, 2025), Dynamics 365 Blog (Teper, September 9 and November 17, 2026).

Exhibit 3 places SAP’s ECC dates and Microsoft’s Activate steps on a grid of years from 2020 to 2033, and shows Microsoft’s ECC tool reaching private preview in November 2026, a year before the end of 2027. In 2020 SAP set the end of 2027 for mainstream maintenance and the end of 2030 for extended maintenance. In 2024 SAP committed to S/4HANA until 2040. In 2025 it added a transition option for 2031 to 2033 for RISE with SAP customers. In 2026 SAP introduced agent-led migration tooling in May, Microsoft opened Activate for CRM in September, and Activate for SAP ECC reached private preview in November. Mainstream maintenance ends in 2027, extended maintenance in 2030, and the transition option runs from 2031 to 2033 on conditions. Years without an event are marked quiet.

Exhibit 3. Microsoft’s ECC tool arrives a year before the first deadline. Data as of November 19, 2026. © Greyhound Research.

The calendar is tight for anyone moving off ECC to Microsoft. Microsoft’s tool reached private preview in November 2026, a little over a year before mainstream maintenance ends. Microsoft’s own partner puts a typical CRM move at 12 to 18 months, and a large finance system is rarely simpler, so the tool cannot carry a full move before the 2027 date. It can help a company decide where to go, and price the choice. The dates after 2027 give more time, at a price and on SAP’s conditions. Greyhound Research said in January 2026, of an earlier short SAP extension, that “This is a transition period, not a reprieve,” and that reading holds for ECC’s later dates too.

Greyhound Standpoint:

Greyhound Research’s reading is that Activate for ERP arrives too close to the end of 2027 to carry a full move off ECC before that date, and early enough to shape the decision about where to go. Large ERP moves take years rather than quarters, and a preview opened a little over a year before mainstream maintenance ends does not change that. SAP deserves a fair hearing. It has stated its ECC dates in public since 2020, offers paid extended maintenance to the end of 2030, has committed to S/4HANA until 2040, and offers its own migration tooling. Those are real options, and for many companies staying with SAP will be the sound choice.

The 2031 to 2033 option is narrower, tied to RISE with SAP and a move to SAP ERP, private edition, and SAP itself says it is not a prolongation. The longer view is that end-of-support dates in enterprise software have tended to arrive with paid extensions and a range of support options rather than a single cliff, and buyers who priced every path early have negotiated from a stronger position. The evidence limit is that Microsoft’s ECC scope is unpublished. A dated general availability and a module list would raise the tool’s weight.

CFOs and CIOs should price three paths side by side before the 2027 budget is set: extended maintenance on ECC, S/4HANA with SAP, and Dynamics 365, with any preview date in writing.

The Deeper Read · About 2 minutes

Select a question to open the full answer

1What exactly has SAP said about ECC dates?

2027 and 2030. SAP’s October 2024 post gives the end of 2027 for mainstream maintenance of the latest three enhancement packages of the Business Suite 7 core applications and 2030 for the extended maintenance option, and commits to S/4HANA until 2040. SAP said in January 2025 that the dates are the end of 2027 for SAP Business Suite 7 and the end of 2030 for extended maintenance.

2031 to 2033. SAP’s February 2025 post, updated in March 2025, describes a transition option active from 2031 to 2033, designed for large customers with complex installations on a RISE with SAP journey. Systems must be moved to SAP ERP, private edition, before the end of 2030, and SAP HANA is the only supported database. The post says this is not a maintenance prolongation of SAP ERP, and SAP said in January 2025 that the option is not a prolongation of the 2020 deadlines.

What the wording tells a buyer. SAP has said in two places that the later option is not a prolongation. That is a careful choice of words, and a buyer should take it at face value. The option is a conversion path with conditions, a move under RISE with SAP and a single supported database, not extra time on today’s system. A plan that counts on 2033 should start from those conditions.

In the source’s own words

  • SAP News Center, October 30, 20242030 for the extended maintenance optionSource
  • SAP spokesperson, January 28, 2025the end of 2027 for SAP Business Suite 7 and the end of 2030 for extended maintenance.Source
  • SAP spokesperson, January 28, 2025not a prolongation of the mainstream maintenance deadlines communicated in 2020.Source
  • SAP News Center, February 4, 2025, updated March 7, 2025need to be moved to SAP ERP, private edition prior to the end of 2030Source
  • SAP News Center, February 4, 2025, updated March 7, 2025this is not a maintenance prolongation of SAP ERPSource
  • SAP News Center, October 30, 2024SAP also announced a commitment to SAP S/4HANA until 2040.Source
2What do Microsoft and SAP each offer ECC customers?

Microsoft’s tool. The Book of News says SAP ECC discovery will identify migration complexity, potential gaps, and areas that need further evaluation. Teper ties the launch to SAP ECC approaching the end of mainstream maintenance.

SAP’s own tool. In May 2026 SAP introduced agent-led transformation tooling that it says can reduce ERP migration effort by more than 35 percent, and said ECC customers are not excluded from select AI scenarios if they commit to moving most of their landscape to SAP Cloud ERP. Both claims are SAP’s own, without a published method.

In the source’s own words

  • Microsoft’s Book of News, Dynamics 365 ActivateIt will identify migration complexity, potential gaps and areas that need further evaluationSource
  • SAP News Center, May 12, 2026SAP also introduced new agent-led transformation tooling that can reduce ERP migration efforts by more than 35 percentSource
  • SAP News Center, May 12, 2026transitioning the majority of their current landscape to SAP Cloud ERPSource

↑ Back to the section guide

Part 2The Exit

Data And Process Fidelity: Records Move, Logic Is Rebuilt

Greyhound SpotlightMicrosoft’s own words for customized software are “move, simplify, or redesign.” Only the first of the three is a migration.

Fidelity is whether the new system does what the old one did, with the same data. Records such as accounts, contacts, and invoices can be copied. The rules around them cannot. Custom fields, automated workflows, approval chains, and code written for one vendor’s platform have to be rebuilt in the other’s. That is where migrations run late and where business users notice what went missing.

This is where the budget is decided. A migration plan that counts records looks complete well before the work is understood, because records are the easiest layer to measure. Earlier waves of consolidation, from mainframes to client-server and from on-premises software to the cloud, each showed that the rules hidden in workflows and custom code took longest to surface. Greyhound Research’s expectation is that migration tools will grow better at reading that logic before they grow better at rebuilding it. The second-order effect concerns knowledge. Many custom rules were written by people who have since moved on, so a migration is also the moment a company learns which of its own rules it no longer understands.

Exhibit 4 follows the layers of a CRM or ERP estate, from data records to history and audit trails, and marks where Microsoft’s announcements place Activate. An audit trail is the record of who changed what, and when.

Greyhound Research · Exhibit 4 · What moves and what is rebuilt

Records move, and the logic around them is rebuilt

The layers of a CRM or ERP estate, marked by what Microsoft’s announcements say Activate moves, November 19, 2026.

Budget for the logic, not the records. The rebuild, not the data load, decides what a move costs.

Moved, per MicrosoftDecided case by caseNot stated
Records and configurationMoved, per MicrosoftData migration into Dynamics 365, with project context carried forward.
Customizations and integrationsMove, simplify, or redesignMicrosoft leaves the choice to the project team.
Workflows and processesMove, simplify, or redesignThe rules that make the old system fit the business.
History and audit trailNot statedWho changed what, and when, in the old system.
Against this: Microsoft says Activate assesses objects, workflows, code, and integrations, so the decisions about logic start from a full list.
Source: Greyhound Research analysis of Microsoft’s Book of News and the Dynamics 365 Blog (Teper, September 9 and November 17, 2026).

Exhibit 4 follows the layers of a CRM or ERP estate along a bar from data to logic and history, in six layers: data records, objects and configuration, customizations and code, integrations, workflows and business processes, and history and audit trail. A marker labeled what moves sits at the end of the first two layers, which Microsoft says Activate moves. Customizations, integrations, and workflows are marked as decided case by case, since Microsoft says organizations must decide what to move, simplify, or redesign. History and audit trail are marked not stated. A strip beneath groups the layers into four. Not stated is not the same as not handled. The mapping is Greyhound Research analysis.

Exhibit 4. Records move, and the logic around them is rebuilt. Current through November 19, 2026. © Greyhound Research.

Microsoft says Activate reads the whole estate and moves data. For customizations, integrations, and business processes, its own Ignite post leaves the choice to the project: move, simplify, or redesign. History and audit trails are not mentioned in any document read. Not stated is not the same as not handled. A buyer should still assume that the logic of the old system will be rebuilt, and test it.

Greyhound Standpoint:

Greyhound Research’s position is that a migration’s speed is set by its data and its cost by its logic. Activate will make the first faster. The second remains a design project, and Microsoft’s own wording, move, simplify, or redesign, says as much. The mechanism is plain. Records are standard objects that a tool can map and copy. Workflows, approval chains, and custom code record how one company chose to work on one vendor’s platform, and each rule has to be understood before it can be rebuilt or retired. That is where budgets drift, because the rebuild can be sized only after the discovery has been read.

Consolidation cycles over three decades show a consistent shape, in which the data moves in weeks and the business logic takes most of the year. There is also an upside. A forced review of customizations is a rare chance to retire rules that no longer earn their cost, and a cleaner estate is worth having on any platform, including the one the company already runs. The limit is that Microsoft has not said how history and audit trails are carried, and not stated is not the same as not handled. Published conversion scope would change the estimate.

Business applications leads should classify every customization as move, simplify, redesign, or retire, and reconcile a sample of records, workflows, and history on real data at the pilot gate, before any timeline is committed.

The Deeper Read · About 2 minutes

Select a question to open the full answer

1What does Microsoft say moves, and what is decided?

Moves. The Book of News says data migration will help move data from existing systems into Dynamics 365. Microsoft’s September post says Activate processed over six billion data records in early customer engagements, a company figure without a stated accuracy rate.

Decided. For ERP, Teper’s Ignite post says that as SAP ECC approaches the end of mainstream maintenance, organizations must decide which customizations, integrations, and business processes to move, simplify, or redesign. The image description on the September post names Salesforce objects, workflows, code, and integrations among the things Activate assesses.

What volume without accuracy tells a buyer. Six billion records shows the tool has run on large estates. It does not show how many records arrived unchanged, or how many rules came with them. The wording that follows, move, simplify, or redesign, is the more useful line for a budget, because it says where the decisions and the cost will sit.

In the source’s own words

  • Microsoft’s Book of News, Dynamics 365 ActivateData migration will help move data from existing systems into Dynamics 365.Source
  • Dynamics 365 Blog, Teper on September 9processed over six billion data recordsSource
  • Dynamics 365 Blog, Teper on November 17As SAP ECC approaches the end of mainstream maintenance, organizations must decide which customizations, integrations, and business processes to move, simplify, or redesign.Source
2Why does the governance of data matter in a move?

Concentration risk. Greyhound Research’s May 2025 note on Salesforce’s Informatica deal cited Greyhound CIO Pulse 2025, in which 58% of enterprise technology leaders globally classify vendor concentration of data governance capabilities as a Tier-1 architectural risk when building their AI platforms. A migration moves that concentration from one vendor to another unless the buyer keeps the data rules in its own hands.

Lock-in, measured. Greyhound Research said in December 2025 that Salesforce customers face “behavioral lock in created by layered dependency over time,” not technical lock-in where migration is impossible. That view stands. What has changed since is the cost of measuring the dependency: Activate lowers the cost of mapping it, while the rebuild the map reveals is as large as before. The title of this note means exactly that, and no more. Leaving gets cheaper to price, not cheap to do.

In the source’s own words

  • Greyhound Research, Salesforce and Informatica note58% of enterprise technology leaders globally now classify ‘vendor concentration of data governance capabilities’ as a Tier-1 architectural risk when building their AI platformsSource

↑ Back to the section guide

Part 3The Stay

Copilotforce: Staying With Salesforce, Inside Microsoft’s Front Door

Greyhound SpotlightSalesforce built the same arrangement with Anthropic in August, as Salesforce in Claude. Greyhound Research reads that as a plan to sit inside every assistant.

For companies that stay with Salesforce, Copilotforce brings Salesforce into the tools staff already use. A seller can ask Copilot about an account, see Salesforce data beside their email and meetings, and update a record without opening Salesforce. Data can also be read across Microsoft’s and Salesforce’s data platforms without copying it, which the companies call zero copy.

The arrangement reflects a change in how integrations reach the buyer. Connecting two vendors’ products used to be a customer project, built by a partner and owned by the buyer. Here the two vendors have built the link themselves and announced it jointly, which shortens the work and also places part of the governance with them. In Greyhound Research’s view, the commercial terms, more than the technology, are likely to decide how widely it is used once it leaves preview. Less visible is the effect on data agreements. Reading data across two platforms without copying it is cleaner, but each query then crosses two sets of terms, and the buyer’s agreements should name both.

Table 2 sets out who governs each part of the arrangement, according to the companies’ own announcements. Writeback means an action that changes a record in Salesforce.

Greyhound Research · Table 2 · Coexistence ledger

The access rules are written, and the money and the blame are not

Who governs each part of Salesforce in Copilot and the Microsoft and Salesforce links, as the two companies announced them, November 19, 2026.

Sound access design, with the money and the blame unwritten. Settle who pays and who answers before the pilot widens.

WrittenPartly writtenRolling outNot written
Part of the arrangementWho governs itWhat is writtenStatus
What a seller can see in SalesforceSalesforce“within their existing Salesforce permissions”Written
Updates made from CopilotSalesforce, with the userSalesforce governs actions, and each update needs explicit user confirmationWritten
Context from Teams, Outlook, and documentsMicrosoftWork IQ adds context under Microsoft’s compliance controlsWritten
Regions and customer accessEach customer’s agreementsGoverned by applicable customer agreementsPartly written
Identity of agents on connected platformsMicrosoft EntraAgents on eleven platforms, Salesforce Agentforce and SAP among them, receive an Entra Agent ID, rolling out to DecemberRolling out
Licenses needed on each sideNot statedNeither company says what a seller needsNot written
Who answers for a wrong updateNot statedNo joint term on writeback errorsNot written
Against this: Keeping Salesforce’s own permissions behind Copilot is the right design, and each update needs a person to confirm it.
Source: Microsoft Book of News (November 17, 2026), Microsoft Source joint release (November 17, 2026), Microsoft Community Hub (Agent 365, November 17, 2026).

Table 2 lists seven parts of the Copilotforce arrangement, who governs each, and what is written, and shows that access rules are written while licensing and accountability for a wrong update are not. Salesforce governs what a seller can see, under existing Salesforce permissions. Updates made from Copilot are governed by Salesforce and need explicit user confirmation. Context from Teams, Outlook, and documents is governed by Microsoft. Regions and customer access are left to each customer’s agreements. Identity for agents on connected platforms comes from Microsoft Entra, rolling out to December. The licenses needed on each side and who answers for a wrong update are not written. The grading is Greyhound Research’s reading of the two companies’ announcements.

Table 2. The access rules are written, and the money and the blame are not. Data as of November 19, 2026. © Greyhound Research.

The access rules are clear. Salesforce decides what each user can see and do, and every update needs the user to confirm it. What is missing is commercial and legal. Neither company says which licenses a seller needs on each side, or who is accountable when an update goes wrong. The arrangement also sits inside preview terms, and regional access is left to each customer’s agreements.

Greyhound Standpoint:

Greyhound Research’s judgment is that Copilotforce is good news for Salesforce customers whose staff work mainly in Microsoft’s tools, and that its full cost is not yet visible. The design deserves credit on both sides. Salesforce keeps its own permissions and remains the system of record, every update needs a person to confirm it, and data can be read across the two platforms without being copied. That is what buyers have asked of integrations for decades: reach without a second copy of the truth. The open question is commercial. When two vendors share a user, each has a license to sell, and experience with suite integrations suggests the combined price is often settled after the pilot, once use has already grown.

A seller who carries Copilot and Salesforce licenses for the same work could be paid for twice, and neither company has yet said what a seller needs on each side or who answers when an update goes wrong. Salesforce’s parallel arrangement with Anthropic is a fair sign that it intends to give customers a choice of assistant rather than tie them to one. The arrangement is in preview, so its terms may change, and published licensing at general availability would settle the main question.

Procurement should ask both companies, in writing, for the combined price per seller at general availability, and business applications leads should pilot with a defined group and measure use before the rollout decision.

The Deeper Read · About 2 minutes

Select a question to open the full answer

1What exactly does Copilotforce do?

In Copilot. The Book of News says users can retrieve customer information and take supported actions within their existing Salesforce permissions, with Work IQ adding relevant context from Teams meetings, Outlook emails, and documents. The joint release says supported writeback actions require explicit user confirmation.

In Teams and the data platforms. Sales Cloud in Teams shows pipeline and quota progress, deal notifications, and briefing materials. Data federation lets joint customers query OneLake data from Data 360 while leaving the source data in Fabric, Microsoft’s data platform.

The first large user. The joint release names Accenture as design and implementation partner and as pilot customer, deploying the integrations in its own global sales organization. The release describes Accenture as one of the largest Salesforce users, with 55,000 users, and says it has scaled Copilot to more than 740,000 people. Julie Sweet, Chair and Chief Executive Officer of Accenture, said the company will serve as customer zero for Copilotforce. A firm that already pays for both products at that scale is the natural first test of what a seller needs on each side.

What customer zero tells a buyer. A pilot inside a firm that is the design partner, a large Salesforce user, and a large Copilot user is a strong test of the technology and a limited guide to what a typical buyer will pay. Few buyers will have its terms. The lessons worth asking for are about writeback, permissions, and seat use, more than about price.

In the source’s own words

  • Microsoft’s Book of News, Salesforce in Copilotwithin their existing Salesforce permissionsSource
  • Microsoft’s Book of News, Salesforce in CopilotWork IQ adding relevant context from Teams meetings, Outlook emails and documentsSource
  • Microsoft Source, joint release, November 17require explicit user confirmationSource
  • Microsoft Source, joint release, November 17Regional availability and customer access are governed by applicable customer agreements.Source
  • Microsoft Source, joint release, November 17and as one of the largest Salesforce users globally with 55,000 usersSource
2What does each company say it gets?

In their own words. Judson Althoff, Chief Executive Officer of Microsoft’s commercial business, said AI is only as powerful as the data and context that grounds it. Miguel Milano, President and Chief Operating Officer of Salesforce, said the companies are turning AI from a standalone tool into a driver of productivity. Each statement is its company’s claim.

Salesforce’s pattern. In August 2026 Salesforce and Anthropic announced Claudeforce, with Salesforce in Claude open to select pilot customers and Claude available in Agentforce, Salesforce’s agent platform. Marc Benioff, Salesforce’s Chair and Chief Executive Officer, said: “This is how every business will run.” On September 15, Anthropic released Salesforce in Claude in beta on all paid Claude plans, so the Claude road is a step further along than the Copilot road, which opened in public preview at Ignite.

In the source’s own words

  • Microsoft Source, joint release, Althoff of MicrosoftAI is only as powerful as the data and context that grounds itSource
  • Microsoft Source, joint release, Milano of Salesforcewe're transforming AI from a standalone tool into a powerful driver of productivitySource
  • Salesforce Newsroom, August 26, 2026Claude is available in AgentforceSource
  • Anthropic, September 15, 2026Salesforce in Claude is available in beta on all paid Claude plansSource

↑ Back to the section guide

Part 3The Stay

The Front Door: Both Doors Lead To Copilot

Greyhound SpotlightMicrosoft calls Copilot “the new front door to Dynamics 365.” Copilotforce puts the same door in front of Salesforce.

The front door is the screen where a person starts their work. For years, the CRM was its own front door: sellers logged into Salesforce or Dynamics to see their accounts. Assistants change that. If a seller asks Copilot, Claude, or Agentforce, the assistant becomes the front door and the CRM becomes the record behind it. Ignite shows Microsoft taking that door on both roads.

In practice, the screen staff open first may soon matter as much in a renewal as the system that holds the data. Seat counts, training, and support have tended to follow the application people log into, and an assistant in front of the CRM moves that center of gravity. Greyhound Research would expect vendors to compete harder on the entry point over the next renewal cycles, with bundles that pair the assistant and the record. One knock-on effect is on measurement. When work starts in an assistant, the CRM’s own usage reports may undercount what sellers do, and license reviews built on those reports could cut or keep the wrong seats.

Exhibit 5 sets the two roads side by side, with what stays the same either way. An agent identity is the account an AI agent uses to sign in and act.

Greyhound Research · Exhibit 5 · Two roads to one front door

Leave or stay, Copilot is where work starts

The exit road and the stay road offered at Ignite 2026, set side by side with what stays the same on both, November 19, 2026.

Microsoft takes the door either way. Choose the record on its merits, and license the door once.

If the company leavesActivate: Microsoft holds the record and the doorRecord. Dynamics 365 replaces Salesforce or SAP ECC.Front door. Copilot, through the Dynamics 365 plugins.Price. Not published for Activate.CRM released, ERP in preview
If the company staysCopilotforce: Salesforce keeps the recordRecord. Salesforce, under its own permissions.Front door. Copilot and Teams, with Salesforce inside.Price. Licensing on each side not stated.Preview and pilot
Either wayWhat does not changeFront door. Copilot is where work starts.Agent identity. Entra issues IDs to agents on connected platforms.The rebuild. Rules and processes still need owners.The buyer’s to decide
Against this: Salesforce also sits inside Claude through Claudeforce, so staying with Salesforce does not tie a company to Copilot as its only front door.
Source: Greyhound Research analysis of the Dynamics 365 Blog (Teper, November 17, 2026), Microsoft’s Book of News, the Microsoft and Salesforce joint release, and Microsoft Community Hub (Agent 365). The grouping is Greyhound Research’s.

Exhibit 5 sets the two roads offered at Ignite 2026 side by side in three cards. If the company leaves, through Activate, Dynamics 365 replaces Salesforce or SAP ECC as the record, Copilot is the front door through the Dynamics 365 plugins, and no price is published. If the company stays, through Copilotforce, Salesforce keeps the record under its own permissions, Copilot and Teams become the front door with Salesforce inside, and licensing on each side is not stated. Either way, Copilot is where work starts, Microsoft Entra issues identities to agents on connected platforms, and the rules and processes still need owners. The grouping is Greyhound Research analysis.

Exhibit 5. Leave or stay, Copilot is where work starts. Current through November 19, 2026. © Greyhound Research.

On the exit road, Microsoft holds both the front door and the record. On the stay road, it holds the front door and Salesforce keeps the record. Either way, Microsoft’s directory is starting to issue identities to agents built on other vendors’ platforms, Salesforce’s and SAP’s among them. A companion Greyhound Research note on Azure agent infrastructure holds that what each agent may read, change, and spend is the control, and that identity is where it is enforced. The buyer’s choice is about the record, the price, and the rules. The front door goes to Microsoft either way.

Greyhound Standpoint:

Greyhound Research concludes that the contest in business applications has widened from the record to the front door, and that Microsoft starts ahead on the door because most office staff work in its tools. The shift is familiar. The browser, the portal, and the mobile app each changed where work started, and each time the vendors behind the screen had to decide whether to own the entry point or be reached through someone else’s. Salesforce’s answer serves its customers well: sit inside every assistant, Copilot and Claude alike, and keep the record and the permissions. That keeps a Salesforce customer’s choice of assistant open.

Microsoft’s answer is to make Copilot the entry point on both roads and to issue identities to agents built on other platforms. The consequence for the buyer is that control now sits in two places, the assistant that frames the request and the system of record that enforces the answer, and the companion note on Azure agent infrastructure places that enforcement in identity. The limit is that no company has published usage data for these assistants in sales work, so Microsoft’s lead is a reading of reach, not of results. Evidence that sellers keep starting their day in the CRM would weaken this view.

CIOs should choose the front door on purpose at the next architecture review: decide which assistant staff start from, license it once, and keep each system of record’s permissions behind it.

The Deeper Read · About 2 minutes

Select a question to open the full answer

1How does Microsoft describe Copilot’s role?

The front door. Teper writes that Copilot is the new front door to Dynamics 365. Microsoft’s Sales, Customer Service, and ERP apps plugins for Copilot are generally available, with more than 57 business skills for customer experience and more than 39 for finance and operations, by Microsoft’s count. On the stay road, Salesforce in Copilot starts in preview with more than 38 prebuilt sales skills, so at launch Microsoft’s own door is the more complete of the two.

A customer at the door. Manish Mittal, Senior Vice President and Global Technology Head for Value-Added Services at Visa, is quoted by Microsoft on building on Dynamics 365 in customer service as Visa expands into sales with Copilot. Visa is not described as an Activate customer. Its quote shows the door in use on Microsoft’s own record.

Agents from other vendors. Microsoft’s Agent 365 post says connected agents now automatically receive a Microsoft Entra Agent ID, with support rolling out across eleven platforms, Salesforce Agentforce and SAP among them, to complete in December.

What the skill counts tell a buyer. By Microsoft’s count, its own plugins carry more skills at launch than the Salesforce plugin, which suggests the door is more finished on Microsoft’s own record. Skill counts measure breadth, not depth or use. A pilot that times common seller tasks on each road would tell a buyer more than the counts do.

In the source’s own words

  • Microsoft Community Hub, Agent 365 at Ignite 2026Connected agents now automatically receive a Microsoft Entra Agent IDSource
  • Microsoft Community Hub, Agent 365 at Ignite 2026Support is rolling out across Salesforce Agentforce, Amazon AgentCore, Google Vertex AISource
  • Dynamics 365 Blog, Mittal of Visa, November 17At Visa, we're building on our success with Dynamics 365 in customer service as we expand into sales with Copilot.Source
2Has Greyhound Research seen this pattern before?

Oracle’s version. Greyhound Research’s November 5 note on the front door race read OpenAI’s ChatGPT becoming a front door to Oracle Fusion, and advised buyers to plan on what is live and get the status, price, and region of the rest in writing. The same rule applies to Copilotforce.

The record still matters. In July 2025 Greyhound Research wrote that the rhetoric of AI agents replacing apps is premature, because core systems such as ERP and CRM still perform irreplaceable data integrity and compliance functions. This note keeps that view. The front door moves to the assistant, and the system of record still decides what each user may see and change.

In the source’s own words

  • Greyhound Research, front door notePlan on what is live, and get the status, price and region of the rest in writing.Source
  • Greyhound Research, SaaS silos note, July 26, 2025The future lies in orchestration, not obsolescence.Source

↑ Back to the section guide

Part 4The Money

Renewal Leverage: The Discovery Report Is The Bargaining Chip

Greyhound SpotlightThe discovery report is worth having even if the company does not move.

Renewals are negotiations about the cost of leaving. A vendor that knows a customer cannot leave has little reason to move on price. A customer with a documented, priced plan for leaving has a credible alternative, which is a strong card in any renewal. Until now, building that plan cost months of consulting. Activate lowers that cost for Salesforce customers today, and for SAP ECC customers once its preview opens.

What changes is the cost of credibility. Buyers have long known that a real alternative improves a renewal, but building one cost enough that many companies negotiated on assumption instead. A cheaper discovery lets more companies bring evidence to the table, and Greyhound Research expects incumbents to answer with earlier renewal offers and longer price holds, as they tend to when switching becomes easier to cost. The effect most coverage misses is timing. A report run a few weeks before a renewal deadline arrives too late to change the terms, so the value lies in running it a renewal cycle ahead and refreshing it before each negotiation.

Table 3 sets out each renewal a buyer faces, what Ignite gives the buyer, what the vendor is likely to answer with, and what to get in writing. Each vendor’s position is its own claim.

Greyhound Research · Table 3 · Renewal leverage ledger

One discovery report strengthens four negotiations

The renewals and contracts a buyer faces after Ignite 2026, with what the buyer gains, each vendor’s likely answer, and the terms to secure.

One report, four negotiations. Commission it a renewal cycle ahead, and keep it in the company’s hands.

The incumbent CRMThe incumbent ERPMicrosoft and partners
NegotiationWhat Ignite gives the buyerWhat the vendor will say (its claim)What to get in writing
Salesforce CRM renewalA released, Microsoft-hosted map of the Salesforce estate, and a priced alternativeStaying is easier: Salesforce now sits inside Copilot and ClaudeData export terms, a price hold, exit support, and seat counts matched to use through Copilot
SAP ECC decisionA second destination to price, once the ECC preview opensS/4HANA until 2040, its own agent-led tooling, and the 2033 option for RISE customersEach path’s dates and costs in SAP’s own words
Microsoft renewalTwo roads, both ending at CopilotSpeed claims: five months for 20,000 users, 25% faster finance setupActivate’s price, migration funding, data handling, and Copilotforce licensing
Implementation partner contractA discovery that once took months, produced fasterPartner speed claims, and the partner’s methodWho owns the discovery output, and who keeps the time saved
Against this: A vendor-built assessment favors its maker, so the report should be reviewed by people who do not sell the destination.
Source: Greyhound Research analysis of Microsoft’s Book of News and Dynamics 365 Blog, the Microsoft and Salesforce joint release, Salesforce Newsroom (August 26, 2026), SAP News Center, and statements by SAP’s spokesperson and CEO (January 28, 2025). Vendor positions are each vendor’s claims.

Table 3 lists four negotiations a buyer faces after Ignite 2026 and shows that one discovery report strengthens all four. In the Salesforce renewal, the buyer gains a map of the estate and a priced alternative, Salesforce will say staying is easier now that it sits inside Copilot and Claude, and the buyer should get data export terms, a price hold, exit support, and seat counts matched to use through Copilot in writing. In the SAP ECC decision, the buyer gains a second destination, SAP will point to S/4HANA until 2040, its own tooling, and the 2033 option, and the buyer should get each path’s dates and costs in writing. In the Microsoft renewal, the buyer gains two roads, Microsoft will cite speed claims, and the buyer should get Activate’s price, funding, data handling, and Copilotforce licensing in writing. In the partner contract, the buyer should settle ownership of the discovery output and of the time saved. The reading is Greyhound Research analysis.

Table 3. One discovery report strengthens four negotiations. Current through November 19, 2026. © Greyhound Research.

The same report helps in every row. It gives the Salesforce renewal a priced alternative and the SAP decision a second destination. In the Microsoft renewal, it gives the buyer a basis for asking what Microsoft will fund. Each vendor has an answer. Salesforce now sits inside Copilot, SAP has its own migration tools and dates, and Microsoft has speed claims. The buyer who holds the report can test each answer against its own estate. Copilotforce adds one more item to the Salesforce renewal: where sellers do most of their work through Copilot, the number and tier of Salesforce seats are worth checking against actual use.

Greyhound Standpoint:

Greyhound Research’s position is that when leaving gets cheaper, the exit plan becomes the control. Renewals are priced against the cost of leaving, and for most CRM and ERP customers that cost has been large, unknown, and therefore easy for an incumbent to discount. A plan with a scope, a price, and a tested sample turns an assumed cost into a measured one, and that changes the terms of every renewal, whichever way the decision goes. The outsourcing waves taught the same lesson, when buyers who had written and priced an exit could renegotiate and buyers who held only an exit clause found it much harder. Each incumbent also has a fair answer.

Salesforce can point to Copilotforce and Claudeforce as evidence that staying no longer limits the choice of assistant. SAP can point to its published dates, its 2040 commitment, and its own tooling. Microsoft can point to its speed claims. A buyer holding its own discovery can test each answer against its own estate. The limit is that no vendor publishes how it prices renewals, so the effect of a plan on a given offer cannot be measured in advance. An exit plan held only by a partner or a vendor is weaker leverage, because the other side knows who controls it.

Procurement and CFOs should commission the discovery before the next Salesforce renewal or SAP decision, and write ownership of the output into the partner contract.

The Deeper Read · About 2 minutes

Select a question to open the full answer

1What will each vendor say?

Salesforce. Salesforce’s answer is to make staying easier. It sits inside Copilot through Copilotforce and inside Claude through Claudeforce, so a customer can change its front door without changing its CRM.

SAP. SAP’s answer is time and tools. It has committed to S/4HANA until 2040, offers extended maintenance to 2030 and a transition option to 2033 for RISE customers, and claims its own agent-led tooling cuts migration effort by more than 35 percent. Christian Klein, SAP’s CEO, said in January 2025: “We don’t want to leave the customers behind.”

What the incumbents’ answers tell a buyer. Each answer is a reason to stay, and each has a price. Salesforce’s place inside two assistants may change which seats a seller needs, and SAP’s later dates come with paid maintenance or a move under RISE with SAP. A buyer who maps each answer to a line in the renewal offer can see which reasons cost money and which do not.

In the source’s own words

  • Christian Klein, SAP’s CEO, January 28, 2025We don't want to leave the customers behind.Source
  • SAP News Center, RISE with SAPdesigned to help large customers with complex installations on a RISE with SAP journeySource
2What has Greyhound Research said about leverage before?

Bundles reduce it. In July 2025 Greyhound Research wrote that folding agents into higher-tier Copilot plans makes each feature’s value hard to judge, and that renegotiation leverage is then materially diminished.

Exit ramps restore it. In May 2025, on Salesforce’s Informatica deal, Greyhound Research advised customers to write exit ramps into multi-year deals, with pricing freezes, migration assistance, and clear licensing transition paths. This note takes the same position one step further: a priced exit plan is what gives those clauses weight. The companion note on Azure agent infrastructure held that committing to one platform is defensible when the way out is in the contract.

In the source’s own words

  • Greyhound Research, Copilot agents note, July 14, 2025At that point, renegotiation leverage is materially diminished.Source
  • Greyhound Research, Salesforce and Informatica note, May 28, 2025writing exit ramps into multi-year deals: pricing freezes, migration assistance, and clear licensing transition pathsSource

↑ Back to the section guide

Part 4The Money

The Speed Claims: Five Months Is One Customer’s Forecast

Greyhound SpotlightThe five-month figure is one partner’s forecast for one customer still on track, not a finished project.

Every migration tool launches with speed claims, and Activate follows that pattern. A partner says one large customer is on track to move 20,000 users off Salesforce in about five months. Another says core finance setup was 25 percent faster in a side-by-side test. SAP, for its own tools, claims more than 35 percent less migration effort. These figures will appear in business cases unless someone checks them first.

Launch figures are a fixture of enterprise software, and seasoned buyers discount them by habit. What is different here is where they will land. Activate’s own discovery output can produce a timeline that looks as authoritative as a partner’s forecast, and the two can reinforce each other in a business case without either being tested. Greyhound Research thinks it likely that more customer timelines will be published over the coming year, which would make the claims easier to judge. A quieter effect concerns the partner market. Once a fast figure is public, partners may be asked to match it in fixed-price bids, and the risk then moves into the scope clauses of the contract.

Table 4 lists each claim with who made it, the basis it gives, and what it lacks. A company claim is a figure the company states about its own product.

Greyhound Research · Table 4 · Speed claims ledger

Five claims, and none comes with a method

The speed and scale claims behind Activate and SAP’s rival tooling, with who made each and the basis it gives, November 19, 2026.

Read every figure as a forecast. Budget from the company’s own discovery and a timed pilot, not from a press release.

Partner claim quoted by MicrosoftMicrosoft’s own claimSAP’s claim for its own tools
ClaimKindWho made itBasis givenWhat it lacks
20,000 users off Salesforce in about five months, against a typical 12 to 18Partner claimcongruentX, quoted by MicrosoftOne customer, still on trackA finished result and the scope moved
Core finance setup 25% fasterPartner claimAlithya, quoted by MicrosoftSide-by-side testingProduction results, and the share of a project it covers
Over six billion data records processedCompany claimMicrosoftEarly customer engagementsAn accuracy or reconciliation rate
Strong momentum with Comcast and Fusion5Company claimMicrosoftTwo names. Fusion5 is a Microsoft partnerOutcomes for either
ERP migration effort cut by more than 35 percentRival claimSAP, for its own toolingNone givenA method, and the tool’s name
Against this: The claims are not false. They show what is possible on a prepared estate with a capable partner.
Source: Dynamics 365 Blog (Teper, September 9 and November 17, 2026), SAP News Center (May 12, 2026). The kinds and gaps are Greyhound Research’s reading.

Table 4 lists five speed and scale claims and shows that none comes with a published method. congruentX, quoted by Microsoft, says one customer is on track to move 20,000 users off Salesforce in about five months, against a typical 12 to 18 months, which is a forecast for one project still running. Alithya, quoted by Microsoft, says side-by-side testing showed core finance setup 25 percent faster. Microsoft says Activate processed over six billion records in early engagements, without an accuracy rate, and names Comcast and Fusion5, a Microsoft partner, among its customers, without outcomes. SAP says its own agent-led tooling cuts ERP migration effort by more than 35 percent, with no method given. The claims are each party’s own.

Table 4. Five claims, and none comes with a method. Data as of November 19, 2026. © Greyhound Research.

None of the five comes with a method. The largest is a forecast, not a result. The test figure covers one part of a finance setup. Microsoft’s six billion records describes volume, not accuracy. SAP’s figure is SAP’s, for SAP’s own tools. The claims are not false. They are not yet evidence a CFO should budget on.

Greyhound Standpoint:

In Greyhound Research’s assessment, the speed claims show what is possible on a well-prepared estate with a capable partner, and they do not show what a given company should expect. A launch figure is chosen because it is the best example a vendor or partner can cite, which is normal practice and no fault. The issue is how it travels. A five-month forecast for one customer, a 25 percent gain on one part of a finance setup, six billion records without an accuracy rate, and SAP’s 35 percent for its own tools each measure something different, and none comes with a method.

Once one of them sits in a business case, it becomes the baseline the project is judged against, and the project team inherits a target it did not set. Three decades of implementation timelines suggest that the difference between one estate and another is larger than the difference between one tool and another. Microsoft deserves credit for naming customers and quoting partners on the record, and the figures may prove right. A finished project with a stated scope and method would change this reading.

CFOs should budget from the company’s own discovery report and a timed pilot on its own data, place any press-release timeline in the risk register rather than the business case, and ask at the pilot gate whether the pilot’s pace held.

The Deeper Read · About 2 minutes

Select a question to open the full answer

1What exactly did each party claim?

Microsoft’s partners. Marty Priest, Chief Executive Officer of congruentX, is quoted by Microsoft saying one large enterprise customer is on track to move 20,000 users from Salesforce in about five months, against the 12 to 18 months such projects typically take. John Scandar of Alithya is quoted saying side-by-side testing showed core finance setup could be delivered 25 percent faster.

Microsoft and SAP. Microsoft says Activate processed over six billion data records in early engagements, and names Comcast and Fusion5 among its customers. Fusion5 is a Microsoft business applications partner, and its New Zealand chief executive’s September quote speaks of delivering Activate with Microsoft for “our customers”, so the second name is better read as a partner’s endorsement than as a customer result. SAP claims more than 35 percent lower ERP migration effort for its own agent-led tooling.

What the sources of the claims tell a buyer. Every figure comes from a party with an interest in the result: two partners that sell the work, a vendor that sells the tool, and a rival that sells its own. That is normal at launch and does not make the figures wrong. It does mean a buyer should ask each party for the scope, the starting state of the estate, and what was left out.

In the source’s own words

  • Dynamics 365 Blog, congruentX quoteOne large enterprise customer is on track to move 20,000 users from Salesforce to Microsoft in about five monthsSource
  • Dynamics 365 Blog, congruentX quotemore than twice as fast as the 12 to 18 months these projects typically take.Source
  • Dynamics 365 Blog, Alithya quoteIn side-by-side testing, Dynamics 365 Activate helped us see how we could deliver core finance setup 25% fasterSource
  • Dynamics 365 Blog, Teper on November 17We're seeing strong momentum with customers including Comcast and Fusion5.Source
  • Microsoft partner Fusion5, Dynamics 365 Blog, September 9the true partnership between Microsoft, Fusion5 and our customersSource
2How should a buyer read them?

As drafts. Greyhound Research wrote in July 2025 that every agent output is a draft, not a decision. A migration estimate produced by an agent, or quoted by a vendor, is the same. Buyers already read launch figures this way. Greyhound CIO Pulse 2026, across more than 1,000 enterprise technology leaders, finds 82 percent dismissing mega-announcements as more optics than delivery. A migration business case is where that caution should be applied.

In the source’s own words

  • Greyhound Research, Oracle AI security note, October 29, 2026finds 82 percent dismissing mega-announcements as more optics than deliverySource

↑ Back to the section guide

Part 5The Risks And The Counter-Argument

Risks To Watch: Where A Cheaper Exit Can Still Go Wrong

Greyhound SpotlightNone of the five risks is caused by the tool. Each comes from treating its output as a decision.

Greyhound Research sees five risks in Ignite’s two roads. Two sit on the exit road, one on the SAP clock, one on the stay road, and one on both. Each shows first in a document the buyer already holds, where it can be caught early.

These risks differ from the ones most migration risk logs were built for. Such logs have tended to track technical faults, such as a data load that breaks or an integration that will not connect, each with a fix and a date. The five here are gaps in judgment, where a document is accepted as more final than it is. Greyhound Research expects the first signs to appear in steering committee papers and budget reviews rather than in test results. The second-order effect is on accountability. If a timeline came from a vendor tool and was adopted without review, the company will find it hard to say who owned the decision, and internal audit will ask.

Table 5 sets each risk beside its early warning and its owner. Every early warning can be checked without help from Microsoft, Salesforce, or SAP.

Greyhound Research · Table 5 · Risk register

Every risk comes from treating a vendor’s output as the decision

Five risks on the exit road, the SAP clock, and the stay road, each with its early warning and its owner.

Every risk is cheapest to catch in the buyer’s own documents. Check all five this quarter, without waiting on a vendor.

RiskEarly warning in the buyer’s own documentsOwner
Rules lost in the moveRecords arrive, and the workflows, approvals, or history that gave them meaning do not.A migration plan with no sample reconciliation of records and processes.Head of business applications
A budget set by a press releaseA business case adopts a partner’s five-month forecast as its own timeline.A budget that cites a vendor or partner claim as its basis.Chief financial officer
A deadline that forces the wrong pathAn ECC plan relies on a private preview reaching general availability by a set date.An ECC roadmap with no dated alternative for 2027.Chief information officer
Paying twice to staySellers carry Copilot and Salesforce licenses for the same work, with no test of use.A license plan that adds Salesforce in Copilot without retiring anything.Head of procurement
Data copies with no ownerData sits in a hosted migration copy or a federated query path with no retention rule.A migration or data agreement without retention and deletion terms.Chief data officer
Against this: This is a judgment about order, not a prediction of harm.
Source: Greyhound Research analytical model, not measured data. Greyhound Research analysis of the evidence in this research note.

Table 5 lists five risks, each with an early warning in the buyer’s own documents and an owner. Rules lost in the move, warned by a plan with no sample reconciliation, owned by the head of business applications. A budget set by a press release, warned by a budget that cites a vendor claim, owned by the CFO. A deadline that forces the wrong path, warned by an ECC roadmap with no dated alternative for 2027, owned by the CIO. Paying twice to stay, warned by a license plan that retires nothing, owned by procurement. Data copies with no owner, warned by an agreement without retention and deletion terms, owned by the chief data officer. The risks are Greyhound Research analysis.

Table 5. Every risk comes from treating a vendor’s output as the decision. Current through November 19, 2026. © Greyhound Research.

The five share a cause: a vendor’s output read as the buyer’s decision. A discovery report is a starting point, a speed claim is a forecast, and a preview is a roadmap. Each warning sits in a plan, a budget, or a contract the buyer controls. The table names owners, not likelihoods, and ranks none of the risks above another.

Greyhound Standpoint:

In Greyhound Research’s reading, none of the five risks is new to business application projects, and what has changed is how quickly a tool can produce a plan that looks finished. A discovery report with clean tables and a confident timeline carries an authority that a consultant’s draft spreadsheet did not, and that authority can carry it past the review it needs. The mechanism behind every risk in the table is the same: a vendor’s output read as the buyer’s decision. Rules lost in the move, a budget set by a press release, a deadline that forces the wrong path, paying twice to stay, and data copies with no owner each begin as a reasonable shortcut.

Program leaders will recognize the pattern from earlier waves of automated tooling, when faster drafting moved the risk from the work to the review of the work. The encouraging part is that each risk shows early, in a plan, a budget, a roadmap, a license plan, or a data agreement the buyer already controls. This is a judgment about order, not a prediction of harm, and the table ranks no risk above another because the evidence does not support a ranking.

A published Microsoft reconciliation method would ease the first risk. Each risk has an owner in the Runbook that follows, and each early warning can be checked this quarter, before the first statement of work is signed.

↑ Back to the section guide

Part 5The Risks And The Counter-Argument

The Strongest Objection: Most Companies Stay

Greyhound SpotlightThe strongest objection to this note is that Microsoft’s own Ignite shows coexistence beats migration. Much of that is right.

The objection deserves its full weight. Large companies rarely leave Salesforce or SAP, because the cost and risk are high and the business gains are uncertain. Microsoft itself chose to partner with Salesforce on the same day it launched an exit tool, which suggests it expects most customers to stay. And a migration assessment built by the destination vendor will tend to make the destination look easy. On this view, Activate is mainly a sales tool and Copilotforce is the larger story.

The objection has history on its side. Enterprise application estates have proved durable for decades, and many announced migrations have ended as partial moves or renegotiated renewals. Microsoft’s own choice to partner on the same day suggests it reads the market the same way, and Greyhound Research expects the coexistence road to carry more customers than the exit road over the next few years. What the objection leaves out is the buyer’s position during those years. A company that stays without a priced alternative renews on the incumbent’s assumptions. One that stays with a priced alternative renews on its own, which makes for a different contract even when the vendor is the same.

Exhibit 6 tests each part of the objection against the evidence. Three parts stand. The conclusion that a buyer gains little from an exit plan does not hold.

Greyhound Research · Exhibit 6 · The objection held to the evidence

Three parts of the objection stand, and its conclusion does not

The fair counter-case to this research note, part by part, against the evidence gathered for each.

Greyhound Research’s judgment: most companies will stay, and those holding a priced exit plan are likely to stay on better terms.

StandsFalls
Large CRM and ERP moves are rare and slowStandsMicrosoft’s own partner puts a typical CRM move at 12 to 18 months, and a finance system move is rarely shorter.
Microsoft expects most customers to stayStandsIt launched Copilotforce with Salesforce the same day, and offers SAP operations on Azure.
A vendor-built assessment favors its makerStandsActivate is built by the destination vendor and runs in a Microsoft-hosted experience.
So an exit plan adds littleFallsLeverage needs a credible alternative, not a move. The plan prices it, and the buyer keeps it.
Source: Greyhound Research analytical model, not measured data. Greyhound Research analysis of the Dynamics 365 Blog, Microsoft’s Book of News, and the Microsoft and Salesforce joint release.

Exhibit 6 holds four parts of the strongest objection to this research note against the evidence, as four cards, and shows that three stand and the conclusion does not. Large CRM and ERP moves are rare and slow: stands, since Microsoft’s own partner puts a typical CRM move at 12 to 18 months. Microsoft expects most customers to stay: stands, since it launched Copilotforce with Salesforce the same day. A vendor-built assessment favors its maker: stands. So an exit plan adds little: falls, because leverage needs a credible alternative rather than a move, and the plan prices that alternative. The verdicts are Greyhound Research analysis.

Exhibit 6. Three parts of the objection stand, and its conclusion does not. Current through November 19, 2026. © Greyhound Research.

Greyhound Standpoint:

Greyhound Research accepts the objection’s facts and does not accept its conclusion. Most companies will not move. Large CRM and ERP migrations are slow and costly, Microsoft partnered with Salesforce on the same day it released a tool for leaving Salesforce, and an assessment built by the destination vendor will tend to favor the destination. Each of those points is fair, and the coexistence road may well prove the larger business for all three companies. The objection goes too far in treating a move as the only return on an exit plan. A renewal changes when the incumbent believes the customer could leave, and a documented estate with a priced alternative is the evidence for that belief.

The plan also lists the customizations the buyer is paying to keep, which is useful whether the company moves or not. Long experience of enterprise contracts points the same way: an option to leave is valuable mainly because it is credible, and it is seldom exercised. The fair limit is that leverage is hard to measure, and some incumbents will hold price regardless. Evidence that priced exit plans made no difference to renewal terms would weaken this view.

Buyers who stay should still own an exit plan, reviewed by people who do not sell the destination, and procurement should table it at the next renewal.

The Deeper Read · About 1 minute

Select a question to open the full answer

1Why does the conclusion not hold?

Leverage needs credibility, not a move. A renewal changes when the vendor believes the customer could leave, and a documented estate with a priced alternative is the evidence for that. Activate lowers the cost of producing it. Greyhound Research’s October note on Oracle’s agentic implementation proposed that the drafter never approves its own output, which here means a vendor-built assessment should be reviewed by people who do not sell the destination.

Microsoft hedges too. Microsoft offers agentic operations for SAP on Azure and partners with Salesforce while selling a way off both. The buyer can hedge the same way, by holding an exit plan while renewing.

What Microsoft’s own hedge tells a buyer. If the destination vendor keeps both roads open, the buyer gains little by closing either one early. Holding a priced exit plan while renewing is the buyer’s version of the same position, and it costs far less than a move.

In the source’s own words

  • Greyhound Research, Oracle agentic implementation notethe drafter never approves its own outputSource

↑ Back to the section guide

Part 6What To Do, By Role

The Greyhound CXO Runbook: Ten Moves Before The Next Renewal

Greyhound SpotlightEvery move uses a document the buyer already controls: a renewal calendar, an estate map, a contract, a budget, a data agreement, a license plan, an access review, or a risk register.

Ten moves follow from the evidence, at least one for each leader who owns part of the decision. Each names the assumption it corrects, the evidence behind it, and the executive who decides. None waits for Microsoft, Salesforce, or SAP, because each uses controls the buyer already holds.

Each move is tied to a document for a practical reason. Migration programs have often been governed by steering committees whose decisions were hard to trace later, while a renewal calendar, an estate map, or a license plan can be dated, read, and checked. The first versions will be incomplete and should be revised as the vendors publish terms. In Greyhound Research’s judgment, the estate map is likely to need the most revision, because it changes with every release of the incumbent’s product. What is easy to overlook is that none of these documents favors a destination. An estate map, a customization register, or a data agreement serves a company that stays as well as one that moves.

Table 6 sets the ten moves beside the assumption each corrects, its evidence, and its owner. Two of the ten finish only when Microsoft publishes its terms.

Greyhound Research · Table 6 · The Greyhound CXO Runbook by owner

Ten moves, and none waits on a vendor to start

Ten moves for the leaders who own part of the CRM and ERP decision, with the assumption each corrects, its evidence, and its owner.

Start all ten this quarter. Only the price of the move and coexistence licensing wait on published terms.

Starts and finishes on controls the buyer already holdsCompletes when Microsoft and Salesforce publish terms

Select a move to open its full text in The Deeper Read below

MoveThe assumption it correctsEvidence anchorThe decision sits with
1/Commission the discovery before the next renewalA discovery is only worth doing once a move is decidedExhibit 2CIO, with the head of business applications
2/Put the exit plan on the renewal tableLeverage requires an intent to leaveTable 3Head of procurement, with the CFO
3/Classify every customization and test a sampleA migration tool moves the logicExhibit 4Head of business applications
4/Price three paths for SAP ECC2027 is the only date that mattersExhibit 3, Table 4CFO, with the CIO
5/Write the rules for coexistenceA joint release settles who answers for whatTable 2Chief data officer, with the CISO
6/Choose the front door onceThe CRM decision settles the assistant decisionExhibit 5CIO, with the CFO
7/Write each item’s release status into the contractA Microsoft web page records the status the buyer pays forTable 1Head of procurement, with the head of business applications
8/Bring agents on other platforms into one identity reviewAn agent built on Salesforce or SAP is only that vendor’s to governTable 2, Exhibit 5Enterprise architect, with the CISO
9/Have the discovery reviewed by someone who does not sell the destinationA vendor-built assessment is a neutral oneExhibit 6Head of business applications, with the CIO
10/Ask for the five early warnings at the board risk reviewMigration risk is a technical matter for the project logTable 5Board risk committee, with internal audit
Source: Greyhound Research analysis of the evidence in this research note.

Table 6 sets out the ten moves of the Greyhound CXO Runbook, each with the assumption it corrects, the exhibit or table it rests on, and the executive with whom the decision sits, and shows that none waits on a vendor to start while two complete only when Microsoft and Salesforce publish terms. The moves are: commission the discovery before the next renewal, put the exit plan on the renewal table, classify every customization and test a sample, price three paths for SAP ECC, write the rules for coexistence, choose the front door once, write each item’s release status into the contract, bring agents on other platforms into one identity review, have the discovery reviewed by someone who does not sell the destination, and ask for the five early warnings at the board risk review. The moves are Greyhound Research analysis.

Table 6. Ten moves, and none waits on a vendor to start. Current through November 19, 2026. © Greyhound Research.

The two that finish later, on the price of the move and on coexistence licensing, wait on terms Microsoft and Salesforce have not yet published. Those terms are what the questions that follow ask for, and each question maps to a move a buyer can make meanwhile. Every other move rests on an exhibit or table in this note and names who decides. The remaining eight can be finished with controls the buyer already holds.

The Deeper Read · About 5 minutes

Select a move to open its full text

1CIOs: commission the discovery before the next renewal.

Exhibit 2 shows that Activate’s first steps, reading the estate and recommending what to change, are written and released for Salesforce. This move corrects the belief that a discovery is only worth doing once a move is decided. Its action is to run a discovery on the Salesforce estate, with Activate or an independent partner, before the next renewal date, and to keep the output in the company’s hands. For SAP ECC, the action is to request access to the private preview or run an equivalent review. The decision sits with the CIO, together with the head of business applications.

Why this move comes first. Every other move draws on its output. Without a discovery, the exit plan has no price, the customization register has no list, and the SAP comparison has no baseline. Buyers who start from the renewal letter rather than the estate map tend to negotiate on the vendor’s numbers.

2Procurement: put the exit plan on the renewal table.

Table 3 shows that a priced exit plan changes the Salesforce, SAP, and Microsoft renewals alike. This move corrects the assumption that leverage requires an intent to leave. Its action is to price the alternative, set it beside the renewal offer, and ask each incumbent for data export terms, price holds, and exit support in writing. From Microsoft, ask for Activate’s price and any migration funding. The decision sits with the head of procurement, together with the CFO.

3Business applications leads: classify every customization and test a sample.

Exhibit 4 shows that records move while customizations, integrations, and processes are moved, simplified, or redesigned case by case. This move corrects the belief that a migration tool moves the logic. Its action is to classify every customization as move, simplify, redesign, or retire, and to reconcile a sample of records, workflows, and history on real data before any timeline is committed. The decision sits with the head of business applications.

4CFOs: price three paths for SAP ECC.

Exhibit 3 shows mainstream maintenance ending at the end of 2027, paid extended maintenance to 2030, and a narrow option to 2033, with Microsoft’s tool in private preview. This move corrects the habit of treating 2027 as the only date. Its action is to price staying under extended maintenance, moving to S/4HANA with SAP, and moving to Dynamics 365, using each vendor’s dates in its own words and a budget built from the company’s discovery, not from a speed claim. The decision sits with the CFO, together with the CIO.

5Chief data officers: write the rules for coexistence.

Table 2 shows that Salesforce governs access and every update needs a user’s confirmation, while licensing and accountability for a wrong update are not written. This move corrects the assumption that a joint release settles who answers for what. Its action is to agree which Salesforce actions Copilot may take, how federated data is kept and deleted, and who answers when an update goes wrong, and to write those into the data and service agreements. The decision sits with the chief data officer, together with the CISO.

6CIOs: choose the front door once.

Exhibit 5 shows that both roads put Copilot where work starts. This move corrects the belief that the CRM decision settles the assistant decision. Its action is to decide which assistant staff start from, license it once, and keep each system of record’s permissions behind it, so that sellers are not paid for twice. The decision sits with the CIO, together with the CFO.

7Procurement: write each item’s release status into the contract.

Table 1 shows two rows that can be signed with full terms today, beside four previews or pilots and no published price. It also shows that Microsoft’s pages disagree. The partner page still described a limited public preview of the Salesforce tool after the Book of News called it generally available, and one page calls the SAP ECC steps private preview while another says they are rolling out. This move corrects the assumption that a Microsoft web page records the status the buyer pays for. Its action is to list every Ignite item an order form or statement of work relies on, write each item’s release status into the contract, and commit no spend to a preview. Partners scope and price work from their own pages, so the partner’s statement of work should carry the same list. The decision sits with the head of procurement, together with the head of business applications, before the first statement of work is signed.

8Enterprise architects: bring agents on other platforms into one identity review.

Table 2 and Exhibit 5 show Microsoft Entra issuing an Entra Agent ID to agents on eleven connected platforms, Salesforce Agentforce and SAP among them, with the rollout due to complete in December, while Salesforce continues to govern what each user may see and change. This move corrects the assumption that an agent built on Salesforce or SAP is only that vendor’s to govern. Such an agent then sits with two vendors. Its action is to use the access review the company already runs to list every agent on a connected platform, name an owner for each, and record which system grants its rights and which can withdraw them. The companion Greyhound Research note on Azure agent infrastructure holds that identity is where control is enforced, so this list is where the work starts. The decision sits with the enterprise architect, together with the CISO, at the architecture review that falls before the December rollout completes.

9Business applications leads: have the discovery reviewed by someone who does not sell the destination.

Exhibit 6 finds that one part of the strongest objection stands: Activate is built by the destination vendor and runs in a Microsoft-hosted experience, so its assessment will tend to favor its maker. This move corrects the assumption that a vendor-built assessment is a neutral one. Its action is to have the discovery report reviewed, before it reaches a renewal or a budget, by people who do not sell Dynamics 365, an internal team or an independent partner. The reviewers should check the recommendations on what to keep, simplify, or redesign, and how those recommendations weigh staying on Salesforce, which Exhibit 2 marks as open. Greyhound Research’s October note on Oracle’s agentic implementation proposed that the drafter never approves its own output, and the same rule applies to a migration assessment. The decision sits with the head of business applications, together with the CIO, at the pilot gate where the report is first used.

10Board risk committees: ask for the five early warnings at the board risk review.

Table 5 sets out five risks, from rules lost in the move to data copies with no owner, each with an early warning in a plan, a budget, a roadmap, a license plan, or a data agreement the buyer already holds. This move corrects the assumption that migration risk is a technical matter for the project log. Such logs track faults with a fix and a date, while these five are gaps in judgment. Its action is to put the five early warnings on the agenda of the next board risk review, ask each named owner whether the warning is present, and record who approved any timeline or budget that came from a vendor tool. If a timeline was adopted without review, internal audit will ask who owned the decision, and the board is better placed to ask first. The decision sits with the board risk committee, together with internal audit.

↑ Back to the section guide

Part 6What To Do, By Role

Questions For Microsoft: What Buyers Will Ask Next

Greyhound SpotlightNot one of the six questions has a full answer in what Microsoft has published, including what Activate costs.

Every finding in this note rests on what Microsoft has published, and Microsoft alone can close the gaps it names. Six questions follow, in the order the evidence raises them. Each gives what Microsoft has said so far, what the answer would settle, and the Runbook move it maps to. No move waits on them, and an account team can answer each from documents Microsoft already holds.

Questions of this kind tend to be answered in the order that suits the seller. Price and release dates usually arrive first, because a vendor needs them to close business, while terms on data handling and accountability arrive later, often only when customers ask in writing. Greyhound Research expects Activate’s price and the SAP timetable to be published before the questions on retention and writeback errors are answered. Buyers who ask together, through user groups or in the same renewal season, have tended to get earlier answers. A written reply can also be appended to the statement of work for a migration, so the answer travels with the contract rather than staying in a slide.

Table 7 tracks the six questions against what Microsoft has said so far. Three are answered in part, and three not at all.

Greyhound Research · Table 7 · Questions for Microsoft, tracked

Three questions answered in part, three not at all

The six questions only Microsoft can answer, against what it had stated by 00:50 UTC on November 19, 2026.

Ask in writing now. A price and a conversion scope would change this reading most, and no move waits on either.

Stated in partNot stated

Select a question to open its full text in The Deeper Read below

QuestionWhat Microsoft has said so farThe Runbook move it settles
Q1What does Activate cost, and does migration funding or credit come with it?Not stated No price in Microsoft’s announcements or its partner page.Runbook move 2
Q2When will Activate for ERP be generally available, and for which ECC releases and modules?Not stated One page says private preview, another says rolling out.Runbook move 4
Q3What does Activate move unchanged, convert, or leave for redesign?Stated in part Items assessed are named. Customizations are moved, simplified, or redesigned.Runbook move 3
Q4Where does customer data sit during a move, and for how long?Stated in part A Microsoft-hosted experience, with no retention terms.Runbook moves 2 and 5
Q5Which licenses does Salesforce in Copilot need on each side, and when does it leave preview?Not stated Access is left to customer agreements.Runbook move 6
Q6Who answers when an update made through Copilot goes wrong in Salesforce?Stated in part Salesforce governs actions, and each update needs user confirmation.Runbook move 5
Against this: None of the six is a trick question. Each asks Microsoft to write down what its product does, costs, or will do at release.
Source: Greyhound Research analysis of Microsoft’s Book of News, Dynamics 365 Blog, partner tools page, and the Microsoft and Salesforce joint release.

Table 7 tracks six questions only Microsoft can answer against what it had stated by 00:50 UTC on November 19, 2026, and shows three answered in part and three not stated at all. Not stated: what Activate costs and whether funding comes with it, when Activate for ERP will be generally available and for which ECC releases, and which licenses Salesforce in Copilot needs. Answered in part: what Activate moves, converts, or leaves for redesign, where customer data sits during a move, and who answers for a wrong update made through Copilot. Each question names the Runbook move it settles. The grading is Greyhound Research analysis.

Table 7. Three questions answered in part, three not at all. Current through November 19, 2026. © Greyhound Research.

Two answers would change this note’s reading most. One is a published price for Activate, with any migration funding attached. The other is a documented list of what Activate moves unchanged, what it converts, and what it leaves for redesign. Either would move Activate from a promising tool to one a CFO could budget on. None of the six is a trick question. Each asks Microsoft to write down what its product does, costs, or will do at release.

The Deeper Read · About 2 minutes

Select a question to open its full text

Q1What does Activate cost, and does migration funding or credit come with it?

Said so far. Not stated. Microsoft’s announcements and its partner page give no price for Activate. The answer settles. Whether the exit plan of the second Runbook move can carry a full price. Evidence that would settle it. A published price or licensing note. Greyhound Research would update. Table 1.

Q2When will Activate for ERP be generally available, and for which SAP ECC releases and modules?

Said so far. Not stated. One Microsoft page says private preview, and the Book of News says rolling out over the coming weeks. The answer settles. Whether Microsoft is a real third path in the fourth Runbook move before SAP’s dates. Evidence that would settle it. A release date and a scope list. Greyhound Research would update. Exhibit 3.

Q3What does Activate move unchanged, what does it convert, and what does it leave for redesign?

Said so far. In part. Microsoft names objects, workflows, code, and integrations among the things assessed, and leaves customizations to be moved, simplified, or redesigned. The answer settles. How much of the third Runbook move’s classification the tool can do. Evidence that would settle it. Documentation of conversion scope, including history and audit trails. Greyhound Research would update. Exhibit 4.

Q4Where does customer data sit during a move, and for how long?

Said so far. In part. Microsoft describes a Microsoft-hosted experience. The answer settles. What the data terms of the second and fifth Runbook moves must cover. Evidence that would settle it. A data handling and retention statement for Activate. Greyhound Research would update. Exhibit 2.

Q5Which licenses does Salesforce in Copilot need on each side, and when does it leave preview?

Said so far. Not stated. The joint release leaves access to customer agreements. The answer settles. The license plan of the sixth Runbook move. Evidence that would settle it. Published licensing for Salesforce in Copilot and Sales Cloud in Teams. Greyhound Research would update. Table 2.

Q6Who answers when an update made through Copilot goes wrong in Salesforce?

Said so far. In part. Salesforce governs access and actions, and each update needs the user’s confirmation. The answer settles. The accountability terms of the fifth Runbook move. Evidence that would settle it. Joint terms naming who is responsible for writeback errors. Greyhound Research would update. Table 2.

Why user confirmation matters. A confirmation step answers part of the question, because a person approved each update. It leaves open what happens when the person approves an update built on wrong context from the assistant. That gap sits between two vendors’ terms, which is why it needs a joint answer in writing.

↑ Back to the section guide

Part 7The Final Greyhound Standpoint

Dynamics 365 Activate: The Final Greyhound Standpoint

Greyhound SpotlightFour signals within twelve months would move this position, and Microsoft controls all four.

Greyhound Research’s final judgment is that Ignite 2026 put a released tool behind Microsoft’s long-standing bid for Salesforce and SAP customers, and on the same day offered Salesforce customers a way to stay. Both roads end at Copilot. When leaving gets cheaper, the exit plan becomes the control: a scoped, priced, tested plan the buyer owns, used at every renewal whether or not the company moves. The judgment is not that companies should leave. For most, staying with Salesforce or SAP will remain the sound choice, and both vendors have given them reasons to stay. Salesforce keeps its record and its permissions behind each assistant it joins, and SAP has committed to S/4HANA until 2040, offers paid maintenance beyond 2027, and has built its own migration tooling.

On the exit road, the Salesforce tool is generally available and its discovery is the part to use now. The SAP tool is a private preview against SAP’s end-2027 date, useful for deciding and too new to carry a full move. On the stay road, Copilotforce keeps Salesforce’s own permissions, and its licensing is not written. On both roads, the hardest work is still rebuilding the rules that made the old system fit the business.

The mechanism is the price of information. For decades the cost of finding out what leaving would involve has protected incumbents more than most contract terms, because a buyer that cannot price the alternative cannot use it. Earlier platform shifts, from client-server software to the cloud, often brought destination vendors willing to fund that discovery to win share, and the buyers who gained most kept the findings and used them at the table, whatever they decided. Activate lowers that cost for Salesforce customers today, and may do the same for SAP ECC customers once its preview opens. Microsoft deserves credit for that, and buyers should remember that the tool comes from the vendor that gains if they move.

The evidence has limits. Activate has no public documentation beyond Microsoft’s announcements and a partner page. Microsoft’s pages disagree on the SAP tool’s status. The speed claims come from partners and vendors without a method. Salesforce’s and SAP’s positions are read only through their own announcements and statements. Statuses and claims are as each company published them through November 19, 2026.

Four signals would move this position within twelve months. Each would make Activate easier to budget on. They are a published price for Activate with any migration funding, general availability of Activate for ERP with a scope list, documentation of what Activate converts and what it leaves for redesign, and published licensing for Salesforce in Copilot at general availability.

Exhibit 7 sets those signals side by side with what each would change. All four sit with Microsoft, and one of them also with Salesforce.

Greyhound Research · Exhibit 7 · Signals that would move the position

Four signals in twelve months would move this position

What would move Greyhound Research’s judgment within twelve months, and what each would change.

A documented conversion scope would move this view furthest. Watch for it first.

Signal Microsoft controlsEvent outside its control
A documented conversion scopeWhat Activate moves unchanged, converts, and leaves for redesign, including history and audit trails.Would show how much of a move is migration and how much is rebuilding. Controlled by: Microsoft.A published priceA price for Activate, with any migration funding or credit attached.Would let CFOs put the exit plan on the renewal table at full cost. Controlled by: Microsoft.Activate for ERP generally availableA release date and a list of the ECC releases and modules in scope.Would make Microsoft a dated third path before SAP’s deadlines. Controlled by: Microsoft.Copilotforce licensingPublished licensing for Salesforce in Copilot and Sales Cloud in Teams at general availability.Would show the cost of staying, set jointly with Salesforce. Controlled by: Microsoft.Outside Microsoft’s controlA change by Salesforce or SAP to data export or access terms, or a new migration offer from either, could reset the comparison.
Source: Greyhound Research analytical model, not measured data. Greyhound Research analysis.

Exhibit 7 lists the four signals that would move Greyhound Research’s position within twelve months, each controlled by Microsoft, and one event outside its control. A documented conversion scope would show how much of a move is migration and how much is rebuilding. A published price for Activate would let CFOs cost the exit plan in full. General availability of Activate for ERP, with a scope list, would make Microsoft a dated third path before SAP’s deadlines. Published Copilotforce licensing would show the cost of staying. A change by Salesforce or SAP to data export or access terms, or a new migration offer, could reset the comparison. The signals are Greyhound Research analysis.

Exhibit 7. Four signals in twelve months would move this position. Current through November 19, 2026. © Greyhound Research.

One event outside Microsoft’s control could reset the comparison: a change by Salesforce or SAP to data export or access terms, or a new migration offer from either. Of the four signals, a documented conversion scope would matter most, because it decides how much of a move is migration and how much is rebuilding. Until the signals arrive, CIOs, CFOs, and procurement leaders have a clear order of work for the next renewal or SAP decision. Run the discovery, keep it in the company’s hands, price the exit beside the renewal offer, and treat any press-release timeline as a forecast to test in a pilot rather than a basis for a contract.

↑ Back to the section guide

Part 8Appendix, Sources, And Disclosures

Appendix: The Evidence Register, Source By Source

Greyhound Research sets out here the evidence behind every fact, figure, and quotation in this research note, one drop-down for each class of source, so that any sentence can be checked against the words it rests on without leaving the page. Each row gives the source, when it was read, the part of the source the words sit in, what it says, and where in this research note that material is used. Times of reading are in UTC. Every source was first read on November 18, 2026, between 11:55 and 12:05 UTC, and read again on November 19, 2026, between 00:28 and 00:50 UTC, when every quotation was checked against the live page. Four sources were added on November 19. Where a passage was summarized and not quoted, the row says so. A passage quoted in The Deeper Read of a section is not repeated here, and the source’s entry names the section that quotes it.

Microsoft announcements, blogs, and partner pages6 sources, 60 extracts
Source, read, and usedWhere in the sourceWhat it says
Microsoft (2026a)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in What Microsoft Announced, Two Signals At Once, Activate For CRM, The SAP ECC Clock, Data And Process Fidelity, Copilotforce, The Strongest Objection, Dynamics 365 Activate. Tables 1 and 2. Exhibits 1, 2, 3, and 4Quoted in The Deeper Read of What Microsoft Announced, Activate For CRM, The SAP ECC Clock, Data And Process Fidelity, Copilotforce, Two Signals At OnceDynamics 365 Activate[quoted in The Deeper Read]
Same section[quoted in The Deeper Read]
Same section"Dynamics 365 Activate is an implementation and migration platform"
Same section[quoted in The Deeper Read]
Same section[quoted in The Deeper Read]
Same section"Project context will carry forward from assessment through implementation"
Same section[quoted in The Deeper Read]
Salesforce in Copilot, Teams and Fabric[quoted in The Deeper Read]
Same section[quoted in The Deeper Read]
Same section"allowing sellers to get a real-time view of pipeline and quota progress"
Same section"while leaving the source data in Fabric."
Azure agentic operations[quoted in The Deeper Read]
Same section"now available in preview with more than 38+ prebuilt sales skills"
Reading noteAzure Workload Center is listed as "in preview", without a private or public qualifier (corrected on November 19 from [quoted in The Deeper Read]). The Book of News does not use the name Copilotforce. The page was read in two passes, from the start and from character 100,000. No passage mentions Agentforce.
Microsoft (2026b)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in What Microsoft Announced, Two Signals At Once, Copilotforce, Renewal Leverage, The Strongest Objection, Dynamics 365 Activate. Tables 1 and 2. Exhibits 1 and 5Quoted in The Deeper Read of What Microsoft Announced, Two Signals At Once, CopilotforceRelease"a plugin available in public preview with 38+ prebuilt sales skills"
Availability[quoted in The Deeper Read]
Availability[quoted in The Deeper Read]
Availability[quoted in The Deeper Read]
AvailabilityData sharing from Salesforce Data 360 into OneLake is in public preview (summarized, not quoted).
Trust[quoted in The Deeper Read]
Trust[quoted in The Deeper Read]
Trust"Microsoft applies its existing enterprise compliance controls to communications and documents."
Accenture"Accenture is serving as design and implementation partner and pilot customer,"
Accenture"having scaled Copilot to more than 740,000 people"
Sweet of Accenture"We are also excited to serve as customer zero for Copilotforce" (Julie Sweet, Chair and CEO, Accenture).
Terms[quoted in The Deeper Read]
Althoff of Microsoft[quoted in The Deeper Read]
Milano of Salesforce[quoted in The Deeper Read]
Reading noteThe release does not address licensing, pricing, or who pays, and does not mention Slack. Several sentences quoted in The Deeper Read end with a comma in the release and are quoted without closing punctuation. Dateline: Redmond and San Francisco, November 17, 2026.
Teper, J. (2026a)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in What Microsoft Announced, Activate For CRM, Data And Process Fidelity, The Speed Claims. Exhibits 2 and 4. Table 4Quoted in The Deeper Read of Activate For CRM, Data And Process Fidelity, What Microsoft AnnouncedStatus"We are starting with a public preview for organizations moving from Salesforce to Dynamics 365"
Discovery[quoted in The Deeper Read]
Execution[quoted in The Deeper Read]
ExecutionThe migration runs in a "Microsoft-hosted experience" (phrase quoted, sentence summarized).
Scale[quoted in The Deeper Read]
Scope[quoted in The Deeper Read]
Partner quote[quoted in The Deeper Read]
Image description"analysis results for Salesforce objects, workflows, code, integrations, and related components"
Comcast"For example, Comcast was looking for ways to accelerate its migration assessment"
Comcast quote"greater visibility into our Salesforce landscape and key migration considerations" (Sathish Arumugam, Manager, Software Dev and Engineering, Comcast).
Fusion5 quote"Dynamics 365 Activate represents a significant step forward in how Dynamics 365 solutions can be delivered." (Kristy Brown, Chief Executive, New Zealand, Fusion5).
Reading noteNo price, licensing, or data retention terms are given. No formal human-review step is described beyond the partner quote.
Teper, J. (2026b)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in What Microsoft Announced, Two Signals At Once, Activate For CRM, The SAP ECC Clock, Data And Process Fidelity, The Front Door, The Speed Claims. Tables 1 and 4. Exhibits 3 and 5Quoted in The Deeper Read of Two Signals At Once, What Microsoft Announced, Data And Process Fidelity, Activate For CRM, The Speed ClaimsModernize with Dynamics 365 Activate[quoted in The Deeper Read]
Same section"extending Dynamics 365 Activate for ERP, starting with SAP ECC (private preview)"
Same section[quoted in The Deeper Read]
Same section[quoted in The Deeper Read]
Same section[quoted in The Deeper Read]
Same section[quoted in The Deeper Read]
congruentX quote[quoted in The Deeper Read]
congruentX quote[quoted in The Deeper Read]
Alithya quote[quoted in The Deeper Read]
Copilot[quoted in The Deeper Read]
PluginsThe Sales, Customer Service, and ERP apps plugins are each marked [quoted in The Deeper Read], with "more than 57 business skills" across the customer experience plugins and more than 39 finance and operations skills.
Visa quoteManish Mittal, Senior Vice President and Global Technology Head for Value-Added Services, Visa (title as printed).
Reading noteThe post does not mention Salesforce in Copilot, Copilotforce, pricing, or credits for Activate. Fusion5 and Comcast appear only in the momentum sentence.
Stanford, C. (2026)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in The Front Door. Exhibit 5Quoted in The Deeper Read of The Front DoorConnected platforms[quoted in The Deeper Read]
Connected platforms"A sales team might build in Salesforce Agentforce, a data team in Databricks Genie, and developers in Amazon Bedrock."
Rollout"Anthropic Claude Managed Agents, OpenAI, Oracle, SAP, ServiceNow, and UiPath, and will complete in December."
Reading noteRe-read November 19: the rollout sentence lists eleven platforms, Salesforce Agentforce first. The earlier reading that the post named Agentforce only as an example is corrected. The post is signed carolinestanford, with no job title.
Microsoft (n.d.)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in What Microsoft Announced. Table 1Quoted in The Deeper Read of What Microsoft AnnouncedActivate[quoted in The Deeper Read]
Reading noteThe page describes Activate for project discovery and Activate for migration for Salesforce only, states no cost to partners or customers, and has no SAP content. It still said limited public preview when read again on November 19.
Salesforce, SAP, and other companies6 sources, 22 extracts
Source, read, and usedWhere in the sourceWhat it says
Anthropic (2026)Read November 19, 2026, between 00:28 and 00:50 UTCUsed in CopilotforceArticle"Today we are releasing Salesforce in Claude in beta."
Reading noteDated September 15, 2026. Admins request access through AgentExchange.
Fusion5 (n.d.)Read November 19, 2026, between 00:28 and 00:50 UTCUsed in The Speed ClaimsNews"won the prestigious Microsoft ANZ Business Applications Partner of the Year Award for 2024"
Reading noteThe page carries no publication date. It is cited only for Fusion5's status as a Microsoft partner.
Salesforce (2026)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in What Microsoft Announced, Copilotforce, Renewal Leverage. Table 3Quoted in The Deeper Read of CopilotforceRelease[quoted in The Deeper Read]
Benioff of Salesforce"This is how every business will run."
Availability"Salesforce in Claude is available to select pilot customers now and expects to launch in open beta in September 2026."
Reading noteThe release does not mention Microsoft or Copilot in its body. [quoted in The Deeper Read] is followed by more text and is quoted without closing punctuation.
Gilg, J. (2024)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in The SAP ECC Clock, Renewal Leverage. Exhibit 3. Table 3Quoted in The Deeper Read of The SAP ECC ClockPost[quoted in The Deeper Read]
Post"end maintenance for the latest three enhancement packages of core applications"
Post[quoted in The Deeper Read]
Reading noteThe post, by Jan Gilg, gives the end of 2027 for mainstream maintenance of the latest three enhancement packages of SAP Business Suite 7, and states no fee.
SAP (2025)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in The SAP ECC Clock, Renewal Leverage. Exhibit 3. Table 3Quoted in The Deeper Read of Renewal Leverage, The SAP ECC ClockTransition option[quoted in The Deeper Read]
Transition option"available for active usage from 2031 to 2033"
Conditions[quoted in The Deeper Read]
Conditions"SAP HANA is the only supported database for the new subscription offering."
Reading noteThe page was published on February 4, 2025, and updated on March 7, 2025, under the headline New Offering to Help Navigate Complex RISE with SAP Transformations. The note earlier gave its title as the RISE with SAP landing title and no publication date, corrected on November 19.
SAP (2026)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in Two Signals At Once, The SAP ECC Clock, Renewal Leverage, The Speed Claims. Tables 3 and 4Quoted in The Deeper Read of The SAP ECC Clock, Two Signals At OnceRelease[quoted in The Deeper Read]
Release"SAP S/4HANA on-premises and SAP ERP Central Component (SAP ECC) customers are not excluded"
Release[quoted in The Deeper Read]
Partnerships[quoted in The Deeper Read]
Reading noteThe tooling is not named. Google Cloud and Microsoft are named as partners for agent interoperability.
Media3 sources, 11 extracts
Source, read, and usedWhere in the sourceWhat it says
Clark, L. (2025)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in The SAP ECC Clock, Renewal Leverage. Exhibit 3. Table 3Quoted in The Deeper Read of The SAP ECC Clock, Renewal LeverageSAP spokesperson[quoted in The Deeper Read]
SAP spokesperson[quoted in The Deeper Read]
Transition option"The option will be offered for the period from 2031 until the end of 2033,"
ConditionsCustomers must "sign up for a cloud migration deal" (phrase quoted, sentence summarized).
Klein of SAP[quoted in The Deeper Read]
Reading noteThe article attributes the Klein line to a recent call, linked to SAP's fourth-quarter 2024 earnings call transcript.
Ghoshal, A. (2026)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in What Microsoft Announced, as corroboration onlyReportActivate was "currently in public preview" on September 10, 2026 (phrase quoted, sentence summarized).
ReportMicrosoft planned "ERP capabilities expected later this year" (phrase quoted, sentence summarized).
Reading noteCommentary from third-party analysts in the article is not used. The article carries no Salesforce comment.
Zwets, B. (2026)Read November 18, 2026, between 11:55 and 12:05 UTC, and again November 19, 2026, between 00:28 and 00:50 UTCUsed in What Microsoft Announced, as corroboration onlyReport"Organizations can now sign up for the public preview of the Salesforce migration."
Report"The ERP capabilities will be released later this year."
Research this note builds on7 sources, 13 extracts
Source, read, and usedWhere in the sourceWhat it says
Greyhound Research (2025a)Read November 18, 2026, before 12:05 UTC, and again November 19, 2026, before 00:50 UTC, on greyhoundresearch.comUsed in Data And Process Fidelity, Renewal LeverageQuoted in The Deeper Read of Data And Process FidelityWhat This Deal Signals"According to Greyhound CIO Pulse 2025, 58% of enterprise technology leaders globally now classify"
Reading noteThe figure is in the main body under What This Deal Signals for the Broader Enterprise Technology Ecosystem, not in the page's separate AI-generated summary notice. The sentence ends [quoted in The Deeper Read], which the note now includes. The exit-ramps advice is point 5 of the Post-Acquisition Toolkit.
Greyhound Research (2025b)Read November 18, 2026, before 12:05 UTC, and again November 19, 2026, before 00:50 UTC, on greyhoundresearch.comUsed in Renewal Leverage, The Speed ClaimsQuoted in The Deeper Read of Renewal LeverageNote[quoted in The Deeper Read]
Note"every agent output is a draft, not a decision"
Greyhound Research (2025c)Read November 19, 2026, between 00:28 and 00:50 UTC, on greyhoundresearch.comUsed in The Front DoorStandpoint"According to Greyhound Research, the rhetoric of AI agents replacing apps is premature."
Standpoint"still perform irreplaceable data integrity and compliance functions"
Greyhound Research (2026a)Read November 18, 2026, before 12:05 UTC, and again November 19, 2026, before 00:50 UTC, on greyhoundresearch.comUsed in Activate For CRM, The Speed Claims, The Strongest ObjectionQuoted in The Deeper Read of Activate For CRM, The Strongest ObjectionStandpoint[quoted in The Deeper Read]
Note[quoted in The Deeper Read]
Reading noteThe shorter wording used before November 19, whoever signs off agent-drafted configuration is signing off authority, sits in that note's AI-drafted synopsis, so the Standpoint wording is now quoted. The note's disclosures state that Oracle is a client of Greyhound Research.
Greyhound Research (2026b)Read November 19, 2026, between 00:28 and 00:50 UTC, on greyhoundresearch.comUsed in The Speed ClaimsReading noteThe figure sits in Questions For Oracle, Q1, and is given as Greyhound CIO Pulse 2026, across more than 1,000 enterprise technology leaders. The note's disclosures state that Oracle is a client of Greyhound Research.
Greyhound Research (2026c)Read November 18, 2026, before 12:05 UTC, and again November 19, 2026, before 00:50 UTC, on greyhoundresearch.comUsed in The Front DoorQuoted in The Deeper Read of The Front DoorNote[quoted in The Deeper Read]
Greyhound Research (2026d)Read November 18, 2026, from the draft of the same date, and checked again November 19, 2026Used in The Front Door, Renewal LeverageLock-In And ExitCommitting to one agent platform is defensible when the way out is in the contract (summarized, not quoted).
Agent Grid And IdentityWhat each agent may read, change, and spend becomes the control (summarized, not quoted).

↑ Back to the section guide

Part 8Appendix, Sources, And Disclosures

Sources And References: Every Document Behind Every Claim

Every fact, figure, and quotation in this research note traces to one of the sources below, presented in Harvard reference format and grouped by class. Each source is also linked in the sentence that carries it. Microsoft’s, Salesforce’s, SAP’s, and the other companies’ documents are each company’s account of its own products, dates, and terms, and prove what the company said rather than that the thing is true. Partner figures quoted by Microsoft are the partners’ claims. The news reports what its authors were told. Standing pages that carry no publication date are marked n.d. All sources were first read on November 18, 2026, and every source was read again on November 19, 2026.

Microsoft announcements and blogs

Microsoft (2026a) Microsoft Ignite 2026 | Book of News. Microsoft News, November 17. Available at: https://news.microsoft.com/events/ignite/2026/book-of-news/

Microsoft (2026b) Microsoft and Salesforce Announce Copilotforce, Bringing Trusted Customer Context and Action into Microsoft AI Experiences. Microsoft Source, November 17. Available at: https://news.microsoft.com/source/2026/11/17/microsoft-and-salesforce-announce-copilotforce-bringing-trusted-customer-context-and-action-into-microsoft-ai-experiences/

Teper, J. (2026a) Accelerate your move to agentic business applications with Dynamics 365 Activate. Microsoft Dynamics 365 Blog, September 9. Available at: https://www.microsoft.com/en-us/dynamics-365/blog/business-leader/2026/09/09/accelerate-your-move-to-agentic-business-applications-with-dynamics-365-activate/

Teper, J. (2026b) Microsoft Ignite 2026: Introducing Dynamics 365 in Copilot. Microsoft Dynamics 365 Blog, November 17. Available at: https://www.microsoft.com/en-us/dynamics-365/blog/business-leader/2026/11/17/microsoft-ignite-2026-introducing-dynamics-365-in-copilot/

Stanford, C. (2026) What’s new in Microsoft Agent 365: Ignite 2026. Microsoft Community Hub, November 17. Available at: https://techcommunity.microsoft.com/blog/agent-365-blog/whats-new-in-microsoft-agent-365-ignite-2026/4571753

Microsoft (n.d.) Dynamics 365 Partner Tools. Microsoft Partner. Available at: https://microsoftpartners.microsoft.com/abs/d365-partner-tools/

Salesforce, SAP, and other companies

Anthropic (2026) Bringing Salesforce into Claude. Claude, September 15. Available at: https://claude.com/resources/articles/salesforce-in-claude

Fusion5 (n.d.) Fusion5 Secures 2024 Microsoft ANZ Business Applications Partner of the Year Award. Fusion5 News. Available at: https://www.fusion5.com/nz/news/fusion5-secures-2024-microsoft-anz-business-applications-partner-of-the-year-award

Gilg, J. (2024) Embracing the Future: A Strategic Shift to Cloud ERP Solutions. SAP News Center, October 30. Available at: https://news.sap.com/2024/10/embracing-strategic-shift-cloud-erp/

Salesforce (2026) Salesforce and Anthropic Announce Claudeforce. Salesforce Newsroom, August 26. Available at: https://www.salesforce.com/news/?p=94766

SAP (2025) New Offering to Help Navigate Complex RISE with SAP Transformations. SAP News Center, February 4, updated March 7. Available at: https://news.sap.com/2025/02/sap-erp-private-edition-transition-option-navigate-complex-rise-with-sap-transformations/

SAP (2026) SAP Unveils the Autonomous Enterprise. SAP News Center, May 12. Available at: https://news.sap.com/?p=242256

Media

Clark, L. (2025) SAP extends support deadline for getting off legacy software – in very special circumstances. The Register, January 28. Available at: https://www.theregister.com/2025/01/28/sap_extends_support_deadline/

Ghoshal, A. (2026) Microsoft targets Salesforce customers with AI-powered Dynamics 365 migration tool. CIO, September 10. Available at: https://www.cio.com/article/4220712/microsoft-targets-salesforce-customers-with-ai-powered-dynamics-365-migration-tool.html

Zwets, B. (2026) Microsoft aims to attract Salesforce customers to Dynamics 365 using AI. Techzine Global, September 10. Available at: https://www.techzine.eu/news/applications/144215/microsoft-aims-to-attract-salesforce-customers-to-dynamics-365-using-ai/

Research this note builds on

Greyhound Research (2025a) Salesforce Acquires Informatica: What This Means for AI Trust. Research note, May 28. Available at: https://greyhoundresearch.com/salesforce-acquires-informatica-what-this-means-for-ai-trust/

Greyhound Research (2025b) How Microsoft’s Researcher And Analyst Copilot Agents Are Transforming Enterprise Workflows With AI Reasoning. Research note, July 14. Available at: https://greyhoundresearch.com/microsofts-copilot-gets-a-brain-what-researchers-and-analysts-mean-for-enterprise-workflows/

Greyhound Research (2025c) Dismantling SaaS Silos: The Role of AI In Integration. Research note, July 26. Available at: https://greyhoundresearch.com/dismantling-saas-silos-the-role-of-ai-in-integration/

Greyhound Research (2026a) Oracle Agentic Implementation – When Agents Draft The Setup, Review Becomes The Control. Research note, October 29. Available at: https://greyhoundresearch.com/oracle-agentic-implementation-when-agents-draft-the-setup-review-becomes-the-control/

Greyhound Research (2026b) Oracle AI Security – When AI Finds The Flaws Faster, Fixing Becomes The Control. Research note, October 29. Available at: https://greyhoundresearch.com/oracle-ai-security-when-ai-finds-the-flaws-faster-fixing-becomes-the-control/

Greyhound Research (2026c) The Front Door Race – Oracle, OpenAI And Five Rivals, And Why The Permission Becomes The Control. Research note, November 5. Available at: https://greyhoundresearch.com/oracle-openai-the-front-door-race-the-permission-becomes-the-control/

Greyhound Research (2026d) Microsoft Azure Agent Infrastructure – When Agents Get Their Own Machines, Authority Becomes The Control. Research note, November 2026. Available at: https://greyhoundresearch.com/microsoft-azure-agent-infrastructure-when-agents-get-their-own-machines-authority-becomes-the-control/

↑ Back to the section guide

Part 8Appendix, Sources, And Disclosures

The evidence in this research note is current through November 19, 2026, with an evidence cutoff of 00:50 UTC that day. Every source was first read on November 18, 2026, the day after Microsoft’s Ignite announcements, and was read again between 00:28 and 00:50 UTC on November 19, 2026. No Microsoft Learn documentation for Dynamics 365 Activate was found by that time. Any written response received from an organization named in it after that time is dated where it appears.

Independence Disclosure

Research under the Greyhound Research brand is independent, and no organization holds a right of approval over its content or publication. It is not commissioned, sponsored, or funded by any organization it covers. Greyhound Research may send a research note to companies named in it for factual review before publication. Any such review is confined to the correction of fact, and no viewpoint, conclusion, or recommendation is guided by those companies. All insights and recommendations are Greyhound Research’s alone, and editorial control remains entirely with Greyhound Research. Greyhound Consilium is the B2B thought-leadership arm of The House Of Greyhound and a sister brand to Greyhound Research. It builds on Greyhound Research’s independent research through collaborations that produce thought-leadership content, research, and practical toolkits for decision-makers. Every Greyhound Consilium publication names its partner on the face of the document. This research note is published under the Greyhound Research brand.

Financial Disclosure

Greyhound Research undertakes advisory and consulting engagements with enterprise buyers and technology providers, and no such engagement confers control over its research findings or its decision to publish them. For this research note, Greyhound Research has no financial interest in, and no commercial relationship with, Microsoft, Amazon Web Services, Google, Anthropic, or OpenAI to declare. Oracle is a client of Greyhound Research. Oracle is not a subject of this research note.

Intended Use

This research note is written for chief information officers, heads of business applications and enterprise architects, chief financial officers, procurement and vendor management leaders, chief data officers, board members, and the press. It reads Microsoft’s Dynamics 365 Activate and Copilotforce announcements at Microsoft Ignite 2026, the announcements beside them, and Salesforce’s and SAP’s own published statements, to inform decisions on CRM and ERP renewals, migration, coexistence, and contracts. This research note is not investment advice, a recommendation to buy, sell, or hold any security, or a view on any company’s share price or valuation. It is not legal advice, and its reading of contract and maintenance terms is to be confirmed with counsel and with each vendor. Its assessments rest on the documents listed in Sources And References as they stood on November 19, 2026, and can change as the companies named publish more. Product availability, status, dates, features, and prices are described as each company published them through November 19, 2026, so confirm them with the vendor before acting on them.

Research Methodology

Greyhound Research’s analysis combines lived experience with public sources. The lived experience is years of continuously tracking the market, Greyhound Fieldnotes from ongoing advisory engagements with enterprise buyers and with technology providers, and Greyhound Pulse, the firm’s market trackers. Lived experience forms the judgment and never stands in for evidence. The public sources are the twenty-two documents listed in Sources And References, in four classes, and every factual claim is verified against the document that supports it. The passages relied on are quoted in The Deeper Read of the section that uses them, and the other words taken from each source, the passages summarized rather than quoted and the reading notes, are set out in the appendix. A finding that something is not stated or not documented is bounded to the documents the text names, as they stood at 00:50 UTC on November 19, 2026. Statuses are given as each company states them, and where two Microsoft pages disagree, both are reported.

Salesforce’s and SAP’s positions are taken from their own announcements and, for SAP, also from statements made in January 2025 by an SAP spokesperson and by Christian Klein, SAP’s CEO. Speed and scale figures from Microsoft, its partners, and SAP are company or partner claims and are not used to compute any estimate. The Greyhound CIO Pulse figures are cited as published in Greyhound Research’s research notes of May 28, 2025, and October 29, 2026. Earlier Greyhound Research comments published in the press, in December 2025 and January 2026, are quoted word for word and attributed to Greyhound Research with their date. No composite figure is computed. No Greyhound Fieldnotes are quoted, and no factual claim in this research note rests on unpublished material.

The reading of the two signals, the Activate steps, the fidelity layers, the coexistence terms, the renewal positions, the readings in Exhibits 1 to 7 and Tables 1 to 7, the risks, the Greyhound CXO Runbook, the questions for Microsoft, the signals, and every term proposed for a contract are Greyhound Research’s analysis, not statements by Microsoft, Salesforce, SAP, or any other company. Quotations are checked against the live source before publication.

Authoring Disclosure

This material reflects the analysis, viewpoint and editorial judgment of Greyhound Research. The position presented is developed from Greyhound Research’s research, advisory work and accumulated institutional knowledge. Depending on the assignment, AI may be used to retrieve relevant material; structure, draft or polish prose from analyst-provided concepts, dictation, notes, rough drafts and source material; support secondary research and factual cross-checking; and assist with editing, condensation and consistency with Greyhound Research’s house style. AI does not independently establish Greyhound Research’s viewpoint, analytical position or conclusions. Material factual claims are verified against source evidence before release. Greyhound Research reviews and approves the final material and retains responsibility for it.

All content in this document and on the Greyhound Research website is protected by copyright law and may not be reproduced, distributed, transmitted, displayed, published, or broadcast without the prior written permission of Greyhound Research or, in the case of third-party materials, the prior written consent of the copyright owner of that content. You may not alter, delete, obscure, or conceal any trademark, copyright, or other notice appearing in any Greyhound Research content. Quotation of up to one hundred words is permitted where it carries attribution to Greyhound Research and a link to the published page. Reproduction, redistribution or republication beyond that extent, in whole or in part, by email or in any medium including websites, newsletters and intranets, requires prior written permission, which may be requested at the address below. The published version of each content piece on the Greyhound Research website carries sharing tools for readers who wish to share it.

For questions arising from these disclosures, including licensing requests, contact the Greyhound Research Community Relations Team at connect@thofgr.com. For media inquiries, write to media@thofgr.com.

↑ Back to the section guide

Analyst In Focus: Sanchit Vir Gogia

Sanchit Vir Gogia, or SVG as he is popularly known, is a globally recognized technology analyst, innovation strategist, digital consultant and board advisor. SVG is the Chief Analyst at Greyhound Research (part of The House Of Greyhound), a Global, Award-Winning Technology Research, Advisory, Consulting & Education firm. Greyhound Research works closely with global organizations, their CxOs and the Board of Directors on Technology & Digital Transformation decisions.


Discover more from Greyhound Research

Subscribe to get the latest posts sent to your email.

Discover more from Greyhound Research

Subscribe now to keep reading and get access to the full archive.

Continue reading