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:
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.
The Stripe gateway is available in all regions upon request. Please contact your AiSP or CPIL to learn how to get started with the Stripe gateway.
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:
- 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.