Samit Roy's Journey From Electrical Engineer to D365 Solution Architect

How do you build the experience and skills needed to become a trusted solution architect in the world of enterprise ERP?

In this episode of The Catch Up Podcast, host Phil Blackmore speaks with Samit Roy, an experienced D365 Finance and Operations solution architect, about his two-decade journey from electrical engineering through Dynamics Great Plains, AX 2009, AX 2012, and into the modern D365 ecosystem. They explore the hard-won lessons from working across partner and end-customer environments, the importance of getting out of your comfort zone as a freelance consultant, and why solution architects must bring far more than product knowledge to the table.

With Microsoft Dynamics 365 recently named a Leader in three Gartner Magic Quadrant reports and research showing that effective project risk management can boost on-time completion rates by up to 90%, Samit explains why early engagement of a solution architect is critical, how to avoid common ERP pitfalls like poor data migration and unchecked customisation, and what separates good architects from great ones: curiosity, empathy, and the ability to ask the right questions at the right time.

From navigating the transition between product versions to putting yourself in the customer's shoes, this conversation offers a practical roadmap for aspiring solution architects and a reminder for organisations embarking on ERP transformation that investing in architectural expertise from day one pays dividends throughout the project lifecycle.

• (00:00) - Welcome to The Catch Up Podcast
• (02:03) - Early Career: From Electrical Engineer to ERP
• (03:36) - The Origins of Dynamics and Great Plains
• (05:24) - Moving to the UK and Dynamics AX
• (06:23) - Working at ePartners and Small Project Teams
• (10:00) - The Transition from AX 4 to AX 2009
• (12:35) - Moving from Partner to Freelance Consulting
• (16:15) - The Challenge of Working Outside Your Comfort Zone
• (22:02) - Transitioning to Solution Architect Roles
• (27:42) - What Solution Architects Bring Beyond Product Knowledge
• (34:34) - Common ERP Pitfalls and How to Avoid Them
• (39:14) - What Makes a Good Solution Architect
• (44:45) - Advice for Organisations Embarking on D365 Implementation

Samit Roy: Samit Roy is an experienced D365 Finance and Operations solution architect with over 20 years' expertise in Microsoft Dynamics ERP implementations. His career began with Dynamics Great Plains in India before relocating to the UK in 2005 to work with Dynamics AX, progressing through AX 4, AX 2009, AX 2012, and into the modern D365 ecosystem. Samit has worked across both partner and end-customer environments, delivering complex, large-scale ERP programmes for multinational organisations in sectors including manufacturing, distribution, and professional services. His architectural approach combines deep functional and technical knowledge with a focus on business outcomes, change management, and long-term system sustainability. Samit transitioned to freelance consulting in 2011, working on implementations ranging from six-month projects to multi-year, multi-geography transformations, and is known for his pragmatic, empathetic style and ability to translate complex technical concepts into decision-ready language for boards and senior stakeholders.

Episode Insights:

• Becoming a solution architect requires at least a decade of hands-on experience across multiple projects, environments, and product versions—there are no shortcuts to building the breadth of knowledge and pattern recognition needed for the role.
• The best solution architects are not necessarily experts in every feature of the product but have deep core knowledge, broad business exposure, and the intellectual curiosity to ask incisive questions and understand what the client truly needs.
• Early engagement of a solution architect—ideally from the discovery phase—dramatically improves project outcomes by surfacing risks, guiding phased vs big-bang decisions, and ensuring design choices support long-term resilience, not just go-live.
• Common ERP pitfalls such as poor data migration, unchecked customisation, and performance issues can often be avoided with experienced architectural oversight that challenges assumptions and applies lessons learned from previous projects.
• Transitioning from a partner environment to freelance consulting forces consultants out of their comfort zone, accelerating skill development and building the self-reliance and troubleshooting instincts that define strong solution architects.

Action Points:

1. Engage a solution architect from day one: Involve an experienced solution architect during the discovery and design phases, not as an afterthought when problems arise. Early architectural input shapes critical decisions around scope, phasing, data migration, and customisation, setting the foundation for long-term project success and helping avoid costly course corrections later.
2. Build broad experience before specialising: If you aspire to become a solution architect, prioritise gaining hands-on exposure across multiple projects, industries, and both partner and end-customer environments. Work in areas outside your core expertise—data migration, integrations, reporting—and take every opportunity to understand how different parts of the ERP ecosystem interconnect.
3. Challenge customisation requests with business-case scrutiny: Question every proposed customisation by asking whether it solves a genuine, enduring business need or simply replicates the old system. Ensure stakeholders understand the long-term cost, upgrade risk, and maintenance burden of custom code, and push for out-of-the-box functionality wherever possible.
4. Avoid common data migration mistakes: Do not start master data numbering sequences with leading zeros, as they will be dropped when data is extracted to Excel, causing chaos downstream. Plan data migration as a strategic workstream with proper validation, cleansing, and testing, and use purpose-built tools rather than direct table imports.
5. Adopt a phased approach for complex implementations: For organisations with geographical spread, multiple business units, or high complexity, resist the temptation to go live everywhere at once. A phased rollout allows teams to learn, adapt, and apply lessons from early deployments, creating a more controlled and manageable transition with better outcomes.

The Catch Up Podcast brings you candid conversations with industry leaders, consultants, and change-makers from the Microsoft Dynamics and tech ecosystem. Hosted by Phillip Blackmore, Sales Director at Catch Resource Management, each episode dives into the real stories behind business transformation, career pivots, and scaling success. Expect thoughtful interviews, practical insights, and honest reflections.

Brought to you by Catch Resource Management, a leading UK recruitment specialist for Microsoft Dynamics and ERP talent, this podcast is your inside track to the people shaping the future of enterprise technology. Tune in for new episodes and stay ahead of the curve.

The Catch Up Podcast is produced by ...