Phase 2: Staging the upgrade and performing tests

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

Queries and reports testing

Commerce testing

Websites and account pages testing

Events testing

Communications testing

Global Payments gateway

During the testing phase of iMIS EMS, you will start the process of transitioning from your current gateway provider to either the Global Payments (NA & AP) or Stripe (UK & EU) gateways. To begin the process, fill out the Enrollment Form.

Customization replacements

Complete the following related to the ListNonImisDatabaseObjectName upgrade script:

Client and AiSP or ASI Client Success discuss and analyze the results of the ListNonImisDatabaseObjectName script.

Replacements for customizations are created and implemented in the iMIS EMS test site.

Client tests all customization replacements and confirms they are ready for go-live.

Third-party integrations

Complete the following:

Third-party integrations are identified.

Communication between the third-party vendors and clients has started. Vendors are aware that an iMIS upgrade is occurring in the near future.

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:

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.