Important! Before upgrading through the iMIS 20/20 Advance Program, you must be licensed accordingly. If you are unsure about your licensing, contact your CPIL.
The iMIS 20/20 Advance Program is a transitionary step to assist the self-hosted/on premise or traditionally-hosted clients in getting to the latest version of iMIS EMS. Although the iMIS 20/20 Advance Program is cloud-based, it includes a VDS, so clients and partners can reconfigure and remove existing customizations and non-cloud-friendly integrations before transitioning to iMIS EMS Enterprise.
Begin reviewing the New Features and Upgrade Changes to prepare for the upgrade.
Things to know before upgrading
If you are an AiSP and would like to request a demo instance, you can enter a ticket to Cloud Services; however, before requesting a demo instance, the following must first be completed or understood:
- You must be on iMIS 2017 with at least Service Pack P applied; however, it is highly recommended that you be on the
latest service pack.
- The iMIS 20/20 Advance Program includes direct access to the VDS, from which you will have access to the database. This access ensures clients and partners can reconfigure and remove existing customizations and non-cloud-friendly integrations before transitioning to iMIS EMS Enterprise.
- The iMIS Pay gateway is the only allowed gateway
- Self-hosted DataVaults must be migrated to iMIS Pay Central
- The REST API must be utilized (no integration through iBO or SOA)
- The iMIS 20/20 Advance Program is only available in an ASI-approved cloud-hosted environment and updates must regularly be applied to sites as they become available
- Applications other than iMIS (e.g., Office, Visual Studio) are no longer supported
- The following are no longer available:
- iMIS Desktop
- iMIS TaskCentre
- Crystal Reports (recreate existing using IQA, SSRS, or iMIS Report Writer)
Important! Although you can upgrade with preexisting customizations, you must continually work toward replacing or dropping all customizations and non-cloud-friendly integrations. No new customizations will be added to the database once it has been transferred to ASI's hosted environment. ASI Cloud Services will release updates on a regular basis that could potentially break preexisting customizations, and the client is responsible for resolving these issues.
Upgrade path through the iMIS 20/20 Advance Program
The following outlines how to upgrade to iMIS EMS through the iMIS 20/20 Advance Program.
The following outlines how to obtain an iMIS 20/20 Advance Program test site:
- Run the following scripts against your iMIS 2017 database:
ListNonImisDatabaseObjectNames.sql- Determines how many customizations are in the database (e.g., tables, views, stored procedures) and creates the script to remove the customizations. iMIS Customizer tables are not considered a customization. This script does not identify customizations outside of the database, such as a custom iPart. AddlComplexities.sql- Identifies potential areas of complexity that may need further investigation prior to upgrading. Review the ReadMe file before running the AddlComplexities script.
- ListCustomizationsThatReferenceObsoleteSchema.sql - Identifies customizations that reference schema that became obsolete between iMIS 2017 and iMIS EMS.
ListCustomizationsNoLongerSupported.sql- Identifies customizations that are no longer supported. This script is meant for those who are upgrading on-prem or through the iMIS 20/20 Advance Program.
- Client and AiSP or ASI Client Success discuss and analyze the results of the scripts. They determine which customizations they need, how they can replace them, and any other details surrounding the customizations. Any customizations not being used should simply be dropped.
- Run the RefreshViewMetadata script to identify any broken views or views that reference dropped tables/other views. This script should only be run if you have already dropped all customizations defined in the ListNonImisDatabaseObjectNames script.
- Complete the pre-upgrade tasks.
- Gather the following items:
- BAK file
- KEK file
- Website app themes
Important! You must have these items ready before reaching out to ASI, as they are required before the upgrade can proceed.
- Contact your CPIL and ask that they work with ASI Orders to enter a ticket to Cloud Services requesting to be added to ASI's hosted environment and start the iMIS 20/20 Advance Program upgrade:
- A Cloud Services analyst will respond to the ticket with a secure link where you can upload the database backup, KEK file, website app themes, and all images.
- Client should also provide a list of RDP users, email addresses, phone numbers, and phone model to setup two-factor authentication.
- Cloud Services does the following:
- Internally request a new VDS
- Move the backup and all associated files to a dedicated server
- Review live database to ensure it's on at least Service Pack P; however, it is highly recommended that you be on the latest service pack
- Upgrade the backup (this could take up to seven business days)
- Setup RDP accounts for login
- Client is to fill out the Global Payments Integrated form to start the application for the iMIS Pay gateway.
Important! All scripts can only be run against an iMIS 2017 database. The AiSP or Client Success is responsible for removing all customizations before uploading the 2017 database backup to Cloud Services.
Tip! Color code the output document to easily see which are actively being used (GREEN), which you are unsure about (YELLOW), and which are not being used anymore (RED).
Testing in the iMIS 20/20 Advance Program
During the testing phase, the client, AiSP, or ASI Client Success should complete the following:
- Test all third-party applications and integrations. The test site is available while testing and final stages of application integration are completed by the AiSP or ASI Client Success. This will not be the live site until all testing has been completed.
- The client/AiSP/ASI Client Success is to follow a test plan to review all areas of change.
Important! iMIS Report Writer is an extra license cost. Contact your CPIL if you require iMIS Report Writer.
Important! Any changes made in the test site do not automatically transfer over on a live upgrade. Keep detailed notes about the changes you make in the test environment, so that you can make the same changes after the live upgrade. Items such as content records, queries, and business objects can be manually exported from test and imported into the live system.
After all third-party applications and integrations are successfully tested, the following steps remain to go-live:
- AiSP or ASI Client Success notifies Cloud Services that all necessary testing has been completed.
- ASI Cloud Services does a final database refresh, so client is live on their new iMIS 20/20 Advance Program site.
- AiSP or ASI Client Success is responsible for reconnecting any third-party application to the live site.
- Complete the post-upgrade tasks.
- Set up the iMIS Pay gateway in the live site.
- The client works with the AiSP or ASI Client Success to reconfigure and eliminate customizations.
- Once customizations have been replaced through reconfiguration or out-of-the-box iMIS functionality, the client should prepare to move to iMIS EMS.
Note: If the client has an on site DataVault, ASI Cloud Services will coordinate the move with the client.