Salesforce, HubSpot and other enterprise SaaS platforms are easy to start with and hard to leave. The bill grows with every new user, every add-on and every consultant hired to bend the platform around your process. At some point the company is paying a large yearly fee for a system that many of its people work around.
One of our clients reached that point with Salesforce. The licenses cost the company about $200,000 a year. We built a replacement tailored to its process for about $150,000, less than one year of what it had been paying for Salesforce, and the new system has no per-user fees.
Replacement doesn't suit every company. Check first whether it makes sense for you, then compare the costs honestly and plan the migration so that the business keeps working on switchover day.
Signs that it is time to replace Salesforce
- The bill is large and keeps growing. Per-user licenses, higher editions for a few features, paid add-ons and extra storage add up. When the yearly total reaches six figures, a custom system starts to compete on price.
- You use a small part of the platform. Many companies need accounts, contacts, deals, tasks and a few reports, and pay for a platform built for every industry at once.
- You already pay for heavy customization. Custom objects, Apex code, Flows and outside consultants are a sign that the standard product does not fit. You are building custom software anyway, inside someone else's platform and under its limits.
- People work around the system. Spreadsheets next to the CRM, data copied by hand between tools, and fields nobody fills in mean the real process lives outside the system.
- You need control over data and integrations. Specific hosting, compliance rules or deep links with internal systems are easier to deliver when you own the code and the database.
When to keep it
Replacement is usually a poor idea when the bill is small, when your teams use many standard features (marketing automation, service consoles, forecasting, a large set of AppExchange apps) or when the process changes so often that nobody can describe it yet. A smaller step can help in those cases: cut unused licenses, move some users to cheaper tools, or take expensive automations out of the platform. In our own sales automation we moved about 8,000 inactive leads out of the CRM into PostgreSQL, and the subscription stayed on a smaller plan.
Compare the full cost of both options
Put both options on one page and count everything for the same period, for example three years.
| Staying on SaaS | Custom software |
|---|---|
| Licenses for every user and edition | Discovery, design and development |
| Add-ons, extra storage, AppExchange apps | Hosting and monitoring |
| Administrators and outside consultants | Support and further development |
| Integrations and middleware | Data migration and user training |
| Price increases at renewal | A team that knows the code |
A custom system is not free after launch. You pay for servers, for fixes and updates, and for new features as the business changes. Include those costs in the comparison: the case for building holds only if the yearly running cost plus the one-off build stays well below what you would pay the vendor over the same period. In our client's case the build cost less than one year of licenses.
For rough market rates on design, development and support, see our software development cost guide.
How to replace Salesforce step by step
1. Audit what you actually use
List the objects, fields, page layouts, reports, dashboards, automations, permission rules and integrations, and check which of them people still use. Login and usage data, report run history and interviews with each team show what matters. The audit usually shrinks the scope, because many custom fields and reports have not been opened for years.
2. Design around your process
Do not copy Salesforce screen by screen. Start from how deals, orders or cases really move through the company, who works on each step and what they need to see. The new system should make the common path short. Rare cases can stay manual at first.
3. Plan the integrations
Email, calendar, telephony, accounting, the website forms and the data warehouse all have to keep working. Map every connection the current system has, including the ones built by former employees or consultants. Some links can be rebuilt in an automation tool such as self-hosted n8n, where you pay for servers rather than per task, as in our n8n project for a real estate brokerage.
4. Migrate the data in rehearsals
Export the data with Salesforce's own tools, such as Data Loader or the Bulk API, map each object and field to the new data model and clean up duplicates on the way. Run the full migration on a test environment several times before the real one, and compare record counts and a sample of records after each run. Remember attachments, notes, activity history and the links between records, which are the parts that most often go missing.
5. Switch over in stages
Move one team or one region first, run both systems in parallel for a short period, then move the rest. Keep read-only access to the old data until everyone trusts the new system. Plan the dates around your Salesforce contract: the switchover has to be finished before the renewal date, with time to spare, or you pay for another term.
6. Train people and keep improving
Short training sessions per role and a clear channel for questions work better than a long manual. The first weeks after launch bring a list of small requests. A custom system can take them in quickly.
Risks and how to reduce them
- Hidden features. Audit trails, sharing rules and scheduled reports are easy to miss until someone needs them. The usage audit and interviews in step 1 catch most of them.
- Data loss in migration. Rehearsals, automated checks and a frozen export of the old system reduce the risk.
- Low adoption. Involve the people who use the system every day in design reviews and in testing before launch, and see our guide to user acceptance testing.
- Dependence on one vendor again. Make sure you own the code, the repository and the cloud accounts, and that the system is documented well enough for another team to take over.
What you get besides the savings
The software follows your process and changes when the process changes, without waiting for a vendor's roadmap or a consultant's availability. There are no per-user fees, so adding people or giving partners access does not raise the bill. You own the data and the database, which makes reporting, AI features and integrations with internal systems simpler.
Frequently asked questions
Is it cheaper to build your own CRM than to pay for Salesforce?
It depends on the size of the bill and on how much of the platform you use. With a few users and standard needs, a subscription is cheaper. When licenses cost six figures a year and you use a small part of the platform, a custom system can pay for itself quickly: our client's replacement cost less than one year of its Salesforce licenses.
How long does it take to replace Salesforce?
The timeline is set by the number of teams and integrations and by the volume of data. Discovery and the usage audit give a realistic timeline. Plan it so that the switchover is complete before the contract renewal date.
Can we keep Salesforce for some teams?
Yes. Some companies move most users to the custom system and keep a few licenses for a team that relies on a specific feature, with the two systems connected through APIs.
Does this apply to HubSpot, Zendesk or other SaaS tools?
Yes. The same audit, cost comparison and staged migration work for any platform that charges per user and that your company has customized heavily.
Next step
Start with the numbers: what you pay per year, which features people use and what the process should look like. If you want a second opinion on the numbers, talk to us before the next renewal. EmphaSoft is a Finnish software development company headquartered in Espoo, with more than 400 projects delivered since 2010, including customer portals, SaaS platforms and business automation. Read more about what custom software development includes or tell us about your project.