When a deal closes, the customer’s next conversation is with support, and that first case shows whether your lead-to-case handoff works. If it opens with only a name and an email address, the agent starts from zero on a customer your sales team spent months learning. Running Sales Cloud and Service Cloud in one org solves half the problem, because reps and agents already share the same Account and Contact records with nothing to sync.
The other half is yours to build. Lead conversion stops at an Account, a Contact and an optional Opportunity, so anything service needs has to be mapped across at that moment, and nothing in standard Salesforce opens a case at Closed Won or links it back to the deal. A record-triggered flow fills that gap by creating the onboarding case with the customer’s entitlement attached, so the SLA clock starts on time, then handing it to a queue or Omni-Channel routing while account teams keep the rep in view.
Flow is the right trigger for most orgs, and 10 documented failure points, such as duplicate contacts that break Email-to-Case or milestones that stay open after a case closes, can still undo the build. Cost depends on project size, mainly license counts and how much data needs cleaning. At HyphenX, most build time on these projects goes into the flow and the entitlement step, because conversion, sharing and routing mostly run on standard settings.
TL;DR
One Record Chain, No Sync Required
Sales Cloud and Service Cloud in one org share a single database. Reps and agents open the same Account and Contact records, so there’s nothing to sync. Licenses decide the features each person gets, with entitlements and the Service Console reserved for Service Cloud users.
Where the Handoff Drops Data
Lead conversion creates an Account and Contact, plus an optional Opportunity, then stops. No standard step opens a case when a deal closes, and the Case object has no standard field pointing back to the deal. Left alone, an agent’s first case has no link to what was sold.
A Closed Won Flow That Opens the Right Case
A record-triggered flow on Opportunity fires once when the stage reaches Closed Won. It creates an onboarding case linked to the deal through a custom lookup and attaches the customer’s entitlement, so the SLA clock is already running before an agent opens the case.
What Does “One Org” Mean for Sales Cloud and Service Cloud?
One org is one Salesforce database. When you run Sales Cloud and Service Cloud together, a rep and a support agent open the exact same Account record, with the same ID and history. Both products are licenses on one shared platform, so the phone number an agent corrects at 9 a.m. is the number the rep dials at 9:05.
Whether your Sales Cloud setup went live first or your Service Cloud implementation did, both teams work from the same records:
- Accounts and Contacts, including every field and related list on them
- The activity timeline, so a logged call or email shows up for whoever opens the record
- The Cases related list on the account, for anyone with access to those cases
- Basic case management, since sales reps can use cases to track issues during a deal
- Account-level reports that put opportunities and cases side by side, such as open cases on deals closed this quarter
What Service Cloud adds on top is the support machinery, like entitlements and Omni-Channel routing, and the license on each user decides which of those tools they see.
Why Customers Feel the Gap Between Closed Won and the First Case
Even with shared records, the deal’s context stays on the Opportunity: the products and the close date, plus whatever the rep wrote down about the customer’s priorities. Agents work in cases, and a case opened from a customer’s first email arrives with a contact and account attached and nothing about the deal. By then the rep has moved on, and the answers sit in Opportunity notes the agent never opens.
Lead conversion stops at the Opportunity, and nothing in standard Salesforce opens a case when the deal closes. What an onboarding case needs varies by business, a kickoff call for one and an install date for another, so its fields are yours to define. Until a flow creates it, the onboarding case in your sales-to-service handoff exists only if someone remembers to open one.
The customer pays for that gap. They repeat answers they already gave the rep, and the SLA they paid for starts late or never starts at all, because the case never got an entitlement.
The Record Chain From Lead to Case
In one org, the lead-to-case chain runs in 6 steps. Standard Salesforce covers steps 1 to 3 and step 6 with configuration; steps 4 and 5 are the ones you build.
- A lead comes in and sales works it. Web forms, imports and reps all create Lead records, lead assignment rules route each one to an owner, and the rep qualifies it the way Sales Cloud handles leads and opportunities day to day.
- The rep converts the lead. Lead conversion creates an Account and Contact, or a person account in B2C orgs, plus an Opportunity unless the rep chooses to skip it.
- The deal reaches Closed Won. The rep updates the Opportunity stage, and that stage change is the signal everything downstream listens for. Closed Won here means whichever stage your sales process treats as won.
- A flow opens the onboarding case. A record-triggered flow creates a Case on the same Account and Contact, with a custom lookup back to the Opportunity.
- The entitlement starts the SLA clock. The flow attaches the customer’s entitlement, and the entitlement process starts tracking milestones on the new case, such as a kickoff call.
- Routing hands the case to service. A queue, a case assignment rule or Omni-Channel puts the case in front of the right agent.
With Sales Cloud and Service Cloud in one org, steps 4 and 5 are also where a failed run stays silent, so each one needs a fault path and a report that exposes a missing case.
What Lead Conversion Carries Forward and What It Leaves Behind
You control which lead data rides along into the new records before the converted lead turns read-only, and these 7 rules decide what makes it across:
- Field mapping: custom lead fields map only to custom account, contact or opportunity fields, and any value you leave unmapped stays behind on the lead.
- Multi-object mapping: in Lightning, one lead field can feed the Account and the Opportunity at once, so an Implementation Contact value lands on both in one pass.
- One source per target: each target field accepts only 1 source field, so 2 lead fields can never feed the same account field.
- Matching types: checkbox, currency, date, email, number, percent, phone and URL fields need the same type on both sides.
- Formula fields: Salesforce advises against mapping them, so rebuild each formula on the target object instead.
- Activities: calls, emails and tasks logged on the lead move to the new account, contact and opportunity, with 1 exception for Sales Engagement cadences.
- Read-only lead: the converted lead locks after conversion, so fix bad data before you convert, because editing it later takes an extra permission.
The practical rule: if a service agent will need it, map it onto the Account or the Opportunity during Salesforce lead conversion. That’s the only moment lead data travels on its own, so a value that misses the mapping has to be retyped by hand once the case exists. Typical candidates are the implementation contact and the go-live date the customer asked for.
How to Build the Closed Won Flow That Opens the Case

The handoff runs as 1 record-triggered flow, the standard tool for Salesforce workflow automation now that Workflow Rules have lost support, and needs only 1 custom field and 1 record type. Build them first, because the flow references both.
Add an Opportunity Lookup to Case
- The standard Case object has no field that points to an Opportunity, so create a custom lookup and give it a clear name, such as Source Opportunity.
- Add it to the case page layout for service users, so agents can click straight through to what was sold.
Give Onboarding Cases Their Own Record Type
- Create an Onboarding case record type with its own support process, which controls the Status values those cases can use.
- Assign it only to the users who should create onboarding cases, and keep everyday support cases on their existing record type.
Set the Trigger on Closed Won
- Build a record-triggered flow on Opportunity that runs when a record is updated, and choose Actions and Related Records, since a Fast Field Updates flow, which runs before the save, can only change the record that triggered it.
- Set the condition to stage equals Closed Won and pick “Only when a record is updated to meet the condition requirements,” so the flow fires once on the transition and stays quiet on later edits.
Create the Case With Everything Attached
- Use a Create Records element to set the Account, the Contact, the Source Opportunity lookup, the Onboarding record type and an Origin value such as Onboarding, plus Kickoff Date/Time if your SLA starts there.
- Set the owner to your onboarding queue, and if deals can be reopened and closed again, check for an existing onboarding case first so a second close doesn’t create a duplicate.
Add a Fault Path
- Connect a fault path to the Create Records element; it runs only when that element hits an unhandled error.
- Send the fault to an admin as an email or a task, so a failed run reaches someone the same day.
Test the flow in a sandbox by closing a dummy opportunity twice: once from an open stage, then again by editing a deal that’s already Closed Won. You should get exactly 1 onboarding case, with the account, contact and Source Opportunity already filled in.
Flow, Apex or Manual Cases: Picking the Handoff Trigger
Option | Who builds it | Duplicate-case control | Support status | Best fit |
|---|---|---|---|---|
Manual case creation | A rep or coordinator, by hand | Depends on people remembering | Supported; standard feature | Very low deal volume |
Record-triggered Flow | An admin in Flow Builder | Entry condition fires once per move into Closed Won | Supported; Salesforce’s main declarative tool | Most orgs |
Scheduled Flow | An admin, running a nightly batch | Needs a flag on the Opportunity so deals aren’t picked up twice | Supported; standard Flow feature | Teams fine with a next-day case |
Apex trigger | A developer | Handled in the trigger code | Fully supported; needs test coverage to deploy | Logic too heavy for Flow |
Workflow Rule or Process Builder | Whoever built it years ago | Depends on how it was built | No support since December 31, 2025 | Nothing new |
Salesforce’s architect decision guide calls record-triggered Flow the platform’s main declarative tool for record-triggered automation, and Apex triggers stay an option when a developer owns the logic.
Manual creation still works for a team closing a handful of deals a month, as long as 1 named person owns the step and checks it weekly. Apex earns its place when the case needs conditional data from several objects and you have a developer who’ll maintain the trigger and its tests.
A scheduled flow is the fallback when record-triggered logic would collide with other automation on Opportunity, since it runs once a night over the deals that closed that day and leaves each save untouched.
When Should the SLA Clock Start?
SLAs in Salesforce run through entitlement management, which is available only in orgs that have Service Cloud. These 4 terms do most of the work:
Entitlement: a unit of support the customer is owed, such as phone support or web support.
Entitlement process: the timeline of steps an agent has to complete on a case, built from milestones.
Milestone: one required step inside that process, like a first response, with its own criteria such as case priority.
Service contract: the support agreement itself, with contract line items for the specific products it covers.
By default, a case enters its entitlement process based on the case’s created date. You can point it at a custom date/time field instead, such as a Kickoff Date/Time that the Closed Won flow sets when it creates the case, so the clock starts when the work is meant to begin. An onboarding process might then hold a welcome call milestone due 1 business day after kickoff and a configuration review due 10 business days after it, and each one can fire success, warning and violation actions so the case owner hears about a slipping deadline before the customer does.
A case the flow creates won’t carry an entitlement unless the flow sets one. Add a Get Records step that finds the account’s active entitlement, then set the Entitlement field in Create Records, and filter that lookup on Status equals Active so an expired entitlement never gets picked. Skip that step and the entitlement process never runs on the case, so your milestone violation report stays clean for the wrong reason.
Getting the New Case to the Right Agent
The flow can drop the case straight into a queue, and if one team handles all onboarding, that’s enough. When cases arrive by email or the web instead, standard case management rules take over: Salesforce runs the active case assignment rule, and only 1 can be active at a time, while anything that matches no rule entry goes to the Default Case Owner in Support Settings.
Queues for a Single Onboarding Team
- An onboarding queue lets a small team pull cases in order, with no routing setup beyond the queue.
- Queue membership decides who sees the work, which keeps onboarding apart from everyday support.
Omni-Channel Routing When Skills Matter
- Omni-Channel routing sends work to agents automatically in 1 of 2 models: queue-based, where a routing configuration sets each queue’s priority and agent capacity, or skills-based, where the case goes to an available agent with the required skills.
- It’s available with the Service Cloud product license or with add-ons like Digital Engagement and Workforce Management.
The Summer ’26 Change
- Salesforce retired Standard Omni-Channel with the Summer ’26 release and moved orgs onto the newer version automatically.
- If your routing was configured before the upgrade, push a test onboarding case through and confirm where it lands.
Escalation Rules as a Backstop
- Escalation rules act on cases that meet criteria you set, such as an onboarding case still untouched after a set number of hours.
- Only 1 escalation rule can be active at a time, so add onboarding entries to the rule you already have.
Test the edge case before go-live: an onboarding case created at 6 p.m. on a Friday should still land with an owner who sees it Monday, so check that your entitlement business hours and escalation entries cover weekend arrivals in your support automation and case management setup.
Who Can See the Account After Sales Hands It Over?
Salesforce’s default internal org-wide defaults give both teams broad access from day 1:
Object | Default internal access | What it means after handoff |
|---|---|---|
Account | Public Read/Write | Reps and agents can both edit account details |
Contact | Controlled by Parent | Contact access follows the account |
Opportunity | Public Read Only | Agents can see the deal without editing it |
Case | Public Read/Write/Transfer | Reps can open and update the customer’s cases |
If you tighten Case access to Private, reps can lose sight of their customers’ issues when a renewal or upsell conversation needs that history. Under implicit sharing, access to an account’s cases depends on the account owner’s role and the account sharing settings, while access to a child record only gives read-only access to the parent account. If cases must stay private, a sharing rule for the sales roles that need them is easier to audit than manual shares.
Our recommendation: leave account ownership with sales and give service ownership of the cases. An account team keeps a customer success or onboarding lead in view of the account, and case teams do the same job case by case, with Read and Write, Read Only or Private roles. Opportunity teams give Read Only or Read/Write access to the deal itself, so a solutions engineer who scoped the work can stay on the record service reads.
Where the Lead-to-Case Handoff Breaks Down
Each of these comes from Salesforce’s case management and conversion documentation, and most stay invisible until a real customer case runs into them.
- Duplicate contacts blank out Email-to-Case. When 2 or more contacts share the sender’s address, Email-to-Case leaves both Contact and Account empty. Fix: turn on duplicate rules for contacts and clean up existing duplicates before go-live.
- Converted leads skip the Opportunity. Reps can finish lead conversion without creating an Opportunity, which leaves the Closed Won flow nothing to fire on. Fix: leave the “Don’t create an opportunity” option off by default in Lead Conversion Settings, and review converted leads with no opportunity.
- Converted records land on the wrong record type. Conversion assigns the converting user’s default record type and ignores subdefaults, so the record type your onboarding logic expects can be skipped. Fix: check the default record types on every profile that converts leads.
- Cadence activities stay behind. Activities from Sales Engagement cadences don’t attach to the converted records the way other lead activities do, so that outreach history never reaches service. Fix: record anything service needs as a regular activity or a field before converting.
- Agents can’t open the original lead. Viewing a converted lead takes the View and Edit Converted Leads permission, so agents without it can’t trace the original inquiry. Fix: grant it to service users who need lead history, or map that history forward at conversion.
- Old automation fires next to the new flow. Support for Workflow Rules and Process Builder ended on December 31, 2025, yet old automations still run, and one that creates cases will double up with your flow. Fix: audit legacy automation and deactivate anything that creates cases.
- A routing address overrides your rules. In Email-to-Case, a Case Owner set on the routing address bypasses your case assignment rules, and no new-case notification goes out. Fix: leave that field blank unless every case from that address should go to one owner.
- Later cases arrive without an entitlement. Entitlements don’t apply automatically to cases from Web-to-Case, Email-to-Case or Experience Cloud, so the customer’s second case has no SLA. Fix: add a flow on Case that finds the account’s active entitlement whenever the field is blank.
- Closed cases leave milestones open. Closing a case doesn’t mark its milestones complete, so a finished onboarding case can still count against your SLA numbers. Fix: add a step that sets milestone completion dates when the case closes.
- Products never become assets. Standard Sales Cloud has no built-in step that turns opportunity products into assets when a deal closes, so entitlement templates on those products never create entitlements. Fix: in the Closed Won flow, create an asset for each opportunity product, then create the entitlement that product’s template describes.
Items 1, 7 and 8 all trace back to Email-to-Case, so if email is your main support channel, fix those 3 first.
What It Costs to Build the Handoff in One Org
The cost of running Sales Cloud and Service Cloud in one org tracks project size, and these 6 drivers decide where your build lands:
Cost driver | Smaller project | Larger project |
|---|---|---|
Licenses | A handful of service agents join an org that already runs Sales Cloud. | Each region or business unit needs its own mix of Sales Cloud and Service Cloud licenses. |
Data cleanup | One merge of duplicate contacts before go-live is usually enough to keep Email-to-Case matching clean. | Years of duplicate leads and contacts need duplicate rules and merges, and old fields need remapping first. |
Handoff paths | One onboarding record type feeds one queue, giving 1 path to build and test. | Each product needs its own record type, queue or skill, and every extra path adds build and test time. |
SLA setup | One entitlement process with 2 milestones covers every onboarding case the flow creates. | Each product or support tier needs its own entitlement process, with separate business hours across time zones. |
Automation | One record-triggered flow with a fault path handles the whole handoff from Closed Won. | Complex logic adds Apex next to Flow, and legacy Workflow Rules have to be retired in the same release. |
Testing | A sandbox run of the Closed Won flow before go-live covers the risk. | Every release needs regression testing across sandboxes, because each path is another place a change can break. |
Licenses follow persona: reps need Sales Cloud, while agents who work entitlements and Omni-Channel routing need Service Cloud, plus the Service Cloud User feature license for the Service Console. Editions and list prices change, so confirm current pricing, what your edition includes and whether one license covers both clouds for one user with your account executive.
Implementation cost follows the same drivers, so budget the build separately from licenses and scope it against the rows that match your org.
A Pre-Launch Checklist for the Sales-to-Service Handoff
Run this list in a sandbox first, then again in production before the first real deal closes. If the handoff is part of a bigger rollout, our guide to implementing Salesforce CRM covers the wider plan.
Data and Conversion
☐ Every field service needs is mapped from Lead to the Account or Opportunity
☐ Duplicate rules are active on Contacts, and existing duplicates are merged
☐ “Don’t create an opportunity” is off by default in Lead Conversion Settings
☐ Default record types are correct on every profile that converts leads
Automation
☐ The Source Opportunity lookup exists on Case and sits on the service page layout
☐ The Onboarding record type has its own support process
☐ The Closed Won flow uses “Only when a record is updated to meet the condition requirements”
☐ A fault path alerts an admin, and legacy rules that create cases are switched off
SLA and Routing
☐ The flow sets the Entitlement field, and later email and web cases get one too
☐ The entitlement process starts from the date you chose, either the created date or Kickoff Date/Time
☐ Milestones get completion dates when cases close
☐ The onboarding queue or Omni-Channel route was tested with a live case
Access
☐ Reps keep visibility through account teams if Case access is Private
☐ Service users who need lead history have View and Edit Converted Leads
☐ Opportunity team members who scoped the work can still read the deal
If any item fails in production, deactivate the Closed Won flow until it’s fixed, because a half-built handoff creates cases that agents learn to ignore.
How to Tell If Your Handoff Is Working

Track these 6 reports to see whether the sales-to-service handoff holds up after launch. The first 2 depend on the Source Opportunity lookup, since nothing else ties a case back to its deal.
Metric | How to build it | What a bad number means |
|---|---|---|
Close-to-case lag | Formula on Case: created date minus the source opportunity’s close date | The flow isn’t firing, or reps update the stage late |
Closed Won deals with no case | Opportunity report on Closed Won, cross-filtered for no related onboarding case | The flow failed or skipped a deal |
Cases with a blank Contact | Case report filtered to an empty Contact | Duplicate contacts are breaking Email-to-Case matching |
Milestone violations | Report on onboarding case milestones marked as violated | The SLA start date or the staffing plan is off |
Flow fault alerts | Count of fault emails or tasks per month | Data or permissions are blocking case creation |
Time to first agent touch | Case history report on the first Status change of onboarding cases, grouped by queue | The queue or Omni-Channel route isn’t reaching anyone |
Review these monthly, and treat any Closed Won deal without an onboarding case as a bug to fix that week. Whoever owns the org after go-live should own this review too, and any change to Opportunity stages, case record types or the onboarding queue is a reason to run it early.
One Team for Both Sides of the Handoff
The lead-to-case handoff breaks when sales and service get configured by teams who never compare notes. HyphenX Solutions has 250+ Salesforce professionals across Sales Cloud and Service Cloud, so the people who map your lead conversion fields also build the Closed Won flow, entitlements and routing that pick up the customer afterward. The handoff gets designed once, end to end. Meet the team.
Explore Our Salesforce Case Study
To see how HyphenX cleans up data at the front of this chain, read this case study on the lead side of the handoff.
From Swivel-Chair Prospecting to Single-Click Pipeline
A B2B SaaS company running structured outbound sales was prospecting across Apollo, Lusha and Hunter, none of them connected to Salesforce, so reps copied records in by hand and checked for duplicates by eye. HyphenX built a single-click identify-and-insert action inside Sales Cloud that resolves a person or company across all 3 providers, verifies the email through Hunter before anything is written, checks existing records in real time and creates or updates the Lead, Contact and Account with source attribution.
Key takeaway: The lead-to-case handoff starts long before Closed Won, and stopping duplicate contacts at the moment they enter Salesforce is what later lets Email-to-Case match a customer’s email to the right contact.
Read the full case study: From Swivel-Chair Prospecting to Single-Click Pipeline
FAQs
Does lead conversion create a case in Salesforce?
No. Lead conversion creates an Account and Contact, plus an optional Opportunity. Opening a case at Closed Won takes automation, usually a record-triggered flow on Opportunity.
Can Sales Cloud users see and create cases?
Sales reps can use cases to track issues during the sales process, and users with Create permission on cases can open them. Entitlements and Omni-Channel routing need Service Cloud, and the Service Console needs the Service Cloud User feature license.
Do Sales Cloud and Service Cloud need an integration in one org?
No. In one org, both products read and write the same Account and Contact records in a single database. You only need integration work when the clouds sit in separate orgs or connect to systems outside Salesforce.
What does the Service Cloud User feature license do?
It gives a user access to the Service Console, the workspace agents use to handle cases. An admin with the Manage Internal Users permission assigns it by selecting Service Cloud User on the user record.
Can a case link directly to an opportunity?
Not through a standard field. The Case object’s standard lookups include Account, Contact, Asset and Entitlement, but no Opportunity. Add a custom lookup on Case and have your Closed Won flow fill it in.
When should the SLA start on an onboarding case?
An entitlement process starts from the case’s created date by default, and it can use a custom date/time field instead. For onboarding, a Kickoff Date/Time field usually fits better, so the clock starts when the work is scheduled to begin.
How do I stop the flow from creating duplicate onboarding cases?
Set the entry condition to “Only when a record is updated to meet the condition requirements,” so the flow fires once when the stage moves to Closed Won. If deals can reopen and close again, check for an existing onboarding case first.
Why does Email-to-Case leave Contact and Account blank?
Email-to-Case matches the sender’s email address to a contact. If 2 or more contacts share that address, it leaves both fields blank. If no contact matches, it stores the sender in Web Email and Web Name.
Do I need Omni-Channel to route onboarding cases?
No. A queue set directly by the flow, or a case assignment rule, handles routing as part of standard case management. Omni-Channel routing helps at higher volume and needs the Service Cloud product license or a qualifying add-on.
Can I still use Workflow Rules or Process Builder for the handoff?
They still run, and Salesforce ended support for both on December 31, 2025, so they get no fixes. Build new handoff automation in Flow, and retire any old rule that creates cases.
Should the sales rep stay account owner after handoff?
At HyphenX we recommend leaving account ownership with sales and giving service ownership of the cases. An account team keeps the onboarding or customer success lead on the account, and case teams handle access case by case.
Do opportunity products turn into assets automatically?
No. Standard Sales Cloud has no built-in step that converts opportunity products into assets at Closed Won. Create them, and each product’s entitlement, in your Closed Won flow.
What’s the difference between an entitlement and a service contract?
A service contract is the support agreement with the customer, with line items for the products it covers. An entitlement is a specific unit of support the customer can receive, such as phone support, and it drives the SLA on a case.
How much does it cost to run Sales Cloud and Service Cloud in one org?
It depends on project size. License costs grow with the number of reps and agents on each cloud, and build costs grow with the number of onboarding paths and the data cleanup needed first.
Is it Sales Cloud or Agentforce Sales now?
Salesforce’s product and pricing pages use Sales Cloud and Service Cloud. Many help articles still say Agentforce Sales and Agentforce Service from the 2025 rebrand, so you’ll see both names in documentation for now.