Pre-upgrade checklist

Perform the following before the test upgrade and the live upgrade.

Note: There are certain pre-upgrade steps that may need to be performed before the test upgrade and again before the live upgrade.

Tip! To assist with completing the pre-upgrade checklist, use the Upgrade Dashboard.

Pre-upgrade steps to perform before the test upgrade

Review the following pre-upgrade steps that must be performed before the iMIS EMS test/staging upgrade in the iMIS 2017 site.

File Storage

  • Files (e.g., images, PDFs) stored in non-standard locations must be identified and sent to Cloud Services. If content on the site references these files using hard-coded paths rather than relative paths, this will require content to be updated post-upgrade. To minimize post-upgrade content updates, ensure that all file references use relative paths or path variables. See Images and files testing for full details.

Database

  • For those upgrading from on-premise or 20/20 Advance Program to cloud, you must ensure the database is has the correct collation. The following collation is required: SQL_Latin1_General_CP1_CI_AS. To review or change the collation, see the Microsoft Documentation.

Contacts

  • Ensure there are no addresses without a Country defined.

Membership

  • Ensure the M and NM customer types are defined.
  • Ensure no billing cycle names match billing product codes.
  • Ensure no billing product codes contain spaces.
  • Open cash non-dues and list billing invoices must be rebilled after the upgrade. Prior to upgrading, confirm whether there are open cash non-dues and/or list billing invoices. If there are, you must perform the associated post-upgrade step.
  • Create an IQA query to identify contact records with AVAIL_CREDIT balances. After upgrading, the identified AVAIL_CREDIT balances will automatically offset the balance of dues products when cash dues renewals are generated. However, generating these renewals will create an open batch that must be posted to complete the credit application. For more information, see the post-upgrade step.

Websites

  • Ensure you are not using a deprecated website template or theme on any website. See Updating deprecated templates and themes in websites.
  • Ensure the Constellations template changes do not affect your custom websites.
  • Multiple publishing servers are no longer supported and must be removed before upgrading. The only publishing server that should be defined prior to upgrading is Publish Server Code A with Is Default set to Yes.

Panels & Tables

Note: While testing panels and tables, it may be useful to review what panel sources are used in each panel definition. Use the ListPanelDefinitionSources.sql script to generate one row for every source included in a panel.

  • After an upgrade to iMIS EMS, there may be panels and/or panel sources that are missing. This may be because the panel source was not correctly added to the ObjectMetaData table when it was initially created. For full details, see Ensuring panels and panel sources are not missing after an upgrade.
  • Confirm every table and/or business object you need accessible as a panel source is properly defined as such. This step is to ensure any table you may need to use as a panel source is converted properly and added to the ObjectMetaData table (as compared to the next pre-upgrade check that is specifically referencing customizer tables). If this action is not performed before upgrading, the tables only appear as business objects and you cannot use them in Panel Designer.
  • Import customizer tables that were never configured as panels.
  • Update Panel Collection Editor content items that are configured to Use all available panels.

Business Objects & Queries

  • Identify 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.
  • Publish all working business objects.
  • Update business objects that are built from unsupported internal tables or views.

RiSE & Settings

  • Ensure no content folders under the root folder (@) are named iMIS.
  • Publish all working content.
  • Rename Tagged List Formats that contain characters other than letters, numbers, and underscores.
  • Remove the Expansion value from general look up tables, with the exception of the DESIGNATION, PREFIX, SUFFIX, and FUNC_TITLE tables.
  • Update custom system icons. iMIS system icons have been updated from PNG to SVG (.svg) for the enhanced scalability, smaller file size, and customization options that the SVG file format offers. Custom themes may require adjustments because of this enhancement. See Updating custom system icons for full details.

Finance

  • Ensure payment methods are defined with a specific Type. If no Type is selected, such as Cash or Credit Card, the payment method will become an Open Credit payment method after the upgrade.
  • Post open batches.
  • Process all premium transactions.

Commerce

  • To ensure all necessary products are available for public users to purchase, you must confirm the product's Web Option is correctly configured prior to upgrading.
  • Product special pricing rules cannot be edited after the upgrade, so you must delete the rules prior to upgrading.
  • iMIS EMS does not support multiple warehouses, so you must designate all inventory to the default warehouse before upgrading. If you do not have multiple warehouses enabled, this does not apply to you.

Events

  • Update events that are using stored procedures for price evaluation.
  • Update the Show on Web option for events.
  • Contacts that have been deleted from iMIS that were once defined as the Event Contact will still have their iMIS IDs recorded in the event definition, which causes errors when editing the event post-upgrade.To prevent these errors, it is important that these IDs are removed from the event definition.
  • Contacts that have been deleted from iMIS that were once defined as an event function resource (speaker or staff) will still have their iMIS IDs recorded in the event definition, which causes errors when editing the event post-upgrade. To prevent these errors, it is important that these IDs are removed from the event definition.
  • Images added to an event through the iMIS Desktop are not added to the Image Manager during the upgrade, which causes errors when editing the event post-upgrade. To prevent these errors, it is important that these images are removed from the event.

Pre-upgrade steps to perform before the live upgrade

The following pre-upgrade steps must be performed before the live upgrade to iMIS EMS: