Daily encrypted backups, tested by restoring them
Stored off the server with restic. We keep 7 daily, 4 weekly and 6 monthly copies, plus one before every deploy and every restore.
Restore tested: same counts as the original
PolarJay CRM Hosting
Your Odoo without the license bill
We move you to Odoo Community on a dedicated server in the US. Your data and customizations come along, and every change gets tested on staging before it goes live.
For Odoo Community · Odoo 18 · LGPLv3
Last updated:
[ Your server ]Running
- Region
- US (San Francisco), DigitalOcean
- Odoo
- Odoo 18 Community
- Database
- PostgreSQL 16
- HTTPS
- Caddy, automatic
- Backups
- Daily, encrypted, off the server
- Staging
- Copy of production, email off
One server per customer
Odoo today. Other open-source CRMs on request.
- Odoo CommunityAvailable now
- EspoCRMOn request
- SuiteCRMOn request
- TwentyOn request
Odoo is a trademark of Odoo S.A. EspoCRM, SuiteCRM and Twenty are trademarks of their owners. PolarJay is not affiliated with or endorsed by them.
How a move works
How you go from Odoo Enterprise to Community
We rehearse on a copy of your real data first and only cut over once it comes out clean. These are the numbers from a real move off Odoo Enterprise on Odoo.sh.
Real migration, rehearsed on a copy of the data
What moved
- about 2,400opportunities
- about 8,300contacts
- about 11,600attachments (about 460 MB)
What we checked
- The backup restores on the new server in about 20 seconds
- Full module update: 0 errors
- 91 screens opened with 4 roles, not one error
- About 400 automated tests in the custom module
- Full rehearsal, from backup to a working CRM, in less than one working day
What stops showing up on the bill
In this move, between $4,300 and $4,700 a month in Odoo licenses and hosting.
What we audited and fixed along the way
A reporting screen that would not open, and outgoing email that had been down for months.
What you get
What runs on your server
One dedicated server per customer, defined entirely as code, so we can rebuild it exactly the same way any time.
Deploys that stop if something is off
Every production change gets a review. It is tested first on staging, a copy of production with email and scheduled jobs off, behind a password.
Staging
Password protected · no email · no scheduled jobs
Done
Production
- Stops Odoo
- Takes a backup
- Updates
- Checks health
- Rolls back only if it fails
A dedicated server in the US
DigitalOcean, San Francisco region. SOC 2 is DigitalOcean's certification for its infrastructure, not ours.
The whole server as code
Docker with Odoo, PostgreSQL 16 and Caddy, which handles HTTPS on its own.
Locked down by default
- SSH with keys only, no root login
- Firewall
- fail2ban watching sign-ins
- Database manager closed
- Staging isolated from production
- Secrets kept in a vault
- Your users' two-factor sign-in, kept as is
Outgoing email through Office 365
With OAuth, or your own SMTP.
[ Illustrative example ]
billing@yourfirm.example
Sent via Office 365 (OAuth)
Leaving Enterprise
What changes when you leave Enterprise
Odoo has no official path from Enterprise to Community. So we do it first on a copy of your real data, and we only cut over once it works.
What you keep
- Your data and its history (except what lives in Enterprise-only apps)
- Your workflows
- Your customizations (Studio work moves into your own module)
- Your users and their two-factor sign-in
What stays with Enterprise
- Enterprise-only apps you use, like full Accounting, Helpdesk, Documents or Sign
- The Studio editor
- VoIP
- The native mobile app
- Editable spreadsheets
- Cohort, map and Gantt views
- Other Enterprise apps and features: the audit shows which ones you use
How we do it
Audit
What you use from Enterprise and what leaving it means for you.
Move Studio into a module
Your Studio fields and views, in a module you own.
Rehearse
On a real copy, tested screen by screen.
Cut over
On the agreed date, with a backup before we start.
Savings
What Odoo licenses cost next to our plans
An estimate using Odoo's public US prices (Custom plan, yearly billing, list price), checked on October 10, 2026. If you are on Odoo.sh, its hosting is billed on top, so the gap is bigger. Migration is quoted separately and not included.
10 users
[ Estimate ]- Odoo licenses
- $610 a month
- PolarJay Essentials
- $1,500 a month
At this size, Odoo's license alone costs less than our plans.
50 users
[ Estimate ]- Odoo licenses
- $3,050 a month
- PolarJay Business
- $2,500 a month
- Difference per year
- $6,600
100 users
[ Estimate ]- Odoo licenses
- $6,100 a month
- PolarJay Enterprise
- $3,000 a month
- Difference per year
- $37,200
Try it with your team size
[ Estimate ]People who sign in to Odoo, not portal users or customers.
Odoo licenses
$3,050
50 users × $61 a month
PolarJay Business
$2,500
a month
Difference per year
$6,600
In the first year Odoo charges initial users $49 per user; after that, $61. Paying month to month, $76.20.
Plans
One monthly price for the whole server
In US dollars, with no per-user fees. Taxes extra.
Essentials
$1,500a month
Small teams that want their Odoo looked after properly.
- Up to about 25 internal users
- Dedicated server in the US
- Production and staging
- Daily encrypted off-server backups
- Tested restore: every quarter
- 4 hours a month of changes and admin
- Response: next business day
- Review call: every quarter
- Version upgrade: quoted separately
Business
$2,500a month
Companies that live in Odoo every day and change things often.
- Up to about 75 internal users
- Dedicated server in the US
- Production and staging
- Daily encrypted off-server backups
- Tested restore: every month
- 10 hours a month of changes and admin
- Response: within 4 business hours
- Review call: every month
- Version upgrade: quoted separately
Enterprise
$3,000a month
Larger teams or heavily customized setups.
- Up to about 150 internal users
- Dedicated server in the US
- Production and staging
- Daily encrypted off-server backups
- Tested restore: every month
- 20 hours a month of changes and admin
- Response: within 2 business hours
- Review call: every month
- Version upgrade: one planned every 12 months (custom modules quoted)
What is separate
- Month to month, taxes extra. No lock-in: 30 days' notice.
- Migration is quoted separately, after we audit your Odoo.
- Custom development is separate work from hosting.
- Support during US business hours.
- No plan includes 24/7 support, an uptime commitment or Odoo Enterprise features.
Questions
What people usually ask us
- Will I lose my data?
- Your database, attachments, users and their two-factor sign-in all move over. Data that lives in Enterprise-only apps and features stops working in Community, for example full Accounting, Helpdesk, Documents, Sign, VoIP or editable spreadsheets (Studio fields and views move into your own module). Before we migrate, we audit what you use from Enterprise and tell you which data is affected and what we do with it: export it or archive it.
- What happens to Studio?
- Studio is part of Enterprise and stays there. The fields and views you built with Studio move into a module of your own, so they keep working. What you lose is the editor itself: new changes are made by us, out of your plan hours, or by your own developer.
- What if we want to go back to Odoo.sh?
- You can. Your data is yours, and we hand you a full copy of the database and attachments whenever you ask. Going back to Enterprise means paying for Odoo licenses again.
- Where is my data?
- On a server dedicated to your company alone, at DigitalOcean in the US (San Francisco) region. Backups are encrypted and stored off that server. SOC 2 is DigitalOcean's certification for its infrastructure; PolarJay does not hold SOC 2 or HIPAA certification of its own.
- Who runs it?
- Polargate (POLARGATE S.L.), the company behind PolarJay, based in Madrid, Spain. Support during US business hours. There is no 24/7 on-call and no uptime commitment: each plan's response time is the one on its card.
- How long does it take?
- It depends on how much you have customized. On a real move with about 43 users, the full rehearsal, from the backup to a working CRM, took less than one working day. After the audit we give you a date, and we do not cut over until the rehearsal comes out clean.
- Do you host other CRMs?
- Today we offer Odoo Community. EspoCRM, SuiteCRM and Twenty, also open source, are available on request: write to us and we will look at it.
Migration plan
Get a migration plan
Tell us where your CRM runs today. We'll get back to you within one business day with next steps.