Client Context
A growing professional services firm needed to migrate its core systems to Microsoft 365. The firm operates in a high-stakes environment where reliability, confidentiality, and continuity are critical. Daily operations could not pause, and tolerance for error or disruption was extremely low.
The engagement required not only technical execution but careful attention to how people work, how knowledge is shared, and how risk is managed during change.
The Challenge
While the initiative involved a technology migration, the real challenge was organizational.
Key conditions included:
- Limited internal IT capacity
- Knowledge embedded in individuals rather than documentation
- Shared ownership across internal staff and external partners
- High anxiety around downtime, access, and client communication
Treating the work as a purely technical project would have increased risk and post-migration friction. Success required managing behavior, clarity, and continuity alongside execution.
The Approach
The engagement was designed using principles from change management, organizational development (OD), and Industrial-Organizational (I-O) Psychology.
Change Management & Risk
- Clarified roles, responsibilities, and ownership
- Made risk explicit, including rollback and contingency planning
- Sequenced work to reduce disruption and cognitive overload
Organizational Development
- Revisited and refined existing process maps and job analyses
- Aligned tools to how work actually occurs
- Strengthened accountability and handoffs across workflows
I-O Psychology
- Designed communication to support psychological safety
- Reduced uncertainty by making expectations visible
- Treated staff as active participants in the change
Knowledge Continuity
- Captured and documented critical workflows
- Created durable “how-to” artifacts and guidance
- Reduced dependency on individual knowledge holders
Planning & Implementing the Change
With organizational foundations in place, execution included:
- Developing a strategy and plan for meeting business requirements and deadlines
- Microsoft 365 migration (email, calendars, contacts)
- Domain and DNS management
- File structure and access alignment
- Coordination with line-of-business systems
Execution succeeded because it was grounded in clear ownership, aligned processes, and thoughtful change leadership.
Outcomes
- No disruption to day-to-day operations
- Reduced post-migration support needs
- Clear accountability for systems and vendors
- Increased staff confidence and adoption
- A more resilient foundation for future change
Key Insight
For expanding professional services firms, technology migrations are rarely just IT projects. They create moments of organizational stress that expose gaps in process, ownership, and knowledge.
When approached as organizational change, migrations can reduce risk, strengthen capability, and leave the organization better prepared for what comes next.