Where Does SuiteCRM Store Config and Data?
SuiteCRM reads config.php (plus config_override.php) for database and site settings. Records live in MySQL beside it.
Last updated
SuiteCRM centers on config.php in the web root: database credentials, site URL, and version, mostly written by the installer rather than hands. The config_override.php sibling carries durable customizations merged over the main file. Records, users, and workflows live in MySQL/MariaDB (MSSQL optional), with uploads, cache, and custom dirs in the tree.
Migration means editing two values: dbconfig host/credentials and site_url. Everything else rides along. Permissions decide installs: cache, custom, modules, themes, data, upload, and the override file must be web-writable, which is also the classic white-screen cause. Cron (the schedulers.php entry) must exist or workflows, emails, and campaigns silently stall.
Where SuiteCRM stores this, by platform
config.php (web root)
DB credentials, site URL, version. Edit directly only on moves. Keep web-writable with cache/custom/upload trees. Cron entry mandatory for schedulers and workflows.
Frequently asked questions
how do i back up suitecrm
Copy config.php and config_override.php plus a MySQL dump with the app stopped. Uploads, cache, and custom modules travel in the tree. Restore all three; the files reference table contents by id.
config.php versus config_override.php
Put deltas in config_override.php, never the main file. It merges over config.php, so upgrades and admin-panel writes cannot clobber hand settings. Only database credentials and site_url normally need direct config.php edits (on moves).
Notice an outdated path? Let us know.