SuiteCRM 8 changes the interface and the way front-end customizations are made. For most teams, the work of an upgrade sits in the customizations added over the years, so that is where planning starts.
Key takeaways
- SuiteCRM 8 has a new interface built on Angular, with legacy modules still available underneath.
- Customizations are the real work of an upgrade, so review them first.
- Always rehearse the upgrade on a copy of your live system.
What is different in SuiteCRM 8
SuiteCRM 8 introduced a new user interface built with Angular, sitting on top of a restructured application. Much of the familiar SuiteCRM 7 functionality still runs underneath, and some screens and modules are shown through a legacy layer inside the new interface. For users, the result looks and behaves differently. For administrators and developers, the folder structure and the way front-end changes are made are different too.
Why the customizations are the real work
A clean SuiteCRM 7 instance is the easy case. The effort in most upgrades comes from what has been added over the years: custom modules, logic hooks, changed views, scheduled jobs, themes and code edited outside the custom folder.
Changes made the upgrade-safe way, inside the custom directory and through Studio and Module Builder, usually carry over with testing. Changes made directly to core files are the ones that break, and they are often undocumented.
A step-by-step approach
- Audit the current system: list custom modules, fields, hooks, workflows, integrations and any edited core files.
- Bring SuiteCRM 7 up to its latest release first, and check the PHP and database versions the target SuiteCRM 8 release requires.
- Copy production to a staging server, including the database and uploads.
- Run the upgrade on staging using the official migration steps for your version.
- Test the workflows people use every day, the integrations and the reports, with real users.
- Rebuild anything that no longer works the upgrade-safe way, and document it.
- Plan the production cutover for a quiet period, with a full backup and a rollback plan.
Things that often get missed
- Email: inbound accounts, outbound settings and scheduled jobs need checking after the move.
- Themes: SuiteCRM 7 themes do not carry over to the SuiteCRM 8 interface.
- Integrations: anything that talks to the API should be tested against the new version.
- Permissions: confirm roles and security groups still give each person the same access.
FAQ
Will our SuiteCRM 7 customizations work in SuiteCRM 8?
Many server-side customizations carry over through the legacy layer. Changes to screens and views usually need rework for the new interface.
How long will SuiteCRM 7 be supported?
Check the official SuiteCRM roadmap for current support dates and plan the upgrade well before support ends.
Can we upgrade without downtime?
Most teams rehearse on a copy, then switch over during a planned quiet window so users are not affected.
Should you upgrade now?
If SuiteCRM 7 is working and supported for your setup, there is no need to rush. But plan the move rather than wait until something forces it. A staged upgrade, with an audit first, turns a risky weekend into a predictable project.
Our SuiteCRM services include upgrade audits, rehearsed upgrades on a staging copy and rebuilding customizations the upgrade-safe way. To keep your branding through the upgrade, see Brandtint, which builds upgrade-safe themes for SuiteCRM 7 and 8. If you are moving to a different CRM instead, use our CRM migration checklist.