Upgrading to iMIS Cloud

iMIS Cloud is the latest edition of iMIS. Many users have already started upgrading to iMIS Cloud from iMIS 2017.

Important!
Considering an upgrade? If so, here are a few important details to know:
— You must be on the latest version of iMIS 2017 with the latest service pack applied.
— There are multiple upgrade paths to consider.
— The Desktop will not be available in the upgraded version.
— All non-standard iMIS objects will be removed upon upgrade.

Understanding the differences between iMIS 2017 & iMIS Cloud

The following are the major differences between iMIS 2017 and iMIS Cloud:

  • There is no more iMIS Desktop, but many of the Desktop features were migrated to the Staff site. Review the Desktop migration to the Staff site article to see which features were migrated.
  • The ability to use custom stored procedures has been removed.
  • Access to SQL tools has been removed.

Upgrade options

Important!
If you are on a version of iMIS prior to iMIS 2017 and would like to upgrade to iMIS Cloud, you must first upgrade to iMIS 2017 with the latest service pack applied. Contact your AiSP or ASI Technical Support to learn how you can upgrade to iMIS 2017. After you are upgraded to iMIS 2017, follow the upgrade option best suited for your organization.

The following three options outline how to begin the upgrade process based on how your iMIS database is hosted. If you do not know how you are hosted, please contact ASI Technical Support.

1) Hosted by ASI with a VDS

This option applies to you if the following are true:

  • Version: iMIS 2017 with latest service pack applied
  • Hosting: ASI with a Virtual Dedicated Server (VDS)

If you are hosted by ASI and have a VDS, all VDS requirements must be removed before upgrading to iMIS Cloud.

The following is the upgrade process for those who are hosted by ASI with a VDS:

  1. Interested clients enter a support ticket to Cloud Services requesting that the database customization script and additional complexities scripts be run.
  2. ASI Cloud Services determines how many customizations the client has by running the ListNonImisDatabaseObjectNames.sql script against the client's database.
  3. Note: This script identifies customizations, such as tables, views, and stored procedures that are not out-of-the-box iMIS functionality. One exception is iMIS Customizer tables.

  4. ASI Cloud Services determines the additional complexities that may be involved in the upgrade by running the AddlComplexities.sql script against the client's database.
  5. Contact your dedicated Client Performance Improvement Leader and set up a meeting to discuss the direction that your organization should take.

2) Hosted by ASI

This option applies to you if the following are true:

  • Version: iMIS 2017 with latest service pack applied
  • Hosting: ASI without a Virtual Dedicated Server (VDS)

Clients that fall into this category are offered a free upgrade program. This program is a six-week testing process that allows clients to fully test their own iMIS data in the iMIS Cloud before a live upgrade.

The following is an outline of the free Cloud Upgrade Program:

  1. Interested clients enter a support ticket requesting a meeting with an iMIS Cloud representative.
  2. ASI creates a test site for the client. The test site is how the client tests iMIS Cloud.
  3. ASI schedules a kickoff meeting with the client. The kick-off meeting is an introduction to the Cloud Upgrade Program and marks the beginning of the client's participation in the Cloud Upgrade Program.
  4.  Client begins testing iMIS Cloud.
  5. A go-live date is scheduled after the client finishes their testing. When the go-live date is set, a new support ticket is opened with the upgrade details.
  6. The client's live site is upgraded on the agreed upon date and time.
  7. The client works with the upgrade team for one-week post-upgrade to make sure the transition from iMIS 2017 to iMIS Cloud is smooth.

3) Self-hosted/On premise/Not hosted by ASI

This option applies to you if the following are true:

  • Version: iMIS 2017 with the latest service pack applied or earlier version
  • Hosting: Self-hosted/on premise (not hosted by ASI)

The following is the upgrade process for those who are not hosted by ASI:

  1. Upgrade database to iMIS 2017 with the latest service pack if this is not already the case.
  2. Run the ListNonImisDatabaseObjectNames.sql script against your database to determine how many customizations you have.
  3. Note: This script identifies customizations, such as tables, views, and stored procedures that are not out-of-the-box iMIS functionality. One exception is iMIS Customizer tables. Run the script in SSMS and not in the iMIS Desktop.

  4. Run the AddlComplexities.sql script to identify potential areas of complexity that might need further investigation prior to upgrading.
  5. Note: Review the ReadMe file before running the AddlComplexities.sql script.

  6. Compile the information gathered after running the scripts against your iMIS database.
  7. Contact your dedicated Client Performance Improvement Leader and set up a meeting to discuss the direction that your organization should take.