Case studyMS Dynamics

One Rulebook for Leads and Cases: StoneX Retail's Salesforce to Dynamics 365 Migration

Leads, Cases and other records in StoneX's retail CRM share one assignment framework. We supported the migration from Salesforce to Microsoft Dynamics 365. We also aligned assignment, routing, case intake and escalation with the required business processes. Chat and email requests are captured as cases, with forms for each case type.

Talk to a CRM expert
Case study: One Rulebook for Leads and Cases: StoneX Retail's Salesforce to Dynamics 365 Migration
MS Dynamics

About the client

StoneX is a global financial services firm. It connects businesses, institutional clients, traders, investors and retail customers to financial markets worldwide. Its services include market access, trade execution and clearing, risk management, market intelligence and payments. Its operations span multiple regions, so client servicing and case management need systems and processes that scale.

What we did

  1. 1

    Supported the migration from Salesforce to Dynamics 365. This meant adapting existing processes and business logic to Dataverse and the Power Platform, while keeping the required business behavior.

  2. 2

    Built one reusable assignment framework for Leads, Cases and other records. It replaces separate assignment logic for each record type with one common, maintainable approach.

  3. 3

    Implemented a unified routing approach, so the same defined criteria apply across supported case and record-handling processes.

  4. 4

    Worked on chat-to-case and email-to-case. Incoming chats and emails are captured as Dynamics 365 cases, which supports consistent handling across channels.

  5. 5

    Configured case forms by case type, so agents see the fields and sections that matter for each kind of case.

  6. 6

    Added escalation rules based on defined business conditions and case criteria. They flag cases that need more attention and apply the right escalation.

  7. 7

    Used server-side plugins for most business logic where efficiency was a priority. Kept Power Automate flows where a workflow fit better.

Sound familiar?

Facing similar challenges in your CRM?

Talk to a CRM expert

The results

One assignment framework for Leads, Cases and other records, in place of separate rules for each record type.

More consistent routing and handling of records across the supported processes.

Chat and email requests captured as cases, with forms suited to each case type and defined escalation rules.

The required retail CRM processes, adapted to Microsoft Dynamics 365 as part of the move from Salesforce.

*Delivered as Vegacompass.

Services used

The service behind this work.

This is a service we deliver. Follow it to see how it works on its own.

CRM Platforms

MS Dynamics

Explore this service

More outcomes like this

All case studies →
Next step

Your story could be the next one.

Bring us your CRM problem. A 30-minute conversation with a senior consultant. No deck, no pitch, just your CRM and your revenue goals.

Talk to a CRM expertor email [email protected]
Salesforce to Dynamics 365 Migration Case Study: StoneX