Loading
Nonprofit Success Pack (NPSP) Managed Package
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Standard NPSP Data Import Fields

          Standard NPSP Data Import Fields

          This article includes reference information about the fields in the NPSP Data Import object, the mapping to target NPSP objects, and information about columns in the NPSP Data Importer Templates.

          This article includes reference information about the fields in the NPSP Data Import object, the mapping to target NPSP objects, and information about columns in the NPSP Data Importer Templates, especially requirements for date fields.

          The NPSP Data Import object contains Contact, Account, Address, Opportunity, Payment, and other fields for import, Gift Entry, or Salesforce.org Elevate. An NPSP Data Import object can contain up to two Contacts and two Accounts for each record. For data import, the majority of the fields are optional, and the NPSP Data Importer will use smart default values for fields that contain no data.

          In addition to the field mapping described in this article, Elevate includes Advanced Mapping specific to payment processing. Learn more in Advanced Mappings for Elevate.

          Important
          Important Make sure your dates are in the format supported by your data import tool.
          • If you're using the Salesforce Data Import Wizard for your import, use dates in your locale format. In the US, this means MM/DD/YY. For example: 12/31/14.
          • If you're using the external Salesforce (Apex) Data Loader tool for your import, use the YYYY-MM-DD date format. This format is not the native Excel date format, and you'll need to reformat all of the columns that contain dates. See this Help and Training article for more information.
          • Contact Fields
            The Contact fields define information about the primary Contact. Salesforce automatically creates a Household Account for each new Contact1 that you enter.
          • Household Fields
            The Household fields define information about Contact1 and Contact2's Household Account record.
          • Account Fields
            The Account1 and Account2 fields are used to match or create Organizational Accounts, and to create an affiliation between the appropriate Contact and Organizational Account.
          • Home Address Fields
            If any of the Home Address fields are specified, Salesforce creates an Address object for the Household, and copies the address to each Contact's Mailing Address fields, and the Household Account's Billing Address fields.
          • Donation Information Fields
            If any of the Donation Information fields are specified, Salesforce creates an Opportunity and associates it with either Contact1 (and the Contact's Household), or Account1.
          • Opportunity Contact Role Fields
            The Opportunity Contact Role fields define soft credit Opportunity Contact Role information for Account1 Organization donations.
          • Recurring Donation Information Fields
            When Recurring Donation Information fields are specified, Salesforce creates a Recurring Donation associated with either Contact1 (and the Contact's Household), or Account1.
          • Campaign Fields
            The Campaign fields define a Campaign associated with a Recurring Donation, Opportunity, and/or Contact. Set a Campaign Member Status to create Campaign Member records for Contact1 and Contact2.
          • GAU Allocation Fields
            The GAU Allocation fields define GAU Allocation information for the donation. Define up to two GAU Allocations for each donation in your import file.
          • System Fields
            The System fields capture information about the import including import statuses and information about the NPSP Data Import record.

          Contact Fields

          The Contact fields define information about the primary Contact. Salesforce automatically creates a Household Account for each new Contact1 that you enter.

          These are the Contact1 fields in the NPSP Data Import object.

          Field LabelDescriptionRequired or Default Behavior
          Contact1 Salutation The salutation for the Contact, such as Mr., Mrs., Dr., and so on. Optional.
          Contact1 First Name The Contact's first name. Optional.
          Contact1 Last Name The Contact's last name. Required, if you are including any other fields from Contact1.
          Contact1 Birthdate The Contact's birthdate. Optional. Use the correct date format supported by your import tool.
          Contact1 Title The Contact's title. Optional.
          Contact1 Personal Email The Contact's personal or home email. Optional, but matching to existing Contacts by Email requires at least one of the Email fields to be provided in order to find a match.
          Contact1 Work Email The Contact's work email. Optional, but matching to existing Contacts by Email requires at least one of the Email fields to be provided in order to find a match.
          Contact1 Alternate Email An additional email for the Contact. Optional, but matching to existing Contacts by Email requires at least one of the Email fields to be provided in order to find a match.
          Contact1 Preferred Email Specifies which of the three Email fields is the preferred one to use for communication with the Contact. If specified, it must match one of the picklist values: Personal, Work, or Alternate. Optional.
          Contact1 Home Phone The Contact's home phone. Optional.
          Contact1 Work Phone The Contact's work phone. Optional.
          Contact1 Mobile Phone The Contact's mobile phone. Optional.
          Contact1 Other Phone The Contact's other phone. Optional.
          Contact1 Preferred Phone Specifies which of the four Phone fields is the preferred one to use for calling the Contact. If specified, it must match one of the picklist values: Home, Work, Mobile, or Other. Optional.
          Contact1 Imported The Contact's Salesforce ID to match against. Optional. If not populated with an ID prior to import, NPSP will automatically populate after dry run or processing.

          The same fields exist for Contact2, and you use them the same way to add or update a secondary member of the household.

          Household Fields

          The Household fields define information about Contact1 and Contact2's Household Account record.

          These are the fields in the NPSP Data Import object that map to a Household Account record. We provided the Household Phone field as an example to follow if you want to set up additional custom fields for the Household. To create additional fields, follow the directions in Customize Advanced Mapping.

          Field LabelDescriptionRequired or Default Behavior
          Household Phone The Household's phone number Optional.
          Household Account Imported The Household account's Salesforce ID to match against. Optional. If not populated with an ID prior to import, NPSP will automatically populate after dry run or processing.

          Account Fields

          The Account1 and Account2 fields are used to match or create Organizational Accounts, and to create an affiliation between the appropriate Contact and Organizational Account.

          The Account1 and Account2 fields are used to match or create Organizational Accounts, and to create an affiliation between the appropriate Contact and Organizational Account. The organization for Account1 will be entered into the Primary Affiliation field for Contact1, and NPSP will create an Affiliation record representing this connection. Likewise, Account2 will be entered as the Primary Affiliation for Contact2. The Account1 and Account2 address fields are used to update the Organizational Account, not the Contact (Household) Address.

          Important
          Important The Account fields in the template are used to create optional Organizational Accounts with which the related Contacts are affiliated. Don't enter Household information in the template's Account fields, because the Account fields are for Organizational Account information only.

          These are the Account1 fields in the NPSP Data Import object.

          Field LabelDescriptionRequired or Default Behavior
          Account1 Name The Account's name. Required, if you are including any other fields from Account1.
          Account1 Street The Account's billing street. Optional.
          Account1 City The Account's billing city. Optional.
          Account1 State/Province The Account's billing state or province. Optional.
          Account1 Zip/Postal Code The Account's billing Zip/postal code. Optional.
          Account1 Country The Account's billing country. Optional.
          Account1 Phone The Account's phone. Optional.
          Account1 Website The Account's website. Optional.
          Account1 Imported The Account's Salesforce ID to match against. Optional. If not populated with an ID prior to import, NPSP will automatically populate after dry run or processing.

          The same fields exist for Account2, and you use them the same way.

          Home Address Fields

          If any of the Home Address fields are specified, Salesforce creates an Address object for the Household, and copies the address to each Contact's Mailing Address fields, and the Household Account's Billing Address fields.

          These are the Home Address fields in the NPSP Data Import object.

          Field LabelDescriptionRequired or Default Behavior
          Home Street The household's street Optional.
          Home City The household's city Optional.
          Home State/Province The household's state or province Optional.
          Home Zip/Postal Code The household's Zip/postal code Optional.
          Home Country The household's country Optional.
          Home Address Imported The Address's Salesforce ID to match against. Optional. If not populated with an ID prior to import, NPSP will automatically populate after dry run or processing.

          Donation Information Fields

          If any of the Donation Information fields are specified, Salesforce creates an Opportunity and associates it with either Contact1 (and the Contact's Household), or Account1.

          These are the Donation Information fields in the NPSP Data Import object.

          Field LabelDescriptionRequired or Default Behavior
          Donation Donor "Contact1" if an individual donation, or "Account1" if an organizational donation. Optional. Will be treated as "Contact1" if left empty.
          Donation Amount The donation amount. Required, if you are including any other fields for Donation Information.
          Donation Date The date you received the donation. Optional. Will use the current date if left empty. Use the date format supported by your import tool.
          Donation Honoree Information Contact information, such as email, address, or phone the donor provided for the tribute honoree. Optional.
          Donation Honoree Name The honoree name as provided by the donor. Optional.
          Donation Name A unique name to identify the donation. Optional. Will be automatically generated by the NPSP if left empty.
          Donation Notification Message A personalized message for the notification recipient. Optional.
          Donation Notification Preference Indicates how the notification recipient should be notified. For example, by email or phone. Optional. Must match values in corresponding picklist.
          Donation Notification Recipient Email The email address for the person receiving the notification. Optional.
          Donation Notification Recipient Info Contact information, such as address or phone the donor provided for the notification recipient. Optional.
          Donation Notification Recipient Name The name of the person to notify of this tribute gift. Optional.
          Donation Record Type Name The name of an Opportunity Record Type to use for the donation. Optional. Will use the Salesforce User's default Opportunity Record Type if left empty.
          Donation Tribute Type Indicates whether the donation is in honor or in memory of an individual. Optional. Must match values in corresponding picklist.
          Donation Type The type of donation. Optional. Must match values in corresponding picklist.
          Donation Stage The stage of the donation opportunity. Optional. Must match values in corresponding picklist. Will use an active Closed Won Stage if left empty, meaning that the donation has been completed.
          Donation Description A description of the donation. Optional.
          Donation Member Level The member level corresponding to the donation. Optional. Must match values in corresponding picklist.
          Donation Membership Origin The origin of the donor's membership. Optional. Must match values in corresponding picklist.
          Donation Membership Start Date The start date of the membership if the donation is for membership. Optional. Use the correct date format supported by your import tool.
          Donation Membership End Date The end date of the membership if the donation is for membership. Optional. Use the correct date format supported by your import tool.
          Payment Method The method of payment used for the donation. Optional. If Payments are enabled, will copy this value to the Opportunity's Payment object. Must match values in corresponding picklist.
          Payment Check/Reference Number The check or payment number for the donation. Optional. If Payments are enabled, will copy this value to the Opportunity's Payment object.
          Payment Paid Indicates the Payment was paid. Optional. Use the correct syntax for your import tool.
          Donation Imported The Donation (Opportunity's) Salesforce ID to match against. Optional. If not populated with an ID prior to import, NPSP will automatically populate after dry run or processing.
          Donation Possible Matches A comma separated list of Salesforce IDs of Opportunities that matched the Data Import record's Donation Matching fields. Automatically populated by NPSP.
          Payment Imported The Payment's Salesforce ID to match against. Optional. If not populated with an ID prior to import, NPSP will automatically populate after dry run or processing.
          Payment Possible Matches A comma separated list of Salesforce IDs of Payments that matched the Data Import record's Donation Matching fields. Optional.
          Donation Elevate Recurring ID The external, unique ID of the Recurring Donation in Elevate that this donation Opportunity is linked to. Populated by Salesforce.org Elevate integration.
          Payment Authorization Token Authorization token for a transaction. Populated by Salesforce.org Elevate integration.
          Payment Authorized Date The date and time the transaction was authorized. Populated by Salesforce.org Elevate integration.
          Payment Authorized UTC Timestamp The exact date and time (down to the millisecond) from the payment gateway that this transaction was successfully authorized. Populated by Salesforce.org Elevate integration.
          Payment Card Expiration Month The expiration month of the card used for this transaction. Populated by Salesforce.org Elevate integration.
          Payment Card Expiration Year The expiration year of the card used for this transaction. Populated by Salesforce.org Elevate integration.
          Payment Card Last 4 The last four digits of the card used for this transaction. Populated by Salesforce.org Elevate integration.
          Payment Card Network The card network of the card used for this transaction. Populated by Salesforce.org Elevate integration.
          Payment Declined Reason Provides detail about why a transaction was declined. Populated by Salesforce.org Elevate integration.
          Payment Donor Cover Amount The amount the donor paid in addition to their donation amount, often to help cover transaction fees or to add a tip to their donation. Populated by Salesforce.org Elevate integration.
          Payment Elevate Created Date The date and time the transaction was created. Populated by Salesforce.org Elevate integration.
          Payment Elevate Created UTC Timestamp The exact date and time (down to the millisecond) from Elevate that the transaction was created. Populated by Salesforce.org Elevate integration.
          Payment Elevate ID The unique ID for this transaction from Elevate. Populated by Salesforce.org Elevate integration.
          Payment Elevate Original Payment ID For refunds only. Shows the ID of the original payment transaction from Elevate. Populated by Salesforce.org Elevate integration.
          Payment Gateway ID The ID of the payment gateway that processed this transaction. Populated by Salesforce.org Elevate integration.
          Payment Gateway Payment ID The unique ID for this transaction from the payment gateway. Populated by Salesforce.org Elevate integration.
          Payment Origin ID The ID for the system where the transaction was initiated. Populated by Salesforce.org Elevate integration.
          Payment Origin Name The name of the system where the transaction was initiated. Populated by Salesforce.org Elevate integration.
          Payment Origin Type The type of system used to initiate the transaction. Available values include Engagement Hub, Giving Page, Payments API, Salesforce. Populated by Salesforce.org Elevate integration.
          Payment Status The status of the transaction from Elevate. Populated by Salesforce.org Elevate integration.
          Payment Type Indicates the type of transaction. Populated by Salesforce.org Elevate integration.
          Payment Elevate Transaction Fee The amount the donor paid in addition to their donation amount, often to help cover transaction fees or to add a tip to their donation. Populated by Salesforce.org Elevate integration.
          Payment Gateway Transaction Fee The transaction fee charged by Elevate. Populated by Salesforce.org Elevate integration.
          Payment Total Transaction Fees The transaction fee charged by your payment gateway. Populated by Salesforce.org Elevate integration.
          UTM Source Google Analytics parameter for tracking the referring source. For example, website or newsletter. Populated by Salesforce.org Elevate integration.
          UTM Medium Google Analytics parameter for tracking how the URL was shared. For example, email or banner_ad. Populated by Salesforce.org Elevate integration.
          UTM Campaign Google Analytics parameter for tracking the name or solicitation code of the outreach effort. For example, spring_2021_fundraiser. Populated by Salesforce.org Elevate integration.
          UTM Content Google Analytics parameter for differentiating similar content or links within a solicitation. Populated by Salesforce.org Elevate integration.
          UTM Keyword Terms Google Analytics parameter for tracking paid search terms. Populated by Salesforce.org Elevate integration.

          Opportunity Contact Role Fields

          The Opportunity Contact Role fields define soft credit Opportunity Contact Role information for Account1 Organization donations.

          The Opportunity Contact Role fields define soft credit Opportunity Contact Role information for Account1 Organization donations. You're able to define an Opportunity Contact Role for Contact1 and a separate role for Contact2 for each Account1 Organization donation in your import file. Opportunity Contact Role 1 fields are for Contact1 and Opportunity Contact Role 2 fields are for Contact2.

          Note
          Note You must use Advanced Mapping instead of Help Text mapping to use these fields. See Advanced Mapping Overview for more information.

          These are the Opportunity Contact Role 1 fields in the NPSP Data Import object.

          Important
          Important Opportunity Contact Role fields should only be used for Organization donations connected to Account1. For individual donations from Contact1, rely on the NPSP automation for assigning the primary donor and Household Member soft credit Opportunity Contact Roles. For more information, see Automated Soft Credits.
          Field LabelDescriptionRequired or Default Behavior
          Opportunity Contact Role 1: Role The role you'd like to assign to Contact1 for this donation. Must match one of your existing Opportunity Contact Roles.
          Opportunity Contact Role 1: Imported The Salesforce ID for the Opportunity Contact Role. Optional. If not populated with an ID prior to import, NPSP will automatically populate after processing.

          The same fields exist for Opportunity Contact Role 2, and you use them the same way to add or update a role for Contact 2.

          Recurring Donation Information Fields

          When Recurring Donation Information fields are specified, Salesforce creates a Recurring Donation associated with either Contact1 (and the Contact's Household), or Account1.

          When Recurring Donation Information fields are specified, Salesforce creates a Recurring Donation associated with either Contact1 (and the Contact's Household), or Account1.

          If you specify both Donation Information and Recurring Donation Information fields, Salesforce relates the Opportunity to the Recurring Donation as its first installment.

          These are the Donation Information fields in the NPSP Data Import object.

          Field Label Description Required or Default Behavior
          Recurring Donation Amount The amount for each installment Opportunity. Required.
          Recurring Donation Date Established The initial inception date for this Recurring Donation. The default is the current date. Optional. NPSP uses the current date if this is left blank.
          Recurring Donation Day of Month Sets the specific day of the month for future installment Opportunities when the Installment Period is Monthly. If you select 29 or 30, the installment date will be the last day of the month for months that don't have that many days. Required when the Installment Period is Monthly.
          Recurring Donation Effective Date The date that new or updated schedule information (Amount, Day of Month, etc.) for this Recurring Donation takes effect. The default is the current date. Optional. NPSP uses the current date if this is left blank.
          Recurring Donation Elevate Recurring ID The external, unique ID of the related Recurring Donation in Elevate. Populated by Salesforce.org Elevate integration.
          Recurring Donation End Date The date on which this Recurring Donation was closed. Optional.
          Recurring Donation Import Status The status given when NPSP Data Importer tries to create the Recurring Donation.

          Automatically populated by NPSP Gift Entry.

          If using Data Importer, and providing a Donation Import value, manually set the Recurring Donation Import Status to Matched or User-Selected Match.

          Recurring Donation Imported The Salesforce ID for the Recurring Donation. Optional. If not populated with an ID prior to import, NPSP automatically populates after dry run or processing.
          Recurring Donation Installment Frequency The Installment Frequency along with Installment Period defines the installment schedule of this Recurring Donation. For example, if Installment Period is Monthly and Installment Frequency is 3, the schedule is defined as "every 3 months". Optional. If left blank, NPSP sets the value to 1 on the target Recurring Donation record.
          Recurring Donation Installment Period The Installment Period along with Installment Frequency defines the installment schedule of this Recurring Donation. For example, if Installment Period is Monthly and Installment Frequency is 3, the schedule is defined as "every 3 months". Required.
          Recurring Donation Name Leave blank if you have a Recurring Donation Name Format selected in NPSP Settings. Otherwise, enter your own name. Required, unless you have a Recurring Donation Name Format selected in NPSP Settings.
          Recurring Donation Payment Method The form of payment for this Recurring Donation. NPSP automatically copies the selected value to each related Payment record. Optional.
          Recurring Donation Planned Installments Number of installments you expect to receive. Only used when Recurring Type is Fixed. Required when Recurring Type is Fixed.
          Recurring Donation Recurring Type Open indicates an ongoing Recurring Donation. Fixed indicates a Recurring Donation that has a specific number of installments. For Fixed, you must also populate the Number of Planned Installments field. Optional. If left blank, NPSP sets the value to Open on the target Recurring Donation record.
          Recurring Donation Status Indicates if this Recurring Donation is actively in use, temporarily suspended, or closed. Optional. If left blank, NPSP sets the value to Active on the target Recurring Donation record.
          Recurring Donation Status Reason The reason this Recurring Donation has its current Status value. Required when the Status is Closed or Paused.

          Campaign Fields

          The Campaign fields define a Campaign associated with a Recurring Donation, Opportunity, and/or Contact. Set a Campaign Member Status to create Campaign Member records for Contact1 and Contact2.

          Field LabelDescriptionRequired or Default Behavior
          Campaign Name For associating a Campaign with a Recurring Donation, Opportunity, and/ or Contact. Optional. If specified, NPSP tries to match to an existing Campaign by name. If no match is found, NPSP creates a new Campaign.
          Campaign Member Status For setting a Campaign Member Status. Optional. If specified along with a Campaign Name or Donation Campaign Source, NPSP creates a Campaign Member for Contact1 and Contact2.
          Donation Campaign Source The Salesforce ID of a Campaign to associate the Donation with.

          Optional. If specified, will match an existing Campaign by Campaign ID.

          If both the Donation Campaign Name and Donation Campaign Source are specified, NPSP will use the ID from the Donation Campaign Source.

          GAU Allocation Fields

          The GAU Allocation fields define GAU Allocation information for the donation. Define up to two GAU Allocations for each donation in your import file.

          Note
          Note You must use Advanced Mapping instead of Help Text mapping to use these fields. See Advanced Mapping Overview for more information.

          These are the GAU Allocation 1 fields in the NPSP Data Import object.

          Field LabelDescriptionRequired or Default Behavior
          GAU Allocation 1: GAU The Salesforce ID for the GAU. Required if you want to designate a GAU Allocation for the donation. If you're using the Data Import Wizard you must indicate it's a Salesforce ID on the Import screen. For more information, see Upload Data from the Template.
          GAU Allocation 1: Amount The monetary amount for this allocation. You must enter either an amount or a percent (but not both) for the GAU Allocation.
          GAU Allocation 1: Percent The percent of the donation total for this allocation. You must enter either an amount or a percent (but not both) for the GAU Allocation.
          GAU Allocation 1: Imported The Salesforce ID for the GAU Allocation. Optional. If not populated with an ID prior to import, NPSP will automatically populate after processing.

          The same fields exist for GAU Allocation 2, and you use them the same way to add or update a secondary GAU Allocation on the donation.

          System Fields

          The System fields capture information about the import including import statuses and information about the NPSP Data Import record.

          The System fields capture information about the import including import statuses and information about the NPSP Data Import record. Unless noted otherwise in the table below, the possible statuses for each target object (Account, Contact, Opportunity, etc.) are:

          Field LabelDescriptionRequired or Default Behavior
          Account1 or Account2 Import Status Indicates if an Account was created or matched an existing Account. Automatically populated by NPSP.
          ApexJobId

          The ApexJobID of the Batch Job that processed the record.

          Automatically populated by NPSP.
          Contact1 or Contact2 Import Status Indicates if a Contact was created or matched an existing Contact. Automatically populated by NPSP.
          Contact1 Consent Message The text of the Elevate Giving Page consent message. Populated by Salesforce.org Elevate integration.
          Created By The Salesforce User who created the NPSP Data Import record. Automatically populated by NPSP.
          Data Import ID The auto-numbered name of the NPSP Data Import record. Automatically populated by NPSP.
          Donation Campaign Import Status Indicates if a Campaign in the Donation Campaign Source or Donation Campaign Name field matched against an existing Campaign or if a new Campaign was created. Automatically populated by NPSP.
          Donation Import Status Indicates if an Opportunity was created or matched an existing Opportunity. If you see the Best Match Used status, we used the best match that falls within the Number of Days from Donation Date specified AND is closest to the Donation Date.

          Automatically populated by NPSP Gift Entry.

          If using Data Importer, and providing a Donation Import value, manually set the Donation Import Status to Matched or User-Selected Match.

          Elevate Custom Metadata Custom metadata from Elevate Giving Pages. Formatted as JSON. Populated by Salesforce.org Elevate integration.
          Failure Information Description of what caused the NPSP Data Import record to fail to be imported. Automatically populated by NPSP.
          GAU Allocation 1 or GAU Allocation 2: Import Status Indicates if a GAU Allocation was created or matched an existing GAU Allocation. Automatically populated by NPSP.
          Home Address Import Status Indicates if a Household Address was created or matched an existing Address. Automatically populated by NPSP.
          Imported Date The date and time the NPSP Data Import record was successfully imported. Automatically populated by NPSP.
          Last Modified By Salesforce User who last updated the NPSP Data Import record. Automatically populated by NPSP.
          NPSP Data Import Batch Lookup to the NPSP Data Import Batch this record belongs to. If you'd like to add files in your CSV to an NPSP Data Import Batch, include the batch's Salesforce ID in this column. Optional or automatically populated by NPSP.
          Opportunity Contact Role 1 or Opportunity Contact Role 2: ImportStatus Indicates if an Opportunity Contact Role was created or matched an existing Opportunity Contact Role. Automatically populated by NPSP.
          Owner Salesforce User is the Owner the NPSP Data Import record. Automatically populated by NPSP.
          Payment ACH Consent Message The Elevate Giving Page consent message the donor agreed to. Populated by Salesforce.org Elevate integration.
          Payment Import Status Indicates if a Payment was created or matched an existing Payment. If you see the Best Match Used status, we used the best match that falls within the Number of Days from Donation Date specified AND is closest to the Donation Date. Automatically populated by NPSP.
          Status

          Indicates the result of the Dry Run or Data Import processing. Possible statuses are:

          • Imported—The NPSP Data Import record was successfully processed in Salesforce.
          • Failed—The NPSP Data Import record was not imported.

          • Dry Run — Validated—Dry Run was successful and the record is ready to be imported into the appropriate objects.

          • Dry Run — Error—Dry Run was unsuccessful and the NPSP Data Import record will not be processed until errors are resolved.

          • Any System errors which caused an issue with this import.

          Automatically populated by NPSP.
          • Matched: The imported record matched an existing Salesforce record.

          • Created: A new record was created because matching is disabled OR there were no matching records in Salesforce.
          • Best Match Used: More than one existing record in Salesforce matched the imported record.
          • Matched by Id: Either the Salesforce ID for the record was included in the import file and used to match an existing Salesforce record or Dry Run found the record ID.
          • Match None: Only used during Dry Run. There are no records in Salesforce that match the value listed in the field. A new record will be created when the import is processed.

          • Any System errors which caused an issue with this import.
           
          Loading
          Salesforce Help | Article