---
schema_version: "1"
id: 0a44cea2c77753d898a3874e0613b62b02472ea0e02d7c71865b9ee6eb572165
title: Verify Data Upload
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sfdo/264-0-0/npsp_verify_upload.md
canonical_url: https://help.salesforce.com/s/articleView?id=sfdo.npsp_verify_upload.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: e92e67a4276893e38b63e1f4ecd68f61bbc68d654f67730a40e06075238af48a
description: Make sure the data from your template uploaded successfully to the NPSP Data Import custom object.
products:
  - Nonprofit
release: "264"
---
# Verify Data Upload

Make sure the data from your template uploaded successfully to the NPSP Data Import custom object.

1. In Salesforce, click the NPSP Data Imports tab. If you don't see NPSP Data Imports, you can find it in the App Launcher.
2. Choose the To Be Imported list view to see records uploaded to the object. Keep in mind that while your data has been uploaded into Salesforce, it hasn't been added to (that is, "imported" into) any NPSP objects yet.
    
    ![NPSP Data Imports tab](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-nonprofit_success_pack-264-0-0-production-enus/bd2879e2-2bdc-4012-aa32-dc0c697c4538/nonprofit_success_pack/images/lightning_data_to_be_imported.png)
3. Spot-check some records to make sure all were uploaded correctly. Make sure the information in the CSV went to the correct fields on the NPSP Data Import object. If you mapped a Salesforce ID with the data wizard and it's not appropriate for the type of record, the Imported field for that Object Group will be blank.
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-nonprofit_success_pack-264-0-0-production-enus/bd2879e2-2bdc-4012-aa32-dc0c697c4538/images/icon_note.png)
    
    Note If your CSV data didn't populate all of the fields you expected in the NPSP Data Import records, you may have run into a Data Import Wizard limitation. Please see this [Data Import Wizard Known Issue](https://success.salesforce.com/issues_view?id=a1p3a0000017xyiqay) for more information. Delete any columns you aren't using in your import to get around this limitation. If you'd like to import more than 65 columns, use an API-based import tool such as Salesforce Data Loader.

If for some reason your data did not upload correctly, or there were errors during the import process, you might want to delete all of the import records and start over again. (See [Delete Imported Records](https://help.salesforce.com/s/articleView?id=sfdo.npsp_delete_imported_records.htm&release=264.0.0&type=5 "After you've successfully imported your records, you can optionally reduce data storage by deleting the intermediate data in the NPSP Data Import object. Deleting the intermediate data in the NPSP Data Import object does not delete your new Account, Contact, or Opportunity donation records.").) Before re-doing your import, go back and review your CSV import file carefully. Simple things like leaving a "$" in the donation field, leaving a leading space like " Smith," or leaving out an "@" in an email address will cause import errors. _Make sure that every single row in your spreadsheet is cleaned and ready for import_.

Look good to go? Do a Dry Run to make sure your data will import successfully. See [Verify Your Upload with Dry Run](https://help.salesforce.com/s/articleView?id=sfdo.npsp_verify_with_dry_run.htm&release=264.0.0&type=5 "Once you import records into NPSP, you can't hit the undo button. And that can be problematic if you accidentally import records that you had previously imported, resulting in duplicate records in your org. It can also be problematic if the wrong record is matched and you've updated it with data from a different record. Doing a dry run allows you to see if there are any potential matches before you import.") for more information.