Plan Transitions in Bitrix24
A company subscribed to B24 "Professional" plan two years ago for 50 people with full toolset. Team has shrunk to 20, half the features unused, yet they pay for full license. Or vice: started on "Basic," company grew to 80 people, hit limits — need upgrade but afraid to lose settings. Transitioning between plans is standard, but without preparation it causes data loss, automation shutdowns, and user conflicts.
Plan Lineup and Key Limits
Current B24 cloud plan lineup (March 2026):
| Plan | Users | Disk | CRM | Automation |
|---|---|---|---|---|
| Free | Unlimited | 5 GB | Basic, no robots | No |
| Basic | 5 | 24 GB | Full, robots | Limited |
| Standard | 50 | 100 GB | Full, business processes | Full |
| Professional | 100 | 1024 GB | Full, BI builder | Full + HR |
| Enterprise | 250-10000 | 3+ TB | Full, clustering | Full + HRMS |
Key limits when downgrading:
- User Limit. "Basic" — 5 users. If 20 active — must deactivate 15 before transition. Deactivated users lose access, but their data (tasks, deals, files) remains.
- Disk Volume. Downgrading to plan with smaller limit — files don't delete, but uploads block when exceeded.
- Business Processes. Unavailable on "Basic." All active BPs stop executing — not deleted, but "frozen."
- CRM Robots. Disabled on Free. Configured chains saved but don't trigger.
Upgrade: What Happens
On plan upgrade everything's simple — additional features become available instantly:
- Pay the difference for remaining subscription period.
- User and disk limits increase immediately.
- New tools (business processes, BI, HR) appear in menu — but need configuration.
- Data untouched: deals, tasks, contacts, files — all in place.
Catch: after upgrade, team gets tools that aren't configured. Employees start experimenting — create chaotic business processes, duplicate funnels. Recommend planning new feature rollout before upgrade.
Downgrade: Risks and Preparation
Plan downgrade has consequences. Checklist before downgrading:
1. User Audit
- List active users. Determine who stays, who deactivates.
- Transfer tasks and deals of deactivating employees to active ones. Otherwise — "orphaned" tasks without owner.
- Check deactivating users aren't work group admins, business process owners, or automation authors.
2. Feature Audit
Create table of used features and check availability on target plan:
| Feature | Current Plan | Target Plan | Status |
|---|---|---|---|
| Business Processes | Professional | Basic | Unavailable — BPs will stop |
| CRM Robots | Professional | Basic | Available with limits |
| BI Builder | Professional | Standard | Unavailable |
| Multi-funnels | Professional | Basic | Available |
| Online Documents | Professional | Basic | Available |
3. Data Audit
- File volume on Disk. If exceeds target plan limit — export archive files.
- Count of CRM records. CRM record limits depend on plan — check.
- Integration settings. Some connectors (REST apps from Marketplace) work only on specific plans.
4. Backup
Before transition — export critical data:
- CRM: export deals, contacts, companies via
crm.deal.list,crm.contact.list - Tasks: export via
tasks.task.list - Disk: download important files
- Business Processes: export BP templates (available via interface)
Billing and Financial
- Mid-period Upgrade. B24 calculates pro-rata cost for remaining period. Paid period isn't lost.
- Downgrade. New plan takes effect after current paid period ends. Early downgrade — via support, refund not guaranteed.
- Billing Period Change. Monthly subscription costs more than annual (20-30% difference). For stable use — annual is better.
- Promotions. B24 regularly offers upgrade discounts — worth waiting for planned transition.
Box to Cloud Migration (and Back)
Separate scenario — migration between cloud and box versions of B24. Not just plan change but data transfer between platforms:
- Box → Cloud. B24 provides migration tool. Transfers: CRM, tasks, disk, users. Doesn't transfer: custom modules, server handlers, core modifications.
- Cloud → Box. More complex. Data exports via API, box DB structure differs from cloud. Requires migration script development.
Transition Sequence
- Audit current plan: what's used, what's not
- Choose target plan based on real needs
- Create risk map: what features will be lost / gained
- Prepare data: deactivate users, transfer tasks, clean disk
- Backup
- Execute transition
- Verify: all features work, data in place, integrations active
- Notify team of changes and new work rules
What We Configure
- Auditing current portal usage: users, features, integrations, data volume
- Selecting optimal plan for real company needs
- Creating migration plan with risk checklist
- Deactivating users with data transfer (tasks, deals, files)
- Exporting and backing up data before transition
- Executing transition and verifying all features work
- Configuring new tools available after upgrade
- Training team: what changed, what features now available or unavailable