Upgrading

Do the following to complete phase 1:

1. Determine if you need to collaborate with ASI Client Success through one of the iMIS EMS Upgrade Packages. The packages are for clients, partners, and AiSPs.
2. If you are a partner (AiSP or CiP), review the Path to Digital Transformation.
3. Review How to upgrade to iMIS EMS to identify which upgrade path applies to you.
4. Review Considerations before beginning an upgrade.
5. Review and understand the Desktop migration to the Staff site article, which details the iMIS Desktop features that have and have not been migrated to the Staff site.
6. Review and understand the Upgrade Changes.
7. (optional) Download and import the Upgrade Dashboard files before getting started with the pre-upgrade checklist.
8. Create a backup (copy) of your iMIS 2017 database. Using the backup, complete the following:
   1. Complete the Pre-upgrade checklist.
   2. Run the Upgrade scripts.
   3. Run the Database Validation Scripts.
9. Order an iMIS EMS staging (test) site from ASI to begin testing. See How to upgrade to iMIS EMS.

Do the following to complete phase 2:

Test iMIS EMS

Using the iMIS EMS test site, the client must work through the testing documentation:

• Settings configuration
• Testing iMIS EMS
• Testing checklist
• Membership testing
• Fundraising testing
• Finance testing
• Queries and reports testing
• Commerce testing
• Websites and account pages testing
• Images and files testing
• Events testing
• Communications testing

Transfer your gateway to Global Payments or Stripe

During the testing phase of iMIS EMS, you will start the process of transitioning from your current gateway provider to one of the following gateways:

• Global Payments (North America & Asia Pacific only) - Review the getting started guide and fill out the Enrollment Form.
• Stripe (Any region) - Review the getting started guide.

Customization replacements

Complete the following related to the ListNonImisDatabaseObjectName upgrade script:

1. Client and AiSP or ASI Client Success discuss and analyze the results of the ListNonImisDatabaseObjectName script.
2. Replacements for customizations are created and implemented in the iMIS EMS test site.
3. Client tests all customization replacements and confirms they are ready for go-live.

Third-party integrations

Complete the following:

1. Third-party integrations are identified.
2. Communication between the third-party vendors and clients has started. Vendors are aware that an iMIS upgrade is occurring in the near future.
3. Identify all queries that are accessing the REST API. These queries must be explicitly granted API access post-upgrade, so it is important that they are identified during the pre-upgrade stage. See IQA Security Update and Updating queries that must access the REST API for more information.

Helpful resources:

• Upgrading with a TopClass integration
• Upgrading with a Higher Logic integration
• Accessing the API endpoint
• Updating queries that must access the REST API
• Integrating with iMIS
• Cloud-safe tailoring and customizations for iMIS
• Standards for third-party integrations

Other items to review

• If you currently offer members the option to renew their memberships for varying term lengths (e.g. 1-year, 2-year, and 3-year terms), you must use the out-of-the-box implementation. See Converting custom multi-year billing.
• If you currently use iMIS Desktop campaigns and appeals, you must review and complete the items outlined in the Migrating campaigns and appeals from Desktop to EMS article.

Do the following to complete phase 3:

1. Complete and sign the iMIS EMS Checklist.

2. Notify ASI Cloud Services to say you are ready for a live upgrade and attach the iMIS EMS Checklist.

3. Schedule a live upgrade date with ASI Cloud Services.

   📘

   Note

   Communicate the live upgrade date with all third-party application vendors.

   🚧

   Warning

   It is the client or AiSP's responsibility to coordinate with the third-party integrations to ensure no connections are broken post-upgrade.

4. Create a list of to-do items that must be manually recreated or changed after the live upgrade. Any changes made in the test site do not automatically transfer over on a live upgrade. Items such as content records, queries, and business objects can be manually exported from test and imported into the live system.

5. Assign someone the task of disabling Process Automation tasks associated with dropped stored procedures. See Disabling Process Automation tasks using custom stored procedures for details.

6. The evening before the live upgrade date, complete the Pre-upgrade checklist items that are remaining.

Do the following to complete phase 4:

1. Set up the Global Payments (AP & NA regions) or Stripe gateway.
2. Complete the post-upgrade tasks:
   • Post-upgrade checklist
   • On premise post-upgrade tasks (on-premise upgrades only)
3. Reconnect the third-party applications.
4. Complete the following related to ListNonImisDatabaseObjectNames - Result Set 5:
   • Review the list of customizations that are being referenced and confirm all replacement customizations are working correctly in the live site.
5. Complete the following related to ListNonImisDatabaseObjectNames - Result Set 6:
   • Confirm that all Business Objects identified as needing to be dropped prior to upgrade have been addressed post-upgrade.
6. If applicable, disable the Process Automation tasks using dropped stored procedures.
7. If applicable, update custom websites to use new Classic_Constellations template.
8. (optional) Update the contact account pages to use new iMIS EMS layout.
9. Work with AVAIL_CREDIT balances after upgrading.
10. Update the live site with any changes from the test site.