How Does a Dynamics SL Upgrade Really Work?

Dynamics SL Upgrade Methodology

Is it time for an upgrade to the latest version of Dynamics SL?  If so, Crestwood Associates is poised to help you through this complex process. We bring resources to the table with years of expertise to make the experience as stress free as possible for our customers.

Here’s what we do:

    1. Verify which version of SL and SQL is being upgraded. This determines whether it will take 1 or 2 passes to upgrade the database in SQL.
    2. Verify local admin on all servers
    3. Turn off UAC on new server. “Must reboot after”
    4. Verify .net 3.5 or later is installed on SL Server.
    5. Install/Configure SQL (make sure you set SQL/Windows compatibility, also set up your user as administrator)
    6. Download software – SL 2015, CU2 (make sure to include 3rd party and integrated products).
    7. Create new DBs in new SQL Server (name must match old server) System and App dbs.
    8. Backup databases from old version (then copy to new SQL server) and restore to new SQL server databases.
    9. Install SL2015 (locate which version of SL to install by logging into current SL, go to Help, About – should show Professional, Adv Mgmt, etc.)
    10. Install SL2015 CU2
    11. Update Domain table in system db in SQL – server name to new server name
    12. SL Database Maintenance (under Administrative Tools) Upgrade databases – select Windows Authorization – use your user as admin user
    13. Change to SQL Authorization (if using Windows Authorization, change back to Windows Authorization again) – Master80 is created from this step
    14. Sync Ownership (make sure everyone is out if SL)
    15. Log onto old server, export Customizations from within Dynamics SL (Administration, Export Customizations – only All Users ones, not Self).
    16. Copy over Usr_rpts directory from old server to new directory, same place.
    17. Delete custom, custom2 and customvba tables from new system database in SQL
    18. Download SL unlocking keys from Partnersource
    19. Download all 3rd party unlocking keys from 3rd party vendor (make sure they are current on enhancement)
    20. Log into SL, register, log out
    21. Log back into SL, Run DBUpdate in SL
    22. Install BSL Components
    23. Import customizations (Administration, Import Customizations)
    24. Share Microsoft Dynamics folder/Security – give full permissions to share and full permissions to Security
    25. Install Crystal 2008 (from install cd)
    26. Install PSTL/Bus analyzer
    27. Install SL User Guides/copy MR user guide
    28. Install 3rd party products if applicable
    29. Modify solomon.ini (change FRx, Crystal and MR locations, for go-live), update QQ lines/pages, AP quick check
      Get users going:
    30. Add roles for Quick Query
    31. Set security for all SQL long user id’s (CD…./E…, etc.) to Read/Write SQL for App/System dbs
    32. create backup maintenance plan in SQL
    33. Install any applicable hotfixes
    34. Work with client to begin User Acceptance Testing (UAT)
    35. Testing can take a week or several months depending on the environment
    36. Provide New Feature training to users
    37. Once the UAT has been completed and signoff has been received confirming that the test environment is fully functional, the live upgrade is scheduled
    38. Access to the old server is removed to prevent entering data into the wrong database
    39. Take a new backup of databases
    40. Restore database over test and cycle back through previous steps to upgrade databases
  1. **restore test system db back (*only during live upgrade). This step ensures that the changes that were made during test are intact
  2. Resolve any issues documented during testing phase
  3. Go Live
  4. Post Go Live – Crestwood is here to support you

Read more on things to consider and planning tips for your upgrade.

If you have further questions, or want to schedule your upgrade, contact us at



Leave a Reply