Professional Documents
Culture Documents
Salesforce B2C Implementation Guide
Salesforce B2C Implementation Guide
Salesforce B2C Implementation Guide
© Copyright 2000-2007 salesforce.com, inc. All rights reserved. Salesforce.com and the “no software” logo are registered trademarks, and
AppExchange, “Success On Demand,” and “The Business Web” are trademarks of salesforce.com, inc. All other trademarks mentioned in
this document are the properties of their respective owners.
Table of Contents
Table of Contents
About this Guide.......................................................................................................................................................................3
Introduction to Person Accounts...............................................................................................................................................5
Implementing Person Accounts..............................................................................................................................................14
Importing Person Accounts.....................................................................................................................................................17
i
Table of Contents
ii
About this Guide
Audience
This guide is intended for administrators of organizations that operate on a business-to-consumer model and plan to use
Salesforce to track their client relationships. The procedures in Implementing Person Accounts on page 14 and Importing
Person Accounts on page 20 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.com and is not intended to be used in isolation.
In this guide, you will find cross-references to online help topics and other resources. For information on how to access and
use such resources, please review the sections below.
After you find the answer you need, you can click the Email Page link at the top of the window to
send a URL for the help topic or knowledge base solution to yourself or anyone else.
3
About this Guide
Useful Websites
AppExchange
Visit the AppExchange at http://www.salesforce.com/appexchange to browse on-demand apps that you can easily install into
your Salesforce organization.
Developer Network
Visit the Developer Network at http://www.salesforce.com/developer for developer-oriented resources such as toolkits, API
documentation, blogs, and discussion boards.
Idea Exchange
Visit the Idea Exchange at http://ideas.salesforce.com for information on upcoming products from salesforce.com.
4
Introduction to Person Accounts
What is an Account?
Accounts are your organization's customers, competitors, and partners. Each account stores information such as name, address,
and phone numbers. For each account, you can store related information 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. You can also sort and filter
your accounts using standard and custom list views. In addition, this tab lets you view and edit detailed information on each
account to which you have access.
If your organization has been enabled with person accounts, you have two different kinds of accounts: business accounts and
person accounts. Business accounts represent the other companies with which your organization does business. For business
accounts, the individuals who work at those companies are represented by contacts. Person accounts represent the individual
consumers with whom your company does business, such as a financial services client, an online shopper, or a vacation traveler.
Depending on your organization's business model, you may use business accounts, person accounts, or both. See "What is a
Person Account?" in the Salesforce online help for more information.
If your organization has been enabled with PRM, you can create partner accounts. Partner accounts are business accounts that
a channel manager uses to manage partner organizations, partner users, and activities.
Note: In the online help and other Salesforce documentation, the word "account" by itself always refers to both
business accounts and person accounts. The terms "business account" and "person account" are used when there are
differences between the two kinds of accounts.
A person account is an individual consumer with whom you do business, such as a financial services client, an online shopper,
or a vacation traveler. Person accounts are applicable to organizations that 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 businesses with whom you work and the
people associated with those businesses. In Salesforce, that translates to accounts and contacts having different fields, features,
and tabs. In a business-to-consumer model, because you are providing products or services to people rather than companies
or organizations, the distinction between accounts and contacts does not exist. Consequently, person accounts in Salesforce
have a combination 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 be associated with campaigns just like contacts, but business accounts cannot. For details on the
contact-specific functionality that applies to person accounts, see "Person Account Behaviors" in the Salesforce online 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
5
Introduction to Person Accounts
record type, and also may have created more account record types that have the same special properties. For more information
on record types, see "Managing Record Types" in the Salesforce online help and "Changing the Record Type Field" in the
Salesforce online help.
Note: In the online help and other Salesforce documentation, the word "account" by itself always refers to both
business accounts and person accounts. The terms "business account" and "person account" are used when there are
differences between the two kinds of accounts.
Person accounts are accounts that can also be used as contacts in many situations. The following table summarizes the key
areas in which person accounts differ from business accounts or have unique considerations:
Contacts In most situations, you can use person accounts as if they were
contacts. You can include them in all contact list views except
the Recent Contacts list on the contacts home page.
Unlike business accounts, person accounts do not have a
Contacts related list. However, you can use the Partners related
list to track relationships between different person accounts.
Contact Roles Like contacts, you can add person accounts to the Contact
Roles related list on cases, contracts, and opportunities.
Custom Objects Custom objects with relationships to either accounts or
contacts can be added as related lists on person accounts.
6
Introduction to Person Accounts
Partners You can use the Partners related list to relate person accounts
to each other. We recommend that you rename the Partners
7
Introduction to Person Accounts
Stay-in-Touch Requests Like contacts, you can send individual and mass Stay-in-Touch
requests to person accounts.
Storage Person accounts count against both account and contact
storage. The reason is because the API considers each person
account to consist of one account as well as one contact.
Workflow Rules Creating or editing a person account triggers account workflow
rules. See "Managing Workflow" in the Salesforce online help.
8
Introduction to Person Accounts
9
Introduction to Person Accounts
10
Introduction to Person Accounts
11
Introduction to Person Accounts
12
Introduction to Person Accounts
13
Implementing Person Accounts
Considerations
Prior to implementing person accounts, note the considerations described below.
Feature Availability
• As a prerequisite, an administrator must have defined at least one account record type before salesforce.com 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 list of account fields at Setup ➤ Customize ➤ Accounts ➤ Fields will always include contact fields.
• Organizations with person accounts cannot be downgraded to Personal Edition.
Converting Records
• The only way to convert existing business accounts and business contacts into person accounts is with version 8.0 or later
of the Apex API.
• 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 Salesforce Sandbox before modifying actual production data.
• It is possible to use version 8.0 or later of the Apex to separate person accounts into individual business account and business
contact records.
Implementation Steps
Follow the steps below to get started with person accounts. Please note that the order of the following steps is only a
recommendation; the steps after Step 1 are optional based on your organization's unique configuration and also can be performed
at any time.
1. Enable person accounts:
a. As a prerequisite, create at least one record type for accounts.
b. Person accounts are available upon request for Enterprise, Unlimited, and Developer Edition organizations. After you
have completed the prerequisite above, contact salesforce.com to make the request.
c. Please note that enabling person accounts is permanent and cannot be reverted. If you are an existing customer, we
recommend creating a Salesforce Sandbox to preview how person accounts will affect your organization.
2. Review your storage usage in case additional storage may be necessary. Person accounts count against both account and
contact storage. The reason is because the API considers each person account to consist of one account as well as one
contact.
3. Customize the names of tabs and field labels:
a. Rename the Accounts tab name, the business account field label, and the person account field label to meet
your business requirements.
b. Rename the Contacts tab name and the business contact field label to meet your business requirements.
14
Implementing Person Accounts
c. Rename the Partners related list to "Related Accounts," "Relationships," or a similar term that reflects how your person
accounts relate to each other.
5. Customize person account record types. When person accounts are enabled, a default person account record type is
automatically created. You can modify this default person account record type, and you can also add additional person
account record types.
6. Assign person account record types to profiles.
7. Add the person account icon to search results and lookup dialogs—the icon corresponds to the Is Person Account
field. The icon visually differentiates person accounts from business accounts in account lists and from business contacts
in contact lists. If your organization works exclusively with person accounts, then adding the icon is not necessary.
8. Similarly, add the person account icon and other person account fields as columns in public list views:
• On the Accounts tab.
• On the Contacts tab.
• For Mass Email.
• For Mass Stay-in-Touch requests.
In addition, configure the search criteria of public list views so person accounts are included or excluded appropriately.
Note that individual users will need to update their personal list views as well.
9. Customize public reports and customize public dashboards to include person account information.
Note that individual users will need to update their personal reports and dashboards as well.
10. Add the Is 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 person accounts. That way you can show only the fields that are supported for each type of account. For
example, a person account email notification template should not have the Company field.
11. Customize partner roles for person accounts—for example, add "Spouse," "Neighbor," "Attorney," and "Accountant."
12. Customize leads:
Note: Leads with a blank Company field are converted to person accounts. The default person account record type
for your profile is applied to the new person account. Similarly, leads with a value in the Company field are converted
to business accounts. The default business account record type for your profile is applied to the new business
account.
15
Implementing Person Accounts
a. Create one-to-one relationships between account and contact records. In other words, remove all contacts on the
accounts except for the contact that will be converted with the account.
b. Identify the accounts that have a different owner than the associated contact. Change the ownership of either record
so both are owned by the same user.
c. 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.
d. Make sure the Parent Account field is blank on all accounts that will be converted. Also, make sure none of the
accounts are the parent account of another account.
e. Make sure the Reports To field is blank on all contacts that will be converted. Also, make sure none of the contacts
are in the Reports To field of another contact.
f. As much as reasonably possible, edit the accounts so they contain all desired field values.
g. Using Apex API 8.0, 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 Salesforce Sandbox.
Note: The following field values are lost during conversion. To preserve the information in these fields, migrate
the data to custom 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 Last Activity.
Converted person accounts contain the Phone, Fax, Description, Created By, Last Modified, and
Last Activity from the source account.
14. Update integrations—for more information on the Apex API, visit the Apex Developer Network.
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 a period (.) or asterisk (*) to the Contacts tab name. For example, the Accounts tab becomes Clients and
the Contacts tab becomes Clients*.
• 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 field displays 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,
a custom field named "Employer") to contain what otherwise would be tracked in the Company field.
16
Importing Person Accounts
With the Import My Organization's Person Accounts wizard, you can import person accounts that are owned by different
users. To understand how person account records are matched to prevent duplicates, see "What Is Imported for Person
Accounts?" in the Salesforce online help.
Note: If the label for person accounts has been renamed for your organization, the renamed label 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 any pages under App Setup or Administration Setup.)
Follow these steps to import person accounts for your organization. Click each link for more details.
1. "Launch the wizard" in the Salesforce online help
2. "Prevent duplicate records" in the Salesforce online help
3. "Specify owner and lookup relationships" in the Salesforce online help
4. "Select record type" in the Salesforce online help
5. "Upload your import file" in the Salesforce online help
6. "Map fields" in the Salesforce online help
7. "Confirm and submit your import" in the Salesforce online help
8. "Complete your import" in the Salesforce online help
Note: The import wizard is dynamic; it displays different screens depending on what you are importing and the setup
of your organization.
17
Importing Person Accounts
3. Click Next.
3. Click Next.
Map fields
1. Map the fields in your import file with 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.
18
Importing Person Accounts
2. If the column labels in your import file exactly match field labels in Salesforce, the wizard automatically maps those fields
for you. However, if two or more of your file's column labels are identical matches with a field in Salesforce, then you must
map the fields manually.
Note: Some Salesforce fields cannot be updated using import, for example, the Created Date and Last
Modified Date. So even though you may be using an exported report as your import file, some of the Salesforce
fields in your file cannot be mapped.
3. Click Next. The import wizard warns you if you have not mapped all of the fields in your import file. Unmapped field
values are not imported.
Matching by Name
When you select this option, the import wizard will detect existing records in Salesforce that have the same name. Note that
this type of matching is not case-sensitive - for example, names that begin with a capital letter will be matched with the same
name that begins with a lowercase letter. If necessary, scan and standardize your custom object names before performing the
import to prevent unintended matches.
Matching by Salesforce ID
A 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 that Salesforce IDs are case-sensitive and must match exactly. Salesforce IDs can be obtained by running
reports that include the ID field of the record.
Matching by Email
With this option, person accounts in your import file will be matched with existing person accounts in Salesforce according
to the exact value in the Email field.
19
Importing Person Accounts
Matching by External ID
An external ID is a custom field that has the "External ID" attribute, meaning that it contains unique record identifiers from
a system outside of Salesforce. When you select this option, the import wizard will detect existing records in Salesforce that
have the same external ID. Note that this operation is not case-sensitive - for example, "ABC" will be matched with "abc".
However, there is an exception: if the custom field has the separate "Unique" attribute and the case-sensitive option for that
attribute is selected, uppercase and lowercase letters will not be considered identical. For more information, see "Custom Field
Attributes" in the Salesforce online help.
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 in the confirmation email.
Note: Only account custom fields with the "External ID" attribute are available for this step. While all custom contact
fields are available on person account page layouts, custom contact fields with the "External ID" attribute are not
available as matching fields during person account import.
20