Skip to content

ERP guide

Should a mid-size company stay on Salesforce or leave it?

Staying on Salesforce is the right call when your org works, your admin team is in place and the renewal still fits the budget. Leaving for a custom build fits a company that pays for edition upgrades, add-ons and consultants mainly to make Salesforce follow a process it already knows, and that wants a CRM it owns with no per-seat fee.

Updated . Researched by David Verneuille for Black Badger Software Solutions. How we rank

Leaving Salesforce or staying on it, a mid-size view. Updated November 21, 2026.
What you are comparingStaying on SalesforceA custom build
Edition and add-on chargesCharged per user by edition, from Starter Suite to Max, with paid add-ons. Sandboxes and Premier support are priced as a share of license spend, so each one grows with the bill.A one-time build scoped in writing, then running costs such as hosting. No per-seat fee and no add-on priced as a share of anything.
Renewal changesList prices rose 9% in 2023 and about 6% on Enterprise and Unlimited in 2025, and renewals price off the new list. Customers report seats can be added mid-term but not removed.No license to renew. The code and the data are yours, so there is no list price for a vendor to raise.
Admin and consultant dependenceNeeds admin staff or an outside consultant to run it, and customers report that even small changes wait on a dedicated admin.Changes go to the team that wrote the system or to any developer you hire, since you own the code.
API and storage limitsIntegrations run against daily API call limits and per-transaction limits, and customers report full API access starts at Enterprise. Storage overages have no published per-GB rate.Limits are those of the database and hosting you choose, sized to your volume, with no per-call quota sold back to you.
Getting data outRecords export, but customers report the weekly export can be a week old and leaves out customizations. Flows, Apex and layouts run only inside Salesforce and cannot move.The database is in your name and can be read, copied or moved whenever you choose, with its full history.
Fit to processThe most configurable CRM in its class, but the edition sets how far. Pro Suite lists 5 flows and 1 custom app per org.Built around your own stages, quotes and approvals, so the system follows the process instead of the process following an edition.
Forced releasesThree releases a year roll out automatically, and customers report customizations breaking after them. Workflow Rules and Process Builder reached end of support, so that automation had to be rebuilt in Flow.Changes ship when you approve them, and nothing is retired on a vendor schedule.
Time to launchAlready running, so staying takes no project.A build starts with discovery and a written scope, and the Salesforce org stays live until the new system is checked against it.

When staying on Salesforce is the right call

Stay if the org works and the people who run it are in place. A company with a capable admin, clean automation and reports the sales team trusts is getting what it pays for, and a move would spend money recreating what already runs.

Stay too if Salesforce is tied into many other systems through marketplace apps, or if a parent company or a large customer requires it. Before deciding to leave, price a cleanup of the existing org, since removing unused fields, licenses and automation can lower the renewal without any migration.

What leaving Salesforce involves

Leaving starts with an inventory of what the org does. Every object, field, flow, Apex class, report and integration gets listed with the people who use it, because the processes that run inside Salesforce do not export and have to be rebuilt somewhere else.

Next come the contract and the data. Customers report that Salesforce contracts auto-renew unless notice is given ahead of the term, so the notice date sets the plan. Export records, files and history while the license is live, check them against the source, and run both systems side by side until the new one matches.

How a custom build replaces Salesforce

A custom build replaces the parts of Salesforce your company uses, not the whole catalog. Black Badger starts from the inventory, writes a scope around your own stages, quoting rules and approvals, and builds the CRM on a database and hosting account in your name.

Black Badger does not resell, implement or administer Salesforce, so nothing rides on which way you go. If the inventory shows the org fits and needs only a cleanup, that is the advice you will get.

What a custom build involves, and how to ask about one

Questions buyers ask

How much notice does a Salesforce contract need before renewal?

Negotiation firms report notice periods of 30 to 90 days before the term ends, set contract by contract. Read your order form for the exact date, since a missed notice renews the full term.

Can a company leave Salesforce one department at a time?

Yes, and a phased move lowers the risk. Sales can move to the new system while service stays on Salesforce, as long as both share customer records through an integration. Customers report seats cannot be cut mid-term, so time each phase to the renewal date.

What should be exported before a Salesforce contract ends?

Records, files, attachments, field history and report definitions should all be exported and checked while the license is live. Customers report the paid recovery service after the fact is slow and returns CSV files to re-import by hand.

Does Black Badger implement or resell Salesforce?

No. Black Badger builds custom software and does not resell, implement or administer Salesforce, so it gains nothing from a renewal and loses nothing if the right answer is to stay.

More from this guide