How the Import Process Works

A Step-by-Step Look at the Import Process

Follow these steps to get donor data into Salesforce.

1. Prepare Salesforce for Import: Get your Salesforce org set up and ready to receive your data set.

2. Prepare Your Data for Import: Clean your data and put it in the NPSP Data Importer Templates, which mirrors the fields in the NPSP Data Import custom object.

3. Import to NPSP Data Import Custom Object: You can use the application of your choice to import your CSV data into the NPSP Data Import object. The instructions we provide in these docs highlight using the Salesforce Data Import Wizard. But you can instead use an external data import application—such as Salesforce Data Loader, DemandTools, Apsona, Jitterbit, and Informatica—to upload your data to Salesforce. (This is the first part of the two-part import process.)

4. Set Up Matching and Do a Dry Run: If you already have records in your org and want to check to see if the records you're about to upload match any of those existing records, you can do a dry run. The Dry Run works like the import process, but doesn't actually import the records. This helps to prevent duplicates in your org and helps you avoid updating an existing record with incorrect data. If you'd like to save any of these NPSP Data Import configuration options, see Batch Import Overview.

5. Process Your Import: Start the NPSP Data Import tool, which takes the organized data from the custom object's records and imports them into the Nonprofit Success Pack as multiple objects, including Contacts, Accounts, and donations (Opportunities). (This is the second part of the two-part import process.)

6. Delete Imported Records: After you've successfully imported your records, you can optionally reduce data storage by deleting the intermediate data in the NPSP Data Import object.

After you complete this process, your data will reside in the following Salesforce objects created from the import process:

• Contacts (donors, volunteers, advocates, and other constituents in NPSP)
• Accounts (households or organizations in NPSP)
• Opportunities (donations, grants, and the like in NPSP)

• NPSP Payments

• Campaigns

• Additional objects you add to the NPSP Data Importer

Why is It so Complicated?

You may be thinking that this process seems awfully complicated. You may also be wondering why we need an intermediate step of uploading data to the NPSP Data Import custom object. What's its purpose?

Without this custom object, you'd need to transfer your existing data into multiple spreadsheets—each one representing a table of Contacts, Accounts, donations (Opportunities), and so on. Then you'd need to import each spreadsheet into Salesforce, individually and in the correct sequence. First create Accounts, then Contacts, and so on. After each import, you'd need to export the data from Salesforce, get unique IDs for records, and create relationships between these records and the records in your other spreadsheets. The NPSP Data Importer not only creates exactly the objects you need from the single NPSP Data Import custom object, but it also avoids creating duplicates of existing Contacts and Accounts.

We won't go into more detail here, but believe us when we say that the NPSP Data Import object can save you hours of work!