The following have been identified as the top items that must be considered before starting the iMIS EMS upgrade process with any client.
Use the Customization and Additional Complexities scripts on a client's 20.2.66 database to understand which of the below items will apply to the client. The Additional Complexities script comes with a ReadMe file that should be read before attempting to review the script results.
Tip! To review the below content in a checklist form, download the following Word document: iMIS EMS Upgrade Analysis Checklist
Current iMIS version
The current version the client is on will affect the client in two ways.
Training
The older the iMIS version, the more training the client is going to need. Consider an ILS for all clients but especially those who are not currently on iMIS 2017 (20.2.66). Those on iMIS 2017 will still benefit from an ILS, but they are also more familiar with the iMIS Staff site.
Clients who are heavy iMIS Desktop users will benefit the most from an ILS, because iMIS EMS no longer has the Desktop.
Physical upgrades
The iMIS database must be on version iMIS 2017 (20.2.66) for the upgrade to iMIS EMS (20.3). Earlier versions of iMIS do not have a direct upgrade; for example, if the client is on 20.1, they must first have their database upgraded to 20.2.66, then hosting can upgrade the database to 20.3.
Client Success or an AiSP must perform the upgrades to 20.2.66. Once the database is on 20.2.66, the database can be handed off to ASI Hosting, so the upgrade to 20.3 can be completed. If the client wants a test site, they will need to pay for the upgrade to 20.2.66 twice: Testing and Live.
Customization replacements
After the client identifies which customizations they need to keep, they must rely on their AiSP or Client Success to replace the customizations with cloud-friendly alternatives. The complexity and amount of customizations will determine the time and cost. Client Success or the AiSP would need to first analyze the customization replacement complexity before an accurate time and cost estimate can be provided.
Tip! To get started with identifying the customizations, run the Customization script on the client's 20.2.66 database. If the client is on an earlier version of iMIS, they must upgrade a backup of their database to 20.2.66 before identifying all customizations.
Third-party integrations
All third-party integrations must be cloud friendly. The client is responsible for the coordination with their third-party providers, but they should be aware that there is a cost associated with the reconfiguration of their connections to be cloud friendly. See Cloud-safe tailoring and customizations for iMIS and Integrating with iMIS. If you are using TopClass, see Upgrading with a TopClass integration.
Submitting payments through the API
In iMIS 2017, you could utilize the API to submit credit card payments. In iMIS EMS, it is not currently possible to submit credit card payments through the REST API. All credit card payments must currently be submitted through the iMIS Cart.
Goals for post-upgrade
Many clients take this upgrade as an opportunity to complete goals they have not been able to get to in the past, such as a website redesign or using iMIS features they have access to but do not currently use. The testing phase is not the time to start or complete these goals. Instead, the client should be informed that there is a PIAS program that helps them accomplish these goals post-upgrade.
Billing case statements
Billing special pricing rules upgrade and are functional post-upgrade; however, the rules are not editable. In order to edit a rule, it must be recreated using the new special pricing window.
If the Additional Complexities script identifies billing case statements, the solution may vary on how to replace the case statement. In the simplest cases, the out-of-the-box special pricing window can be used by the client with no Client Success or AiSP assistance required. In more complex cases, an Expression Builder business object will need to be built for the client to replace a case statement, which more then likely requires AiSP or Client Success hours.
Custom multi-year billing
Some clients may offer multi-year billing through a custom implementation. These implementations are typically offered through custom stored procedures and views, which are no longer supported. Review the following article for full details and potential steps that may need to be taken: Converting custom multi-year billing
General ledger package (GL export)
iMIS EMS only has a native export for QuickBooks. If the client is exporting GL rows to an accounting package that is not QuickBooks, the client may need to consider using an Excel macro or CSI’s GL Processor integration.
Custom Crystal Reports
iMIS EMS does not support Crystal Reports. In many cases, the out-of-the-box SSRS or Report Writer reports are good replacements for the client; however, some clients have very custom Crystal Reports that they rely on.
In instances where the client needs a custom Crystal report recreated, Client Success would need to analyze how much time it would take to recreate the report with SSRS or Report Writer.
Note: There are no plans to deprecate SSRS; however, it is best practice to use Report Writer going forward.
Fundraising source codes
iMIS EMS does not support any use of source codes outside of the Campaign Management source codes, so these may need to be migrated into the new infrastructure as part of the upgrade process (ASI has tools to assist with this migration if needed). See Migrating campaigns and appeals from Desktop to EMS.
Custom Staff site content
Many clients have custom account pages. This means after the upgrade, their custom account pages do not have any of the new features or content on them. We recommend comparing the custom account page with the out-of-the-box account page and migrating content over to the custom pages. See Updating the contact account page after an upgrade from iMIS 2017.