There are several changes to the campaign and appeal structure from iMIS Desktop to iMIS EMS, with the main changes being the following:
- Campaigns are now a required component. Campaigns were not previously required, which allowed appeals to be created free from a campaign. In iMIS EMS, an appeal (now referred to as source code) must be tied to a parent campaign. The benefit to this requirement is that all users have access to the Marketing > Campaigns navigation of the iMIS Staff site, which was previously a licensed feature.
- Source codes cannot be used in multiple campaigns. While you can create many different campaigns with various source codes, each campaign must have a unique set of source codes, meaning there is no way to share a source code among multiple campaigns. The benefit to this change is the response tracking feature in iMIS EMS, which allows users to easily track source codes that are embedded in communication templates.
example
The annual summer campaign uses the same EMAIL source code each year. There is a different campaign code for each year, but the source code is reused. This structure is no longer accepted. Before upgrading to iMIS EMS, new source codes must be created, so the associated data can be successfully migrated.
Below is an illustration of this example.
| Campaign code | Desktop source code | New EMS Source Codes |
|---|---|---|
| SUMMER20 | EMAIL_SUMMER20 | |
| SUMMER21 | EMAIL_SUMMER21 | |
| SUMMER22 | EMAIL_SUMMER22 |
Reviewing the iMIS Desktop campaign and source code data
Those hosted by ASI or moving to an ASI-hosted environment will work closely with the ASI Upgrade Program Team to migrate the campaign and source code data. Those upgrading in a self-hosted (on-prem) environment must download the linked attachment to begin the migration process.
Upgrading to iMIS EMS (hosted by ASI)
If you are working with the Upgrade Program Team to upgrade to iMIS EMS (ASI-hosted), then they will work with you to gather all data, review which campaigns and source codes to migrate, and confirm the new names of the campaigns and/or source codes.
The migration will happen once in the test site and then again after you upgrade live. In the test site, you will confirm the new configuration before upgrading live. The ASI Upgrade Program Team performs both migrations for you, to ensure all data is correctly migrated to iMIS EMS.
Upgrading to iMIS EMS (on-prem/not hosted by ASI)
If you are hosting iMIS EMS on-prem, you must use the linked files to begin the review and migration process: Migrating source codes to iMIS EMS
Begin with the readme.v1.3.txt file to understand the various steps involved, then use the Instructions tab in the SourceCodesReview.v1.3 file to continue the process. Contact the ASI Upgrade Program Team if you have questions.
Ensuring historical data is maintained
Source codes may need to be renamed if they are used with multiple campaigns, which may be concerning. The ASI Upgrade Team works closely with you throughout this process to ensure all historical data is maintained for reporting purposes. If the name of a source code or campaign needs to change, the related data will not be lost.
Understanding where source codes are used in iMIS EMS
Source codes are used in the following areas:
- Entering a new gift as a staff user: Distributions are now referred to as Gift items. Gift items cannot have campaigns or source codes associated with them; however, when entering a gift, staff users can choose a source code to associate with the donation (Fundraising > Enter gifts), and the campaign that is assigned acts as the source code's parent campaign. A campaign cannot be set directly for the gift.
- Reporting: There are several out-of-the-box reports that detail source code data.
- Hyperlinks embedded in communication templates:
Creating new source codes in iMIS EMS
To learn how to create new source codes in iMIS EMS, see