Southeast Toyota Distributors logo
CUSTOMER SUCCES STORY

How Southeast Toyota Distributors Turned 50 Years of Mainframe Knowledge Into a Blueprint for Dynamics 365

Southeast Toyota Distributors,  a JM Family Enterprises company, used Mavim to capture how its associates move vehicles and parts to dealers.
That shared record gave associates and implementation partners a way to check design decisions together and prepare teams
for how their work would change.

SOUTHEAST TOYOTA DISTRIBUTORS AT A GLANCE

 

Industry
Automotive distribution   

Headquarters
Deerfield Beach, Florida, United States 

Project Scope
Drive, a multiyear program to replace SET’s legacy mainframe and move vehicle and parts distribution processes to Microsoft Dynamics 365

Transformation Focus
Defining how associates will work in Dynamics 365 and preparing business teams for changes to their daily responsibilities 

Mavim’s Role
The shared process repository where SET and its partners document current operations, design future workflows, and record what will change for each team 

ABOUT SOUTHEAST TOYOTA DISTRIBUTORS

Southeast Toyota Distributors is the world’s largest independent distributor of Toyota vehicles. Part of JM Family Enterprises, SET supplies vehicles, parts, and accessories to 178 independent Toyota dealerships across Alabama, Florida, Georgia, North Carolina, and South Carolina. Its facilities in Florida and Georgia process vehicles built in North America and Japan for delivery to dealers across the Southeast. 

THE CHALLENGE

Replacing a Mainframe That Held 50 Years of Business Knowledge

For nearly 50 years, SET associates had used the same mainframe to keep vehicles and parts moving to dealers. Over that time, the company had customized the system around the way its business worked. Even the language teams used to describe their jobs had grown out of its screens and routines.

When SET launched Drive, its implementation partners needed to understand which of those routines mattered and why. Much of that knowledge sat with a handful of experienced associates. Asking them to explain each process again whenever a design question came up would take them away from daily operations. And when two people described the same task differently, partners needed to know which version to design for.

THE APPROACH

Starting With the Work Associates Knew Best 

Agree on how the business
works today

Early in Drive, a senior leader asked the team to document current operations before defining requirements for Dynamics 365. Associates mapped their processes in Mavim, worked through differences, and agreed on a version they could share with implementation partners.

Use that record to make
design decisions

SET checked proposed requirements against the process they were meant to support. Power Automate linked processes in Mavim to work items in Azure DevOps, where the delivery team managed requirements through approval and development. As design progressed, SET began mapping future workflows down to the individual role, task, and Dynamics 365 activity.

Bring change management
into solution design

SET’s change management team helped decide what to capture alongside each process, from a change in terminology to a shift in responsibility. Power BI dashboards in Mavim gave the team a way to show department leaders what the transition would mean for their associates.

THE RESULTS

A Shared Record Saved Time During Solution Design

  • Less time spent re-explaining processes. John Robertson of SET estimated that having an agreed process record saved at least 30% of the time spent establishing how work was done in design conversations. Partners could revisit the record whenever a question resurfaced.
  • A way to check requirements against actual work. During future-state design, SET teams returned to the original process maps to verify that a proposed Dynamics 365 design would meet the business need it was intended to address.
  • Clearer conversations with department leaders. The change management team could use its dashboards to discuss specific changes with each department, including which tasks, terms, and technologies its associates would encounter.
  • A commitment to document future operations. After seeing the value of the current-state maps, stakeholders agreed to build process documentation into design, build, and testing. That gave future-state mapping a place in the delivery plan from the outset.
CUSTOMER PERSPECTIVE


quote (1)

“The moment we share that digitally with our partner, they have the version of truth that we say we all agree on.”

JOHN ROBERTSON, Southeast Toyota Distributors 

KEY TAKEAWAYS

Give Implementation Partners a Process Everyone Agrees On

SET’s design conversations became more productive once associates agreed on how a process worked and gave partners a record they could revisit. When a new requirement came up, the team could start with a specific question: Would the proposed Dynamics 365 workflow support the work associates needed to do?

RELATED CASESTUDY'S

Explore More Customer Stories

Discover how other organizations use Mavim to create process clarity, align teams, and build a stronger foundation for transformation.

KIWA

A Process-First Foundation for Dynamics 365 and AI

See how Kiwa connected its business processes to the Microsoft Business Process Catalog to prepare for Dynamics 365 modernization and future AI adoption.

 

READ THE CUSTOMER STORY → 

ZEPPELIN CAT

Standardized Dealer Operations
for Dynamics 365 

Explore why documenting how a dealership works today is an important starting point for planning a Dynamics 365 transformation.

 

READ THE CUSTOMER STORY →  

 

KRAMP

Building the Foundation
for Change at Kramp

Hear how Kramp identifies process dependencies and training needs as it introduces new systems across its European wholesale business. 

 

WATCH THE CUSTOMER STORY →  

START YOUR TRANSFORMATION

Which Process Should You Map Before Moving to Dynamics 365?

Bring one workflow your implementation team needs to understand. Talk with a Mavim expert about how to capture the steps with the people who do the work, check the requirements against those steps, and identify what will change for each role.