CRM Hosting for Beginners: Self-Hosted vs Cloud CRM Guide | Pick Hosting

A client called me last year after their self-hosted SuiteCRM instance went down for 14 hours during a product launch. Their VPS had run out of disk space because nobody configured log rotation. They lost an estimated $23,000 in leads that weekend. The fix took 8 minutes.

That’s the reality of CRM hosting decisions. The choice between self-hosted and cloud isn’t about features or philosophy — it’s about what you’re willing to maintain, what you can afford, and where your data needs to live.

What CRM Hosting Actually Means

A CRM (Customer Relationship Management) system stores every interaction your business has with leads and customers. Contact details, email history, deal stages, support tickets, notes from phone calls — all of it.

That data has to live somewhere. “CRM hosting” is just the question of where.

You’ve got three real options:

Cloud/SaaS CRM — The vendor hosts everything. You log in through a browser. HubSpot, Salesforce, and Pipedrive all work this way.
Self-hosted CRM — You install the CRM software on your own server or VPS. SuiteCRM, vTiger, and EspoCRM are common choices.
Managed hosting — A hosting provider runs the server, and you install the CRM on it. It’s a middle ground where you own the data but someone else handles uptime.

Most businesses under 50 employees should start with a cloud CRM. I’ll explain why, and I’ll tell you exactly when self-hosting makes sense instead.

Cloud CRM: What You’re Actually Paying For

Cloud CRMs charge per user per month. That price covers hosting, security patches, backups, uptime monitoring, and usually some level of support. You don’t think about servers. You sign up and start adding contacts.

Here’s what the real costs look like in 2026:

CRM	Free Tier	Starter	Mid-Tier	Enterprise
HubSpot	Yes (up to 1M contacts)	$20/user/mo	$100/user/mo	$150/user/mo
Salesforce	No	$25/user/mo	$100/user/mo	$300/user/mo
Pipedrive	No	$14/user/mo	$49/user/mo	$99/user/mo
Zoho CRM	Yes (3 users)	$14/user/mo	$40/user/mo	$52/user/mo

Those starter prices look reasonable until you do the math for a growing team. A 15-person sales team on Salesforce’s mid-tier plan costs $18,000/year. On HubSpot’s Sales Hub Professional, you’re at $18,000/year too. And those prices tend to climb — Salesforce raised its prices 9% in 2023 and hasn’t dropped them since.

The Hidden Costs of Cloud CRMs

The per-seat price is the visible cost. Here’s what catches people:

API limits. HubSpot’s free tier gives you 100 API calls per 10 seconds. If you’re syncing with your website, email platform, and accounting software, you can hit that fast. Upgrading to Operations Hub just for higher API limits costs $800/month.

Storage limits. Salesforce gives you 10GB of file storage on most plans, plus 20MB per user. If your team attaches proposals and contracts to deals, you’ll blow through that in months. Additional storage is $125/month per 500MB. Yes, really.

Integration add-ons. Want to connect Salesforce to your billing system? That’s often a separate connector app at $50-200/month. HubSpot’s App Marketplace has free integrations, but the powerful ones (like the Salesforce sync) require paid tiers.

Export difficulty. This one burns people. Try exporting your full HubSpot database — including email history, deal associations, and custom properties — into a format another CRM can actually import. It’s technically possible. It’s practically a 40-hour project.

When Cloud CRM is the Right Call

Cloud CRM makes sense when:

Your team is under 20 people
You don’t have a dedicated sysadmin or DevOps person
You need to be operational in days, not weeks
Compliance doesn’t require data residency in a specific location
You’d rather pay predictable monthly costs than manage infrastructure

For most small businesses reading this, that’s you. Start with HubSpot’s free tier and only upgrade when you genuinely hit a limitation. Don’t let a sales rep convince you that you need Marketing Hub Enterprise on day one.

Self-Hosted CRM: Real Server Requirements

Self-hosting means you install CRM software on infrastructure you control. The software itself is usually free and open source. You pay for the server, and you handle everything else.

The most common self-hosted CRMs in 2026:

SuiteCRM — Fork of SugarCRM Community Edition. PHP/MySQL. The most mature option with the largest community.
EspoCRM — Modern PHP-based CRM with a cleaner UI than SuiteCRM. Good REST API.
Twenty — Open-source CRM built on Node.js/PostgreSQL. Newer, but gaining traction fast with developer-focused teams.
ERPNext CRM — Part of the ERPNext ecosystem. Python/MariaDB. Best if you also need invoicing and inventory.

Actual Server Specs You Need

I’ve deployed SuiteCRM and EspoCRM on everything from shared hosting to dedicated servers. Here’s what actually works:

For 1-5 users (small team):

2 vCPU, 4GB RAM, 40GB SSD
Cost: $20-40/month on most VPS providers
Example: Hetzner CX31 or DigitalOcean Droplet

For 5-25 users (growing business):

4 vCPU, 8GB RAM, 80GB SSD
Separate database server recommended
Cost: $40-80/month
Add Redis for caching — it cuts page load times by 40-60%

For 25-100 users (mid-market):

8 vCPU, 16GB RAM, 160GB SSD
Dedicated database server (4 vCPU, 8GB RAM minimum)
Load balancer if you need high availability
Cost: $150-300/month total

Compare that mid-market scenario to cloud CRM pricing. 50 users on Salesforce Essentials costs $15,000/year. 50 users on a self-hosted SuiteCRM instance costs maybe $3,600/year in hosting. The software is free.

That’s an $11,400/year difference. Over five years, you’re looking at $57,000 saved. But only if you can actually maintain it.

The Maintenance Tax Nobody Talks About

Here’s where the self-hosting dream meets reality. That $57,000 in savings evaporates if you’re paying a contractor $150/hour to manage your CRM server.

Monthly maintenance tasks for a self-hosted CRM:

Security patches — PHP, MySQL/PostgreSQL, and the OS all need updates. SuiteCRM had 3 security advisories in 2025. Miss one and you’re exposed.
Backups — Daily automated backups with offsite storage. Test restores quarterly. I’ve seen backups that ran for two years but were silently corrupted and never verified.
SSL certificate renewal — Let’s Encrypt makes this free, but certbot still fails sometimes. Set up monitoring.
Disk space monitoring — The problem that killed my client’s launch. CRM databases grow faster than you’d expect. A 20-user SuiteCRM instance can generate 5-10GB of database growth per year.
Performance tuning — Slow CRM means low adoption. If your search takes 4 seconds, your sales team will stop using the CRM. Period.

Budget 4-8 hours per month for maintenance. If you’re doing it yourself and your time is worth $75/hour, that’s $3,600-7,200/year. If you’re hiring someone, double it.

Your concrete next step: Before choosing self-hosted, honestly answer this question: Who will respond at 2 AM when the database crashes during your busiest sales week? If you don’t have an answer, go cloud.

The Middle Ground: Managed Hosting for CRM

Managed hosting providers handle the server — updates, security, backups, uptime — while you install and configure the CRM application. You get more control than cloud CRM without the full operational burden.

This works especially well when:

You want to run SuiteCRM or EspoCRM but don’t want to manage Linux servers
Your data needs to stay in a specific country (GDPR, data sovereignty requirements)
You’ve outgrown cloud CRM pricing but aren’t ready to hire a sysadmin

Look for hosting providers that offer managed VPS or managed cloud hosting with root access. You’ll need to be able to install PHP, configure MySQL, and set up cron jobs for scheduled CRM tasks.

Some things to check before you pick a managed host:

Do they include automated backups? How many days of retention? Can you download them?
What’s their actual response time? Ask for SLA numbers, not marketing promises. Under 15 minutes for critical issues is the standard worth paying for.
Can you scale the server without migration? Adding RAM and CPU should take minutes, not a weekend of downtime.
Where are their data centers? This matters for both performance and compliance.

Check our hosting comparison pages to evaluate providers side-by-side on these specific criteria.

CRM Database Hosting: MySQL vs PostgreSQL

This is one of those decisions that seems minor at setup and becomes a major headache two years later. Most PHP-based CRMs (SuiteCRM, EspoCRM, vTiger) use MySQL or MariaDB. Newer CRMs like Twenty use PostgreSQL.

Here’s what matters practically:

MySQL/MariaDB is easier to find cheap hosting for, has more tutorials available, and works with every PHP CRM out of the box. For teams under 50 users, it handles CRM workloads perfectly fine.

PostgreSQL handles complex queries better, has superior full-text search, and scales more gracefully with large datasets. If you have over 500,000 contacts or need heavy custom reporting, PostgreSQL is worth the slightly steeper learning curve.

Database Performance Tips That Actually Matter

I’ve tuned CRM databases for dozens of clients. These three changes consistently produce the biggest improvements:

1. Increase innodb_buffer_pool_size to 70% of available RAM. On a 4GB server dedicated to the CRM database, set this to 2.8GB. Default MySQL configurations are designed for shared environments and leave most of your RAM unused.

2. Add indexes to custom fields you search on. Every custom field you’ve added to your CRM that appears in a search or report filter needs a database index. Without one, every search scans the entire table. I’ve seen searches drop from 8 seconds to 0.3 seconds by adding a single index.

3. Schedule off-peak database maintenance. Run OPTIMIZE TABLE on your largest tables weekly, during off-hours. CRM tables with frequent updates develop fragmentation that degrades performance over time.

Data Migration: Moving CRM Data Between Hosts

At some point, you’ll need to move your CRM. Maybe you’ve outgrown your VPS, maybe you’re switching from cloud to self-hosted, or maybe you’re consolidating from two CRMs into one.

Here’s the process I follow for every CRM migration:

Step 1: Full Data Audit

Before touching anything, document what you have:

Total number of contacts, companies, deals, and activities
Custom fields and their data types
Integrations that push or pull data
Workflow automations and their triggers
User roles and permissions

I use a spreadsheet with one tab per object type. It takes 2-4 hours for a typical small business CRM. Skip this step and you’ll spend 20 hours fixing data inconsistencies after migration.

Step 2: Export and Clean

Export everything you can. CSV is the universal format — every CRM can export to it and import from it. But CSVs lose relationships between records. Export contacts, then deals, then activities, and keep track of the ID fields that connect them.

Clean the data before importing. Every CRM migration is an opportunity to:

Remove duplicate contacts (most CRMs accumulate 15-25% duplicates)
Archive deals older than 2 years that nobody’s touched
Standardize fields (is it “US,” “USA,” “United States,” or “U.S.”?)
Delete test records and spam contacts

Step 3: Test Migration

Never import directly into production. Set up a staging instance of your target CRM with identical configuration. Import your cleaned data there first. Verify record counts, spot-check 50 random records, and test that relationships between contacts and deals survived.

I’ve done over 40 CRM migrations. Every single one had at least one data mapping issue that only showed up during the test import. Every. Single. One.

Step 4: Plan the Cutover

Pick a weekend. Communicate the timeline to your team. Freeze data entry in the old CRM on Friday evening. Run the final export, import into the new system, and verify. Monday morning, everyone logs into the new CRM.

Your concrete next step: If you’re planning a migration, start the data audit from Step 1 this week. It’ll tell you how big the project really is before you commit to a timeline.

CRM Hosting Security Basics

CRM databases are high-value targets. They contain names, email addresses, phone numbers, deal values, and sometimes payment information. A breach is both a legal liability and a trust-destroying event.

Non-negotiable security measures for any CRM setup:

Encrypt data in transit. SSL/TLS everywhere. No exceptions. If your CRM is accessible over HTTP, fix that today.

Encrypt data at rest. Cloud CRMs handle this automatically. For self-hosted, enable full-disk encryption on your server and make sure your database backups are encrypted too.

Enforce two-factor authentication. Every CRM user, including admins. HubSpot and Salesforce both support 2FA natively. For self-hosted CRMs, configure TOTP through your authentication layer.

Restrict database access. Your CRM database should only accept connections from the application server, not from the public internet. I audit client servers and find publicly accessible MySQL instances roughly 30% of the time. That’s terrifying.

Log and monitor access. Know who’s logging in, from where, and what they’re exporting. Set up alerts for bulk data exports — that’s often the first sign of a compromised account.

How to Choose: A Decision Framework

Forget feature matrices and marketing buzzwords. Answer these five questions:

1. How many users do you have right now? Under 5: Cloud CRM free tier. Start with HubSpot. 5-25: Cloud CRM paid tier or self-hosted, depending on your team’s technical ability. Over 25: Do the math on cloud vs self-hosted with real numbers from your vendor quotes.

2. Do you have someone who can manage a Linux server? No → Cloud CRM or managed hosting. Yes → Self-hosted is an option.

3. Where does your data need to live? If regulations require specific geographic data residency, self-hosted or managed hosting in the right region. Most cloud CRMs let you choose a data region, but verify this — some don’t for lower tiers.

4. What’s your actual budget? Include everything: license fees, hosting costs, maintenance hours, integration costs. Don’t compare monthly software fees against annual server costs.

5. How fast do you need to be operational? This week → Cloud CRM. This month → Managed hosting with a pre-configured CRM. This quarter → Self-hosted with proper planning.

Common Mistakes I See Over and Over

Buying too much CRM too early. A 3-person startup doesn’t need Salesforce Enterprise. Start with the smallest plan that works and upgrade when a real limitation appears, not when a theoretical one might.

Ignoring adoption in favor of features. The best CRM is the one your team actually uses. I’ve seen $200,000 Salesforce implementations abandoned because the UI was too complex for a 10-person sales team. They switched to Pipedrive and their data entry compliance went from 40% to 92%.

Not testing email deliverability from self-hosted CRMs. Self-hosted CRMs send transactional emails (deal notifications, task reminders) from your server’s IP address. If that IP has a poor reputation, those emails land in spam. Always use a dedicated email service like Postmark or Amazon SES for outbound CRM emails.

Skipping the backup verification. Running backups is not the same as having backups. Schedule a quarterly restore test. Boot up a fresh server, restore your backup, and confirm the data is complete and accessible. It takes an hour. It could save your business.

Treating CRM hosting as a set-and-forget decision. Your needs will change. A startup that’s fine on HubSpot’s free tier today might need self-hosted infrastructure in two years when they hit 200,000 contacts and the API limits start throttling their integrations. Plan for eventual migration by keeping your data clean and well-documented.

Where to Go From Here

Pick the CRM hosting model that matches your team’s technical ability and budget — not the one with the flashiest marketing. Start small, keep your data clean, and make sure someone’s actually responsible for backups.

If you’re comparing specific hosting providers for a self-hosted CRM deployment, our hosting comparison tools let you filter by server specs, data center location, and managed service options. For CRM-specific recommendations, check out our reviews of HubSpot and Salesforce to understand what you’re getting (and what you’re giving up) with each platform.

Disclosure: Some links on this page are affiliate links. We may earn a commission if you make a purchase, at no extra cost to you. This helps us keep the site running and produce quality content.