Feathr's integration with iMIS is forward looking only. This means that only mapped data that is created or changed after the integration is connected will be automatically synced from iMIS to Feathr.
To get the most value out of syncing data between both platforms, Feathr strongly recommends a one-time manual import of iMIS data into Feathr. Learn more about manual imports here.
This article provides recommendations on best practices for bringing your data over from iMIS.
What to do before you export your list from iMIS:
Focus on data hygiene in iMIS, to ensure that you're bringing clean and organized contact data into Feathr. This can look like:
- Consolidating duplicates in iMIS.
- Making sure your contacts have the appropriate primary email selected.
- Determining how you will handle unsubscribed constituents in Feathr.
- Deciding which iMIS fields you need in Feathr.
Most important considerations:
-
Contact Key
- Ensure that you're pulling the Contact Key for your contacts, to map to the External ID field in Feathr. This is a required field, and we recommend double checking that you are indeed using the correct ID.
- The External ID field in Feathr is how our system identifies unique records. In order to avoid creating duplicates, please do not import anything but the Contact Key to this field.
- Do not map the iMIS ID to the External ID field in Feathr. This will create duplicates. Please create a custom field in Feathr for your iMIS ID to be mapped to.