What do I need to do to prepare for my upgrade?

DM2-ERP-CRM-Wheel-with-imagesWhether you’re still considering an upgrade or have already submitted your Upgrade Evaluation request, here are some things you can do to prepare for your upgrade:

Check out our New Feature Summary to learn about the new features you’ll be receiving

Find out what Hardware and Operating Systems are required for your upgrade

Log in to PDI Connections to get started

Frequently Asked Questions:

How long does an upgrade take?
It varies depending on modules, custom programming, required forms and reports, amount of user testing needed, etc.  Once you’ve submitted your Upgrade Evaluation request, you can expect your upgrade to take between 2 to 6+ months, based on the following company size and user count estimates:

Small & CardLink Only (1 -10 users) – 2 to 3 months
Medium – (11 – 25 users) – 3 – 6 months
Large (26 – 50 users) – 4 to 6 months
Extra Large (50+ users) – 6+ months

What’s involved in an upgrade?

Similar to system installations, standard upgrades follow a proven 9 Phase process consisting of the following phases:

Phase 1 – Upgrade Evaluation

  • Review of system programming code and custom programming code comparison (if applicable) to latest production release to determine what custom programming may no longer be required due to system enhancements
  • Identify training requirements based on system and module usage
  • Develop test plan and test environment
  • Subscription only – provide estimate of any optional services required (standard upgrades are facilitated by running Crystal Report, Custom Office, Motor Fuel Tax, and Visual Integrator Jobs conversion utilities. Optional services may be required to modify existing reports and/or forms if table or field names changes are required)

Phase 2 – Upgrade Authorization

  • Review and approve upgrade timeline estimates and scheduling
  • Upgrade projects will be added to the upgrade schedule based on a mutually agreed upon schedule

Phase 3 – Programming (only applicable to if you have added custom programming to your system)

  • Estimate programming timeline based on scope of work
  • Develop programming schedule

Phase 4 – DM2 Bench-testing

  • In house testing based on a mutually agreed upon test plan to check for check for any major operational issues with the system (User Acceptance Testing will be more extensive)
  • Timeline will vary depending on complexity of the Test Plan

Phase 5 – User Acceptance Testing & Training

  • Remotely walk-through system revisions and provide basic training to facilitate user acceptance testing
  • Provide additional review and hands on training of other features and functionality currently being used that have undergone significant changes
  • Identify the need for additional training on the key new features and functionality introduced by your upgrade (see New Feature Summary)
  • Provide optional new feature and functionality training and/or “Refresher” re-training as needed
  • Work with end users to update and/or create user training documentation
  • Obtain User Acceptance testing sign-off to ensure a successful Go Live

Phase 6 – Pre-Go Live Checklist

  • Verify and test workstation and/or server connections
  • Confirm Go Live timeframe
  • Verify user acceptance testing checklists
  • Backup confirmation document signed and returned
  • Confirm all requirements related to system status i.e. no open batches

Phase 7 – Go Live

  • Run conversions and migration utilities (your system will be unavailable during this time – downtime depends on scope of your upgrade project and speed of your hardware. DM2 will provide you with an estimate for any downtime requirements)
  • Work with end users to ensure internal controls are being followed
  • Verify that the system is operating as expected

Phase 8 – Transition to Support Services

DM2 Upgrade consultants will be the primary contact during upgrades and approximately one week after Go Live for any issues that may arise.  After that time, DM2 Support will continue to provide general support.

Phase 9 – Tracking and Feedback Survey

  • Continue to Track any open items or post-Go Live issues until resolved
  • Provide feedback on the upgrade process

Log in to PDI Connections to get started

What type of hardware do I need? Find out what Hardware and Operating Systems are required for your upgrade

Will my forms and reports be brought over?
Some forms and reports go through an automatic conversion, but based on your current version, some may need to be manually converted. DM2 will evaluate this during the Upgrade Evaluation phase and provide an estimate as needed.

What happens during the live upgrade day?
All open batches will be updated and all users will log out of the prior version system. Then, DM2 will begin the process of converting your data to the new version. Once the conversion is done, users will login and start processing transactions in the new version. You can expect all users to be logged out for an entire business day, but the time will vary based on the size of your company.

Do I get support after my upgrade?
Yes. An upgrader will work directly with you for the first week after go live to ensure you are stable. After that time period is completed, you will be re-instated with your full DM2 Support services, and Support will be your primary contact moving forward.

Do all journals and registers need to be updated prior to go live?

Can I have open batches prior to go live?

Can I have open orders prior to go live?

Can I have my inventory frozen prior to go live?

Can I have CardLink transactions in process?
No. We recommend updating any CardLink transactions in process before your live

Does everyone need to be logged out during the live upgrade?
Yes. No one will have access to MAS during the live upgrade conversion process.

Should I upgrade to Sage 100 Standard, Advanced, or Premium?
DM2 recommends moving to a client/server version of Sage 100 like Advanced or Premium for user counts greater than 5. Premium is only recommended for customers who want to convert their database to SQL to take advantage of the reporting options available in SQL. If you are going to stay with Sage 100 Standard, the best practice is for the MAS90 folder to be on the local drive of the terminal server and users only access it through that one terminal server. It’s not recommended for the MAS90 folder of Sage 100 Standard to be accessed by multiple terminal servers on a separate server.

Log in to PDI Connections to get started