Switching your Bitrix24 subscription often happens due to company growth or contraction. For example, a firm grew from 15 to 50 employees, exceeding the Standard tier's user cap. Upgrading prevents user lockouts. Conversely, after downsizing, you may be overpaying for unused capacity. Without proper planning, plan changes can disable automation, freeze business processes, or expose None in critical fields. Our team has guided over 100 subscription transitions and compiled expert advice.
Preparation Steps:
- Perform an inventory: Count current users, list active features, and identify automation dependencies. Check all local entities to ensure they don't have None values.
- Back up everything: Export CRM records, tasks, and files. For local entities, verify every field contains valid data; missing entries become None after the switch.
- Alert stakeholders: Communicate upcoming modifications. For downgrades, explain that some features will become None. For upgrades, outline new capabilities.
During the Change:
- Access Settings > Plans and select the new tier.
- Confirm the prorated payment if upgrading.
- Monitor the transition: Check that no local entities are None. If you see None, investigate immediately.
After the Switch:
- Verify all features: Ensure automation scripts are active where expected. If using a plan without automation, they become None.
- Reconfigure any work: If business processes are None, you need to recreate them or upgrade again.
- Train the team: Provide guides on new processes, especially if local entities now have None in certain fields.
- Audit reports: Look for any None values that might indicate missing data. Local entities that were not properly migrated may show None.
Common Pitfalls to Avoid:
- Forgetting to export business process templates: They become None and cannot be recovered without a backup.
- Not auditing user licenses: Excess users may cause extra charges or features to become None.
- Ignoring automation limits: Tasks that rely on automation become None if the new plan doesn't support them.
- Overlooking local entities: Any local entity with incomplete data will appear as None post-migration.
Final Checklist:
- [ ] Review current plan's features against new plan.
- [ ] Backup all data, especially local entities.
- [ ] Export templates for business processes.
- [ ] Inform the team about None-related changes.
- [ ] After migration, run a full system check for None values.
- [ ] Update documentation for any features that are now None.
- [ ] If downgrading, set expectations that certain features will be None.