5.1 Lead, Campaign, Account, Contact, and Opportunity Flow

Core Sales Data Flow

A Lead is a person or organization that has shown interest but has not yet been qualified into the customer model. Sales teams use Leads for inquiries from a form, list import, trade show, referral, partner event, or marketing campaign. A Lead can have a company name, contact details, source, rating, status, and owner. It is separate from Accounts and Contacts so sales development work can happen before the organization decides the person belongs in the durable customer database.

When a Lead is qualified, the user converts it. Conversion creates a new Account, creates a new Contact, and can create a new Opportunity. It can also attach the converted person to existing Account and Contact records when the user has access and the match is selected. The admin controls field mappings from Lead fields to Account, Contact, and Opportunity fields in Setup. A common mistake is adding a required custom field to Contact or Opportunity but forgetting that lead conversion must be able to populate it.

Campaigns And Member Status

Campaigns are the Salesforce feature that tracks marketing activity inside core Sales Cloud. A campaign may represent a webinar, email series, advertisement, trade show, direct mail run, or partner event. Campaign hierarchy can roll up related efforts, such as a fiscal quarter program with several child campaigns. Campaign Members link Leads and Contacts to the campaign. Member status values, such as Sent, Registered, Attended, or Responded, should match the business activity.

For administrator work, the status design matters because reports and campaign influence depend on consistent member data. If one campaign uses Attended and another uses Showed Up, reporting becomes messy. If the Responded flag is not set correctly on the member status, response reporting is misleading. If users only populate Lead Source, they lose the ability to track multiple touches for the same person. Lead Source is useful as an original-source field, but Campaign Members are better for many-to-many marketing participation.

Conversion Workflow

A practical lead process starts before conversion. Decide how Leads enter Salesforce, how they are assigned, what statuses mean, who can convert them, what duplicate rules run, and which fields are required. Web-to-Lead and imports can create many records quickly, so validation and assignment rules should be tested with real sample records. Do not make the status path so complex that users work around it with notes or spreadsheets.

Admin checklist for lead conversion

• Confirm Lead Status values include a converted status and match the sales process language.
• Review Lead field mappings to Account, Contact, and Opportunity fields.
• Check required fields on Account, Contact, and Opportunity before enabling new validation rules.
• Test conversion as a standard sales user, not only as System Administrator.
• Verify duplicate rules and matching rules warn or block at the right point.
• Confirm record type selection and page layouts after conversion.
• Report on converted Leads, conversion rate, source quality, and campaign response.

Accounts, Contacts, And Opportunities

Accounts and Contacts are the durable relationship records. Opportunities represent sales deals, renewals, expansions, or other revenue events. A B2B organization usually treats Accounts as companies and Contacts as people at those companies. A B2C organization may use person accounts if enabled and designed intentionally, but that is a major model choice. Platform Administrator scenarios usually focus on knowing which record owns which data and how the records relate.

Opportunities belong to Accounts and usually have a primary Contact Role or related Contacts through Opportunity Contact Roles. Contact Roles help show who is the evaluator, signer, economic buyer, or technical contact. Products and Price Books are discussed in the next section, but the key flow here is that an Opportunity should represent a qualified revenue pursuit, not a raw inquiry. If the team creates Opportunities too early, forecasts and pipeline reports become inflated.

Security, Ownership, And Automation Boundaries

Ownership drives record access when org-wide defaults are private or controlled. Leads, Accounts, Contacts, Opportunities, and Campaigns can have different sharing behavior, and users may be able to convert a Lead only when they have the right object permissions and field access. A conversion failure that looks like a sales process problem may really be Create permission missing on Opportunity, field-level security on a mapped field, or a validation rule blocking the target record.

Automation should support this lifecycle without hiding the business decision. Assignment rules can route Leads by region, product, queue, or source. Flow can stamp source details, create follow-up tasks, or notify owners. Duplicate rules can warn users before they create another Account or Contact. Avoid automating conversion itself unless the qualification criteria are truly objective and the downstream data requirements are stable. Bad automated conversion creates duplicates faster than humans can repair them.

Scenario Judgment

Suppose marketing imports 3,000 trade show attendees. The sales manager wants every attendee converted to an Account and Opportunity immediately. A strong admin would slow down and ask what qualifies a real Opportunity, whether the attendee company already exists, whether campaign membership should capture attendance, and whether SDRs should work the Leads first. The safer configuration is usually to import or capture them as Leads, associate them with the trade show Campaign, assign them through rules or queues, and convert only qualified records after duplicate checks.

For hands-on practice, create a small Campaign in a Trailhead Playground, add one Lead and one Contact as Campaign Members, customize member statuses, convert the Lead, and inspect the resulting Account, Contact, and Opportunity. Then add a required custom field to Opportunity and test conversion again. This exercise makes the common exam traps visible: required fields, mappings, duplicate behavior, owner assignment, and reporting expectations.