Dynamics SL
User group community for the Dynamics SL application.
Organizer:
- JOSE Organized by
-
-
Dynamics SL EOL Advice
-
Dynamics SL EOL Advice
Question for other Dynamics SL users
Hi Y’all. I’m new to this forum and didn’t even know this existed so I’m glad I’ve gotten some light from seeing other discussions but didn’t find what I’m looking for so here’s my story. Weāve been on Microsoft Dynamics SL for a long time and itās been a solid system for us. With the general shift toward cloud ERP, weāve started having some internal conversations about what the future might look like.
For anyone who has evaluated or moved off SL:
What was the most challenging part?
How did data migration go?
Any surprises with reporting or customizations?
How disruptive was the transition for your team?
Just trying to learn from othersā experiences and understand what to realistically expect. Sorry for tall the bullet questions in advance. Thanks again and any feedback helps!
-
1 Reply
-
Hi Lloyd,
We went through a similar evaluation after being on Dynamics SL for many years. Overall, the biggest challenge wasn’t the software migration itselfāit was rethinking existing business processes and deciding which customizations were still truly needed.
Data migration took more effort than expected, especially around historical project data, custom fields, and reporting requirements. Master data was relatively straightforward, but cleaning old or inconsistent data before migration became a significant task.
Reporting was another area that required attention. Many of our users had become comfortable with SL reports and Excel-based processes. While modern ERP platforms offer more powerful reporting and analytics, recreating some legacy reports and validating the numbers took time.
Regarding customizations, we discovered that several custom developments had been built over many years to compensate for limitations or unique business requirements. During the evaluation process, we found that some could be replaced with standard functionality, while others required additional configuration or extensions.
From a change management perspective, user adoption was probably the most disruptive element. People had been using the same screens and workflows for years, so training and communication were critical. The organizations that seem to have the smoothest transitions are the ones that invest early in user engagement rather than treating the project as purely a technical migration.
My recommendation would be to start with a thorough assessment of:
Current customizations
Integrations
Reporting requirements
Historical data retention needs
Business processes that have evolved over time
You’ll likely find that the migration is as much a business transformation project as it is an ERP replacement project.
Best of luck with the evaluation. SL has served many organizations well, but planning early and understanding your requirements in detail will make the transition much smoother when the time comes.
Log in to reply.
