Requirements
PrimoCRM runs on standard WordPress hosting. This page lists what it needs and the settings that matter most for sending email and importing large lists.
Minimum requirements
Section titled “Minimum requirements”| Component | Minimum | Recommended |
|---|---|---|
| WordPress | 5.8 | Latest |
| PHP | 7.4 | 8.1 or newer |
| MySQL / MariaDB | MySQL 5.7 / MariaDB 10.3 | MySQL 8 / MariaDB 10.6 |
| WP-Cron | Enabled | A real system cron (see below) |
The current PrimoCRM version is 1.0.0.
WP-Cron and background work
Section titled “WP-Cron and background work”PrimoCRM does all heavy work in the background: campaign sends, sequence drips, automation steps, and CSV imports are processed by self-rescheduling cron workers so they never block a page request or time out.
Because of this, reliable cron is important. On a busy site the default WordPress pseudo-cron (which only runs when someone visits a page) is fine. On a low-traffic site, sends can stall between visits, so a real server cron is strongly recommended. The full setup, including how PrimoCRM’s workers are scheduled and how to configure a real cron on cPanel, a VPS, or a shared host, is covered in Cron and Background Processing.
PHP limits for importing
Section titled “PHP limits for importing”Large CSV imports are limited by two PHP settings. If a file is larger than
post_max_size, PHP discards it before PrimoCRM ever sees it, and the importer
reports that the upload exceeded the server limit.
| Setting | Suggested for large imports |
|---|---|
upload_max_filesize |
64M |
post_max_size |
64M |
max_execution_time |
300 |
memory_limit |
256M |
Raise these in php.ini, in a hosting control panel, or ask your host. See
Importing Contacts for the full explanation.
Sending email
Section titled “Sending email”Out of the box PrimoCRM sends through the WordPress mailer (wp_mail). For real
volume and better inbox placement, configure SMTP or, with Pro, a dedicated email
service provider. See Sending and Deliverability.