Product: Omatic Cloud

Description: This solution presents a pre-onboarding checklist for Omatic Cloud for Salesforce

Environment: Salesforce

Versions: All


Administrative Tasks

  1. Provide your organization’s initial two Omatic Cloud administrative users (first name, last name, email address). These users will be responsible for adding your organization’s additional users. There is not a limit to the number administrative users that can be added to Omatic Cloud.
  2. Decide whether you will be using a Salesforce Sandbox or Production for initial testing. If you are using a Sandbox we will transition it to Production through our training.   
  3. It is recommended, though not required, to create a new user account specifically for your Omatic Cloud integration in Salesforce called "Omatic Cloud Integration." This user will be used to connect Salesforce to Omatic Cloud on your connectivity call. This user must have system administrator rights. 
    • Please note that creating this user is helpful for reporting and staffing transitions.
  4. If you are using a flat file or CSV for import (IOM+), please submit the sample data file you would like to use for your onboarding to the secure SharePoint folder provided by your Project Coordinator.   
    • The data files should contain no more than 25 rows and 52 columns of raw or sample data for the purposes of training.        
    • Please do not combine or manually edit files prior to sending, as we want the data to be reflective of a typical import.   
    • This sample file will be reviewed alongside your consultant for approved use during your data review call. Please note one spreadsheet does not equal one formula. 
  5. If you plan to connect to an external system, please follow these instructions on obtaining your API and login credentials.
    • Please DO NOT share this information with our implementation team; please have it readily accessible for your first call.  
  6. Please complete and return the OC Pre-Training Survey (attached below) to your Project Coordinator.  
  7. Please complete and return the OC Mapping Decisions document (attached below) to your Project Coordinator. Completing the mapping document prior to your consulting helps you to expedite your formula configuration.   
    • For IOM+ (flat file), please use your sample data file to complete the OC Mapping Decisions document.  

    • For an external system (connector), consider what aspects of the system you are using and provide initial mapping decisions for each of those data flows 

      (i.e., types of transactions, events, TeamRaiser in Luminate Online, campaigns, mailings, email campaigns, etc.) 

      • Please note, for each type of data flow you plan to build, you will need to either have live or test data available. Live data is preferred for more accuracy in your integration formulas. 

  8.  Once you have access to Omatic Training Pass, please review the Omatic Cloud eLearning resource herePlease note you will need to be logged into the website to access
  9. If you are using a flat file or CSV for import and you plan on setting up automated/scheduled imports, please have your FTP credentials ready for your first consulting call. This article provides more details.  
    • Please DO NOT share this information with your Omatic team ahead of time; please have it readily accessible for your first call. 

Prepare Your Database (Required)

Note: these directions are written for those using Lightning view

  1. Create a custom external ID field to store Constituent IDs. You can find instructions on how to do so here.
    Explanation: This step is required if you want to use the ID from your source data for matching. 
  2. Review your duplicate settings.

Explanation: reviewing your Duplicate Settings will give you the opportunity to ensure that your criteria is either as strict, or as loose, as you'd like it. We recommend the settings in your Sandbox reflect what is in your Production so when you begin pushing data to Production you will see the same syncing behavior. 

Omatic Cloud allows you to set your own matching rules for identifying possible duplicates in Salesforce. Additionally, Salesforce will do its own duplicate search when attempting to add or update records. Review this information about how to bypass additional duplicate searching when sending updates from Omatic Cloud.

Nonprofit Success Pack (NPSP Only)

  1. If you have not yet done so, please complete the NPSP post-installation required configuration. You can find instructions here.
  2. Review your Address Management settings. 
    Explanation: reviewing your Address Management Settings will give you a clear picture of how addresses will be handled. It will also allow you to ensure that your addresses are up to date, and consistent across all Households or Organizations. For more information on Address Management, please check out
     this article.
    • Click on the App Launcher and type in NPSP Settings
    • Select People, then Addresses
    • If you want multiple addresses stored on a Household account record, please be sure that Household Account Addresses Disabled is unchecked
    • If you want address management enabled for Organization Accounts, please enable Organizational Account Addresses Enabled
    • If you want address changes treated as an update (no new Address object created), please enable Simple Address Change Treated as Update
  3. Review your Campaign Management settings.

Explanation: enable Automatic Campaign Member Management to automatically add donors on an opportunity as a Campaign Member to the primary campaign source.  

  • Click on the gear icon, then click Setup
  • Click on the App Launcher and type in NPSP Settings
  • Select Donations, then Campaign Members
  • We recommend enabling Automatic Campaign Member Management to create a Campaign Member record for tracking and reporting purposes