Owning your agent desk instead of renewing Salesforce Service Cloud tends to pay off once you license well over a hundred agents on Core or a higher edition, your case handling is specific to how you sell and support, and engineers are ready to run it; under a few dozen agents on standard email and phone work, renew. Compare agents × edition list price × 36 months with engineers × build months × $7,000 plus a yearly run cost. Often the smartest move is partial: Salesforce remains your CRM system of record while the agent console, or a single case process, becomes owned code.
Salesforce sells Service Cloud by the user, per month, across five editions whose names were changed recently. If your order form predates the rename, match each line to Starter Suite, Pro Suite, Core, Advanced or Max before comparing anything. For reference, the Service Cloud pricing page shows Core at $195 per user per month, billed annually (list price checked November 21, 2026; check your contract).
List prices checked November 21, 2026. Check your contract; negotiated prices differ.
Why does the number climb at renewal? Licenses follow people: supervisors, escalation specialists and back-office staff who touch cases each need one, and the agent floor usually expands as your customer base does. Messaging sits on top, so a Core agent with Enhanced Messaging lists at $270 a month rather than $195. And editions step steeply: Advanced is $395, roughly double Core, while AI capacity arrives as Agentforce purchases or Flex Credits instead of inside the seat. Budget for the edition next year's roadmap requires, which is not always the one you run now.
Plenty of support organizations should simply renew. Service Cloud is a mature product that shares one platform with the Salesforce CRM. Owning makes sense only for the slice you really use, at a head count where that slice is expensive.
That hybrid is worth pricing first. Sales keeps its account history, nobody re-platforms the org, and the per-user line shrinks exactly where heads are concentrated: the agent floor. You do take on an integration whose API budget becomes a design constraint, covered below. People who already know your org's metadata shorten this considerably; see hire Salesforce developers.
Renting for three years costs agents × list price × 36. Owning costs the build (engineers × months × $7,000), the Salesforce bill you still pay while building and for one overlap month, and an assumed run cost starting in that overlap month. Break-even is the first month from which owning's running total never again exceeds renting's. Inputs below: Core at $195 per user per month billed annually (list price, check your contract), every Service Cloud seat retired, and run cost assumed as a fraction of one $7,000-a-month engineer plus hosting, monitoring and channel providers. Edit these to match your org.
Core list price checked November 21, 2026 (list price, check your contract). Enhanced Messaging and other add-ons are left out, which understates the Salesforce column for many orgs. Build size and run cost are assumptions.
Twenty agents is a clear "renew": three years of owning costs $38,400 more than three years of Core, and the two lines meet only in year five. At 120 and 350 agents the monthly license is far larger than the run cost, so the build is recovered early in year two. Hybrid readers should leave the remaining CRM licenses in the owning column. Plug your own edition, discount and add-ons into the 3-year build vs buy TCO calculator, and read our build vs buy guide for the wider reasoning. We are showing where lines cross on stated inputs, not promising anyone a saving.
Catalogue case record types, queues, assignment and escalation rules, entitlements, email-to-case addresses, macros, quick actions, knowledge article types, every flow or trigger that fires on a case, and each report a manager opens weekly. Mark each used, dormant or unknown. Watch for logic shared with sales: an Account or Contact trigger may serve both teams and cannot just vanish. Gate to the next step: a signed scope of day-one behavior, later behavior and things nobody uses.
Salesforce's Data Export Service writes a zip of CSV files on a weekly or a monthly (every 29 days) schedule, depending on edition, and only users holding the "Weekly Data Export" permission can run it; by default that is System Administrator alone. Tick the boxes for images, documents, attachments and Salesforce Files. Known gaps: formula and roll-up summary fields never appear, Chatter posts and comments are cut at 1,000 characters, and sandboxes are unsupported. Large orgs get several roughly 512 MB zips, downloadable one at a time with a 60-second pause, and Salesforce deletes them 48 hours after its email (weekends excluded), so assign a person to collect them.
Scripted, repeatable pulls belong on Bulk API 2.0, which allows 10,000 query jobs and 1 TB of results in any rolling 24 hours and holds results for 7 days. Because formulas are missing from exports, recompute them in your own code. Gate to the next step: per-object row counts agree between Salesforce and staging, and you have personally verified that cases, case comments, email messages and knowledge articles arrived.
Only model what the audit kept. Typical tables: cases, case events, messages, attachments, queues, SLA clocks and knowledge, plus either local accounts and contacts or foreign keys back to Salesforce if it remains the CRM. Store the Salesforce record ID on every migrated row, indexed, for reconciliation and so links in old emails still work. Gate to the next step: the complete export loads without manual fixes, and one case's full history can be reconstructed from the new tables alone.
Whichever case type occupies the most agents gets rebuilt first: intake, routing, the console view, macros and its SLA timer. Long-tail record types stay on Salesforce for now. Routing becomes tested code, replayed against last quarter's actual cases. Our custom software development teams put this behind a feature flag so a pilot group can switch over. Gate to the next step: pilot agents resolve real customer cases start to finish without logging into Salesforce.
Connect SSO through your identity provider, then email, phone and chat, then the systems agents look things up in. Under the hybrid, the owned console talks to Salesforce all day, so plan against the REST and SOAP allocation: 100,000 calls a day as a base, plus a per-license amount, plus add-ons; no more than 25 concurrent requests running 20 seconds or longer in production; and a 10-minute timeout. SOQL over REST returns at most 2,000 records per batch, paging through nextRecordsUrl until done is true. Rather than polling, Change Data Capture can stream create, update, delete and undelete events to your copy, though only certain editions have it. Gate to the next step: replayed production-scale traffic for a full day stays comfortably within the allocation, with alerts set well before the ceiling.
Keep Salesforce live through at least one full billing month while new cases mirror into the owned console. Per case, compare assignment, first response, SLA breach and closure code. Each mismatch is a defect or a rule the audit missed. Gate to the next step: a diff report explaining every mismatch, approved by support leadership.
Freeze configuration changes, take one last Bulk API pull, repoint routing, and leave Service Cloud read-only until the renewal date. Salesforce's security, privacy and architecture document says customers may request their data within 30 days after termination, returned as CSV with attachments in native format; data then sits inactive for 120 days before deletion from production within 90 days and from backups within 180 days. Uninstalling a managed package before termination can trigger deletion of that package's data, so extract package objects first. Gate to closing the project: the archive sits in your storage, verified, with a named owner for retention.
Coding assistants handle the tedious work for our AI pod teams: mapping Salesforce fields onto columns, turning historical cases into tests, writing extraction and reconciliation scripts. A human reviews every change, and tests must pass before anything merges.
Expect a tech lead accountable for the schema and the switchover, one to three senior full-stack engineers building the console and routing, a data engineer if the org carries years of cases and files (hire data engineers), and part-time QA for routing replays and side-by-side checks. Experience administering Salesforce speeds up the audit a lot. Many teams begin with a pod of 3 to 5 senior engineers (a tech lead plus engineers), and a full pod is about seven. A narrower job, say one case type under the hybrid, can begin with a tech lead and one or two engineers.
Ryz engineers on your team start from $7,000 per month (our published range is $7,000–$15,000 per engineer per month, mostly mid-level to senior), quoted per team. Once you say go, engineers can typically start in under two weeks. Ryz engineers work on your team, reporting to your leads. When the math favors owning, scope your team.
Only above a certain agent count. Multiply agents by your edition's price by 36, then set that against engineers times build months times $7,000, plus Salesforce fees during the build and an overlap month, plus run cost. With Core at list price and our assumptions, 120 or 350 agents recover the build early in year two, while 20 agents never do within three years.
Combine the Data Export Service, which gives a full CSV archive, with Bulk API 2.0 for scripted extracts inside its daily job and result limits. Collect export zips within 48 hours of the email, not counting weekends, rebuild formula and roll-up values yourself, and accept that Chatter text is capped at 1,000 characters. After termination, you have 30 days to request a data return.
Mostly scope: how many record types and queues are in active use, how much automation sales also depends on, the volume of cases and attachments, how many channels you run, and whether Salesforce remains your CRM. Retiring a single case type under the hybrid is a fraction of the work of closing the whole service org, which is why the audit comes first.
Engineers multiplied by months multiplied by a monthly rate that starts at $7,000 per engineer, plus a run cost you choose for hosting, channel providers and a share of maintenance time. Salesforce stays on the bill until switchover, so those months count on the owning side.
Often that is the right answer. Salesforce continues as the CRM system of record for accounts, contacts and opportunities, while the agent console or one heavy case process moves to owned software that reads and writes Salesforce through its APIs. Check the integration against your API allocation before committing.
Questions we didn't answer? Email info@ryzlabs.com.
Thanks — your message has been sent. We’ll get back to you soon.
Something went wrong while sending your message. Please try again or email info@ryzlabs.com.