salesforce b2c implementation guide
DESCRIPTION
Salesforce B2C Implementation GuideTRANSCRIPT
Implementing Person AccountsSalesforce.com, Winter ’15
@salesforcedocsLast updated: November 7, 2014
© Copyright 2000–2014 salesforce.com, inc. All rights reserved. Salesforce is a registered trademark of salesforce.com, inc.,as are other names and marks. Other marks appearing herein may be trademarks of their respective owners.
CONTENTS
About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Useful Websites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Introduction to Person Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Accounts Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2What is a Person Account? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Person Account Behaviors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Feature Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Converting Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Implementing Person Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Required Implementation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Recommended Implementation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Testing the Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Importing Person Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Import My Organization's Person Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11What Is Imported for Person Accounts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
ABOUT THIS GUIDE
This guide describes how to implement person accounts, which are an exciting major enhancement to the Salesforce data model. Personaccounts represent the individual clients with whom you do business. If your company operates on a business-to-consumer (B2C) model,person accounts are a simple yet powerful way to manage the entire life cycle of each customer relationship.
Audience
This guide is intended for administrators of organizations that operate on a business-to-consumer model and plan to use Salesforce totrack their client relationships. The procedures in Implementing Person Accounts on page 8 and Importing Person Accounts on page11 require familiarity with the Salesforce user interface and how it can be customized to meet particular business requirements.
Additional Resources
This guide is part of a comprehensive documentation set published by Salesforce.
Useful Websites
Force.com AppExchangeVisit Force.com AppExchange at http://sites.force.com/appexchange to browse on-demand apps that you can easily install into yourSalesforce organization.
Salesforce DevelopersVisit developer.salesforce.com for developer-oriented resources such as toolkits, API documentation, blogs, and discussion boards.
IdeaExchangeVisit IdeaExchange at ideas.salesforce.com for information on upcoming products from Salesforce.
1
INTRODUCTION TO PERSON ACCOUNTS
Does your business operate on a business-to-consumer model? By default, accounts in Salesforce are designed for a business-to-businessmodel in which accounts represent firms, corporations, and other institutions such as nonprofit organizations. To facilitate interactionswith customers who are individual human beings, such as a client buying an insurance policy or a patient receiving medical care, considerimplementing person accounts.
Read the following sections to learn whatperson accounts are, their capabilities, and their supported fields.
Accounts Overview
EDITIONS
Business accounts availablein: All Editions exceptDatabase.com
Person accounts availablein: Enterprise, Performance,Unlimited, and DeveloperEditions
Accounts are your organization’s customers, competitors, and partners. Each account storesinformation such as name, address, and phone numbers. For each account, you can store relatedinformation such as opportunities, activities, cases, partners, contracts, and notes.
The Accounts tab displays a home page that lets you quickly create and locate all types of accounts,and also sort and filter your accounts using standard and custom list views. In addition, this tab letsyou view and edit detailed information on each account to which you have access.
You can also enhance your traditional account data with your customers’ social information. Withthe Social Accounts and Contacts feature, you can see your accounts’ social network profiles andother social data—directly in Salesforce. Easy access to this information helps you know yourcustomers better, so you can solve their problems and build stronger relationships.
Learning about Types of Accounts for Managing Your BusinessYou can manage your business with business accounts and person accounts. Depending on your organization’s business model, you mayuse business accounts, person accounts, or both.
For this type of account,You can useWhen you dobusiness with
The individuals who work at those companies are contacts.
If your organization has a partner portal, you can create partner accounts, whichare business accounts that a channel manager uses to manage partnerorganizations, partner users, and activities.
Business accountsCompanies
The individuals can be people who, for example, may be a financial services client,an online shopper, or a vacation traveler.
Person accountsIndividual consumers
Note: In the Salesforce Help and other Salesforce documentation, the word account by itself always refers to both businessaccounts and person accounts. We use the terms business account and person account when there are differences between thetwo kinds of accounts.
2
What is a Person Account?
EDITIONS
Business accounts availablein: All Editions exceptDatabase.com
Person accounts availablein: Enterprise, Performance,Unlimited, and DeveloperEditions
Note: Person accounts are not enabled by default in Salesforce. To quickly verify whetheryour organization uses person accounts, see if you have an option to select Person Accountas the record type when you create a new account. To request person accounts, check withyour administrator.
A person account is an individual consumer with whom you do business, such as a financial servicesclient, an online shopper, or a vacation traveler. Person accounts are applicable to organizationsthat operate on a business-to-consumer model as opposed to a business-to-business model.
In a business-to-business model, there is a natural differentiation between the other businesseswith whom you work and the people associated with those businesses. In Salesforce, that translatesto accounts and contacts having different fields, features, and tabs. In a business-to-consumermodel, because you are providing products or services to people rather than companies ororganizations, the distinction between accounts and contacts does not exist. Consequently, person accounts in Salesforce have acombination of fields from both accounts and contacts, and can be used as contacts in most situations that involve contacts. For example,business accounts do not have standard fields for email address and job title, but person accounts do. Also, person accounts can beassociated with campaigns just like contacts, but business accounts cannot. For details on the contact-specific functionality that appliesto person accounts, see “Person Account Behaviors” in the Salesforce Help.
The ability for person accounts to act like contacts is made possible by applying an account record type which has special properties.The default name of this record type is “Person Account.” Your administrator may have changed the name of this record type, and alsomay have created more account record types that have the same special properties.
Note: In the Salesforce Help and other Salesforce documentation, the word account by itself always refers to both businessaccounts and person accounts. We use the terms business account and person account when there are differences between thetwo kinds of accounts.
Person Account Behaviors
EDITIONS
Business accounts availablein: All Editions exceptDatabase.com
Person accounts availablein: Enterprise, Performance,Unlimited, and DeveloperEditions
Note: Person accounts are not enabled by default in Salesforce. To request person accounts,contact Salesforce.
Person accounts are accounts that can also be used as contacts in many situations. The followingtable summarizes the key areas in which person accounts differ from business accounts or haveunique considerations:
Person Account BehaviorSalesforce Functionality
Person accounts can only be merged with otherperson accounts. See “Merging DuplicateAccounts” in the Salesforce Help.
Account Merge
On the accounts home page, the fields in theQuick Create area are based on whether the
Account Quick Create
default account record type set on your profileis a person account record type or a businessaccount record type.
3
What is a Person Account?Introduction to Person Accounts
Person Account BehaviorSalesforce Functionality
Person accounts are accounts that support contact fields andcapabilities.
Accounts
Person accounts can be associated with activities using either theName or Related To fields.
As with contacts, person accounts can be invited to events andrequested meetings.
Activities
For users to request a meeting with a person account, the Emailfield must be added to the Person Accounts page layout.
As with contacts, person accounts can be added to campaigns andhave a Campaign History related list.
Campaigns
On cases, person accounts can be entered in the AccountName field, the Contact Name field, or both.
Cases
When you follow person accounts, you follow the account fields,but not the contact fields.
Chatter Feed Tracking
As with contacts, person accounts can be enabled as users for yourSalesforce Communities and Customer Portals.
Communities and Customer Portal
As with contacts, you can add person accounts to the ContactRoles related list on cases, contracts, and opportunities.
Contact Roles
In most situations, you can use person accounts as if they werecontacts. You can include them in all contact list views except onthe contacts home page.
Unlike business accounts, person accounts do not have a Contactsrelated list. However, you can use the Partners related list to trackrelationships between different person accounts.
Contacts
Custom objects with relationships to either accounts or contactscan be added as related lists on person accounts.
Custom Objects
Person accounts are not supported by Data.com Prospector orData.com Clean.
Data.com
Person accounts are currently supported in Connect Offline,Salesforce for Outlook, Salesforce Side Panel, and Connect forOutlook version 3.2 and later.
Desktop Integration
As with contacts, you can send individual emails and mass emailsto person accounts.
Person accounts are supported, but additional configuration isrequired.
ExactTarget
Account fields for person accounts can be tracked using theaccount field history settings, but contact fields for person accountsare configured on the contact field history settings page.
Field History
4
Person Account BehaviorsIntroduction to Person Accounts
Person Account BehaviorSalesforce Functionality
A predetermined combination of standard account and contactfields is available on person account page layouts. In addition, all
Fields
custom account and contact fields are available. See “PersonAccount Fields” in the Salesforce Help.
Note that some business account fields are not supported forperson accounts, such as Parent Account and ViewHierarchy. Also, the Reports To field on contacts is notsupported for person accounts.
You can rename field labels for a person account so alternate termsdisplay in Salesforce.
Person accounts have a person icon ( ), while business accountshave a folder icon ( ). The person account icon can be added to
Icons
search results, list views, and lookup dialogs using the criteria “IsPerson Account equals True.”
Person accounts can be imported using the Data Import Wizard.Alternately, person account data can be imported using the ImportWizard for Person Accounts.
Import Wizards
Leads with a blank Company field are converted to personaccounts. The default person account record type for your profile
Leads
is applied to the new person account. Note that you can only createleads with a blank Company field using the Force.com API. Leadswith a value in the Company field are converted to businessaccounts. The default business account record type for your profileis applied to the new business account.
Person accounts appear in both account and contact list views.Add the Is Person Account icon to list views to visually
List Views
differentiate person accounts from other records, and to includeor exclude person accounts in a list.
Mobile configurations that include the account object automaticallydeliver person accounts and business accounts to users' mobiledevices.
Person accounts can be excluded from the configuration's dataset using the criteria “Is Person Account equals False.” To
Mobile Configurations
mobilize only person accounts, use the criteria “Is PersonAccount equals True.” If a mobile configuration includesaccounts but not contacts, users assigned to that configurationwill see a Contacts tab in the mobile client application, and the tabwill contain person accounts.
Person account components and attributes can be included inmanaged and unmanaged packages.
Packaging
5
Person Account BehaviorsIntroduction to Person Accounts
Person Account BehaviorSalesforce Functionality
Person accounts have unique page layouts that can have accountfields, contact fields, account custom links, account related lists,
Page Layouts
and contact related lists. Person accounts page layouts do notsupport the Reports To and Parent Account fields.
Person accounts are supported, but additional configuration isrequired.
Pardot
You can use the Partners related list to relate person accounts toeach other. We recommend that you rename the Partners related
Partners
list to “Related Accounts,” “Relationships,” or a similar term thatreflects how your person accounts are connected.
Administrators can configure multiple record types for personaccounts. A person account can only be changed to another personaccount record type.
Record Types
Administrators can customize the names of tabs and fields relatedto person accounts, such as:
Renamed Tabs and Standard Fields
• The Accounts tab name, the business account fieldlabel, and the person account field label.
• The Contacts tab name and the business contact fieldlabel.
For organizations that have enabled person accounts andSalesforce1, person accounts can be created, accessed, andmanaged within Salesforce1 for most features.
Salesforce1
Person accounts only appear in account search results.Administrators can add the Is Person Account icon to
Search
account search layouts in order to differentiate person accountsfrom business accounts.
As with contacts, person accounts can be enabled as users for yourSelf-Service portal.
Self-Service Portal
Note: Starting with Spring ’12, the Self-Service portal isn’tavailable for new organizations. Existing organizationscontinue to have access to the Self-Service portal.
Contact sharing is not available if you have enabled personaccounts. The organization-wide default for contacts is set toControlled by Parent and is not editable.
If your organization has customized your contact sharing settingsand you want to enable person accounts, change your
Sharing Settings
organization-wide default for contacts to Controlled by Parent,which removes all your contact sharing rules and manually sharedcontacts.
6
Person Account BehaviorsIntroduction to Person Accounts
Person Account BehaviorSalesforce Functionality
As with contacts, you can link person accounts to social networkprofiles
Social Accounts, Contacts, and Leads
As with contacts, you can send individual and mass Stay-in-Touchrequests to person accounts.
Stay-in-Touch Requests
Person accounts count against both account and contact storagebecause the API considers each person account to consist of oneaccount as well as one contact.
Storage
Creating or editing a person account triggers account workflowrules.
Workflow Rules
Considerations
Prior to implementing person accounts, note the following considerations.
Feature Availability• As a prerequisite, an administrator must have defined at least one account record type before Salesforce can enable person accounts
for your organization.
• Person account functionality is permanent and cannot be reverted. For example, after person accounts have been enabled, the listof account fields that you can access from Setup at Customize > Accounts > Fields will always include contact fields.
• Organizations with person accounts cannot be downgraded to Personal Edition.
Converting Records• Before conversion, there must be a one-to-one relationship between each business account record and its corresponding contact
record. Furthermore, fields common to both records such as Owner and Currency must have identical values.
• After conversion, the new person accounts will have unique one-to-one relationships with the contact records that formed them.As is true for all person accounts, no other contacts can be associated to a person account.
• We strongly recommend testing your conversions in a sandbox before modifying actual production data.
• You can use version 8.0 or later of the API to separate person accounts into individual business account and business contact records.
7
ConsiderationsIntroduction to Person Accounts
IMPLEMENTING PERSON ACCOUNTS
This section contains required steps and recommendations for implementing person accounts.
Required Implementation Steps
Person accounts are available upon request for Enterprise, Unlimited, Performance, and Developer Edition organizations.
Note: Person accounts count against both account and contact storage because the API considers each person account to consistof one account as well as one contact. Additional storage may be necessary when you implement person accounts, so you shouldreview your storage usage.
Enabling person accounts is permanent and cannot be reverted. If you are an existing customer, we recommend creating a sandboxto preview how person accounts will affect your organization.
Follow these steps to get started with person accounts.
1. Create at least one record type for accounts.
2. Grant read permission on contacts for profiles that have read permission on accounts.
3. Ensure that the contact sharing organization-wide default is set to “Controlled by Parent.”
4. After you do steps 1–3, contact Salesforce to enable person accounts.
5. From Setup, click Customize > Accounts > Person Accounts.
6. Assign person account record types to profiles that require person accounts.
For more information, see “Creating Record Types” in the Salesforce Help.
Recommended Implementation Procedures
Salesforce recommends that you follow additional implementation procedures for person accounts. These procedures are optional;implement them as needed for your organization's unique configuration. You can perform these procedures in any order, at any time.
Customize the names of tabs and field labels
1. Rename the Accounts tab and the business account and person account fields to reflect your business use.
2. Rename the Contacts tab and the business contact field to reflect your business use.
3. Rename the Partners related list to “Related Accounts,” “Relationships,” or a similar phrase or term that reflects how your personaccounts relate to one another.
Customize person account page layouts
1. From Setup, click Customize > Accounts > Person Accounts > Page Layouts.
2. Add contact fields and related lists to the page layout as needed.
Customize person account record typesWhen person accounts are enabled, a default person account record type is automatically created. You can modify this defaultperson account record type, and you can also add additional person account record types.
8
Add the person account icon to search results and lookup dialogsThe person account icon corresponds to the Is Person Account field. The icon visually distinguishes person accounts frombusiness accounts in account lists and from business contacts in contact lists. If your organization works exclusively with personaccounts, adding the icon is not necessary.
Add the person account icon and other person account fields as columns in public list viewsAdd these icons to the Accounts and Contacts tabs and for Mass Email and Mass Stay-in-Touch requests.
You can also configure the search criteria of public list views so that person accounts are included or excluded as appropriate.
Note that individual users will need to update their personal list views as well.
Customize public reports and customize public dashboards to include person account informationNote that individual users will need to update their personal reports and dashboards as well.
Add the Is Person Account field to rulesAdd the Person Account field to rules such as:
• Workflow rules
• Assignment rules
• Escalation rules
• Field validation rules
• Territory assignment rules
Note: When configuring lead assignment rules, create separate email notification templates for business accounts and personaccounts. That way you can show only the fields that are supported for each type of account. For example, a person accountemail notification template should not have the Company field.
Customize partner roles for person accountsExamples of customized partner roles include “Spouse,” “Neighbor,” “Attorney,” and “Accountant.”
Customize leadsCreate lead record types for person accounts.
Create lead page layouts for business accounts and person accounts. Page layouts for leads that will become business accountsmust contain and require the Company field. Page layouts for leads that will becomeperson accounts must not contain theCompany field.
Note: Leads with a blank Company field are converted to person accounts. The default person account record type for yourprofile is applied to the new person account. Note that you can only create leads with a blank Company field using theForce.com API. Leads with a value in the Company field are converted to business accounts. The default business accountrecord type for your profile is applied to the new business account.
Convert existing account-contact pairs to person accounts
1. Create one-to-one relationships between account and contact records. In other words, remove all contacts on the accountsexcept for the contact that will be converted with the account.
2. Identify the accounts that have a different owner than the associated contact. Change the ownership of either record so bothare owned by the same user.
3. If your organization uses multiple currencies, identify the accounts that have a different currency than the associated contact.Change the currency of either record so both have the same currency.
4. Make sure the Parent Account field is blank on all accounts that will be converted. Also, make sure none of the accountsare the parent account of another account.
5. Make sure the Reports To field is blank on all contacts that will be converted. Also, make sure none of the contacts are inthe Reports To field of another contact.
9
Recommended Implementation ProceduresImplementing Person Accounts
6. As much as reasonably possible, edit the accounts so they contain all desired field values.
7. Using the SOAP API, update the record types of the chosen accounts to convert them to the desired person account record type.We recommend running a test conversion in your sandbox.
Note: The following field values are lost during conversion. To preserve the information in these fields, migrate the data tocustom fields prior to conversion. You can later expose the custom fields on a person account page layout.
• Accounts lose Account Name, which is replaced by the First Name and Last Name of the contact.
• Contacts lose Salutation, Phone, Fax, Description, Created By, Last Modified, and LastActivity. Converted person accounts contain the Phone, Fax, Description, Created By, LastModified, and Last Activity from the source account.
Update integrationsFor more information on the API, visit Salesforce Developers.
Testing the Implementation
Perform the following tests to confirm a successful implementation:
• Verify that each person account page layout correctly contains related lists for any associated custom objects.
• Verify that custom object page layouts correctly contain account lookup fields, if such relationships have been configured.
• Verify that workflow rules involving accounts trigger correctly.
• Verify that API-based integrations correctly create, update, and access person accounts and business accounts.
• Verify that leads correctly convert into person accounts and business accounts.
• Verify that account assignment rules correctly assign person accounts and business accounts to territories.
Best Practices
• If your organization exclusively uses person accounts (meaning you never use business accounts, which have a Contacts related list),consider giving the Accounts and Contacts tabs the same name. However, to differentiate the tabs, append a character such as aperiod (.) or asterisk (*) to the Contacts tab name. For example, the Accounts tab becomes Clients and the Contacts tab becomesClients*.
• Alternatively, modify user profiles to prevent the Contacts tab from displaying: change the visibility setting for the Contacts tab to“Default Off” or “Hidden.”
• Consider renaming the standard field Account Site and repurposing it as a unique identifier for person accounts. For example,you could rename the field “Client Number” and use it to store a number that a uniquely identifies each person. By default this fielddisplays in many list views and other areas throughout Salesforce, and can help differentiate people who have similar names.
• As leads must have a blank Company field in order to convert to person accounts, substitute a custom lead field (for example, acustom field named “Employer”) to contain what otherwise would be tracked in the Company field.
10
Testing the ImplementationImplementing Person Accounts
IMPORTING PERSON ACCOUNTS
As an administrator, you can import person accounts for your organization by running the person account import wizard. The followingsections describe how the wizard works.
Note: An additional wizard not described in this guide allows individual users to import person accounts they own. For moreinformation, see the online help.
Import My Organization's Person Accounts
EDITIONS
Person account importavailable in: Enterprise,Performance, Unlimited,and Developer Editions
USER PERMISSIONS
To import yourorganization's personaccounts:• “Import Person
Accounts”
Important: Salesforce is replacing individual import wizards for accounts, contacts, andother objects with the unified Data Import Wizard. (Individual import wizards open in smallpop-up windows, while the unified wizard opens in a full browser with dataimporter.app atthe end of the URL.) To start using the unified wizard, click Data Management > DataImport Wizard in Setup, or click the Import option under My Settings. (The options you seedepend on your permissions.)
With the Import My Organization's Person Accounts wizard, you can import person accounts thatare owned by different users. To understand how person account records are matched to preventduplicates, see “What Is Imported for Person Accounts?” in the Salesforce Help.
Note: If the label for person accounts has been renamed for your organization, the renamedlabel will appear in the import wizard itself and in the Tools area of the accounts home page,but not in the Data Management area under Setup. (Renamed labels do not appear in anypages in Setup.)
Follow these steps to import person accounts for your organization.
1. Launch the wizard
2. Prevent duplicate records
3. Specify owner and lookup relationships
4. Select record type
5. Upload your import file
6. Map fields
7. Confirm and submit your import
8. Complete your import
Note: The import wizard is dynamic; it displays different screens depending on what you are importing and the setup of yourorganization.
Launch the wizardTo import person accounts for your organization:
1. From Setup, click Data Management > Import Person Accounts.
Alternatively, click Import My Organization's Person Accounts in the Tools area of the accounts home page.
11
2. For best results, perform all of the steps provided on the introductory page.
3. Click Start the Import Wizard! to begin your import.
Prevent duplicate records1. The import wizard can compare the records in your import file with existing records in Salesforce in order to prevent duplicate
records from being created as a result of your import. Indicate whether you would like to prevent duplicate records from beingcreated. You must select Yes in order to update existing records.
2. If you choose Yes, then additional choices will appear:
• Choose the field that you are using to match existing records in Salesforce with records in your import file. The ExternalID option is disabled if no external ID fields have been created for your records.
• Choose what you want to happen if matches are found—only import new records, only update existing records, or updateexisting records and import new ones.
Note: If you have chosen to match by Salesforce ID, you can only update existing records; you cannot importnew ones.
3. Click Next.
Specify owner and lookup relationships1. Specify the field in your import file that contains person account owners.
When you choose “Name,” the following formats are valid:
• First name followed by last name
• Last name followed by first name
• Alias
• Username
2. Records can have custom fields that create lookup relationships with other records. If you have included lookup fields in your importfile, then check the corresponding boxes.
Note: Any related records must already exist in Salesforce before proceeding. Related records will not be updated duringyour import even if your import file contains different values for fields on those related records.
3. Click Next.
Select record type1. Choose the record type that you want to assign to the records in your import file.
2. If you are inserting new records and updating existing records at the same time, then choose whether to override the record typesof existing records.
3. Click Next.
Upload your import file1. Click Browse... to provide the location of your import file.
12
Import My Organization's Person AccountsImporting Person Accounts
2. Choose the character encoding of your import file. In most cases, you can accept the default value.
3. Make additional settings depending on the setup of your organization, such as whether workflow rules will be triggered and thelanguage of the records in the import file.
4. Click Next.
Map fields1. Map the fields in your import file to the appropriate Salesforce fields by matching the fields on the left, which includes all the columns
in your import file, with the appropriate Salesforce field on the right. If the column labels in your import file exactly match field labelsin Salesforce, the wizard automatically maps those fields for you. However, if two or more of your file's column labels are identicalmatches with a field in Salesforce, you must map the fields manually.
Note: Some Salesforce fields cannot be updated using import, for example, the Created Date and Last ModifiedDate. So even though you may be using an exported report as your import file, some of the Salesforce fields in your filecannot be mapped.
2. Click Next. The import wizard warns you if you have not mapped all of the fields in your import file. Unmapped field values are notimported.
Confirm and submit your import1. Read any warning messages that the import wizard displays. Optionally, click Previous to return to earlier steps and resolve potential
problems.
2. Click Import Now! to submit your import request to Salesforce.
Complete your import1. A message indicates approximately how long the import will take. When the import operation is finished, a message from Customer
Support will be sent to the email address shown.
2. Click Finish to exit the wizard.
3. To monitor the status of your pending import, from Setup, click Monitoring > Imports.
What Is Imported for Person Accounts?
EDITIONS
Person account importavailable in: Enterprise,Performance, Unlimited,and Developer Editions
Important: Salesforce is replacing individual import wizards for accounts, contacts, andother objects with the unified Data Import Wizard. (Individual import wizards open in smallpop-up windows, while the unified wizard opens in a full browser with dataimporter.app atthe end of the URL.) To start using the unified wizard, click Data Management > DataImport Wizard in Setup, or click the Import option under My Settings. (The options you seedepend on your permissions.)
The import wizards for person accounts allow you to prevent the creation of duplicate records bymatching records according to one of the following fields: Account Name, SalesforceID, or Email. In your import file, include a column for the field that you are using for record matching.
Note: Your administrator may have renamed “person account” to another term. If so, the import wizard will refer to the newname.
13
What Is Imported for Person Accounts?Importing Person Accounts
Matching by NameWhen you select this option, the import wizard will detect existing records in Salesforce that have the same name. Note that this typeof matching is not case-sensitive - for example, names that begin with a capital letter will be matched with the same name that beginswith a lowercase letter. If necessary, scan and standardize your custom object names before performing the import to prevent unintendedmatches.
Matching by Salesforce IDA Salesforce ID is a system-generated, case-sensitive string of 15 or 18 letters and numbers that uniquely identifies each Salesforce record.When you select this option, the import wizard will detect existing records in Salesforce that have the same Salesforce ID. Note thatSalesforce IDs are case-sensitive and must match exactly. Salesforce IDs can be obtained by running reports that include the ID field ofthe record.
Matching by EmailWith this option, person accounts in your import file will be matched with existing person accounts in Salesforce according to the exactvalue in the Email field.
Matching by External IDAn external ID is a custom field that has the “External ID” attribute, meaning that it contains unique record identifiers from a systemoutside of Salesforce. When you select this option, the import wizard will detect existing records in Salesforce that have the same externalID. Note that this operation is not case-sensitive - for example, “ABC” will be matched with “abc”. However, there is an exception: if thecustom field has the separate “Unique” attribute and the case-sensitive option for that attribute is selected, uppercase and lowercaseletters will not be considered identical.
If necessary, scan and standardize your external ID values before performing the import to prevent unintended matches.
When matching by external ID, if the import wizard finds duplicate records, only the first three duplicate records are reported to you inthe confirmation email.
Note: Only account custom fields with the “External ID” attribute are available for this step. While all custom contact fields areavailable on person account page layouts, custom contact fields with the “External ID” attribute are not available as matching fieldsduring person account import.
Ignoring or Updating Matching RecordsWhen the import wizard detects existing records in Salesforce that match according to the field you have chosen, you can choose oneof the following actions:
• Do not update existing records and only insert new records - If there are records in your file that are new and do not matchany existing records, then insert them into Salesforce. Also, ignore any records in your file that match an existing record, and donothing to the existing record.
• Update existing records and do not insert any new records - If there are records in your file that match an existing record, thenupdate the existing record. Also, ignore any records in your file that do not match an existing record, and do not insert them as newrecords.
• Update existing records and insert new records - If there are records in your file that are new and do not match any existingrecords, then insert them into Salesforce. Also, if there are records in your file that match an existing record, then update the existingrecord.
14
What Is Imported for Person Accounts?Importing Person Accounts
INDEX
AAccounts
overview 2Person accounts 3Social Accounts and Contacts 2
CConsumers
See Person accounts 3
IImport wizards
Import My Organization's Person Accounts 11
Importingperson accounts 13
OOverview
accounts 2
PPerson accounts
importing 13overview 3
15