CRM Platforms

Constituent Relationship Management platforms centralise organisational data about individuals, organisations, and their interactions into a unified system supporting fundraising, communications, membership, and programme delivery. These platforms maintain contact records, track engagement history, manage donation pipelines, execute segmented campaigns, and generate reports across constituent lifecycles. For mission-driven organisations, CRM platforms serve as the operational backbone connecting donor cultivation, volunteer coordination, beneficiary tracking, and stakeholder communications.

This page covers general-purpose CRM platforms suitable for constituent management across multiple organisational functions. Platforms focusing exclusively on programme delivery appear in the Case Management Systems benchmark. Dedicated fundraising and donation processing platforms with limited CRM functionality appear in the Fundraising and Donations concept page.

Assessment methodology

Tool assessments are based on official vendor documentation, published API references, release notes, and technical specifications as of 2026-01-11. Feature availability varies by product tier, deployment model, or region. Verify current capabilities directly with vendors during procurement. Community-reported information is excluded; only documented features are assessed.

Requirements taxonomy

This taxonomy defines evaluation criteria for CRM platforms. Requirements are organised by functional area and weighted by typical priority for mission-driven organisations. Adjust weights based on specific operational context.

Functional requirements

Core capabilities defining what the platform must do.

Contact and organisation management

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
F1.1	Individual contact records	Storage and management of person records with demographic, contact, and custom fields	Full: unlimited custom fields, flexible data model, merge/dedupe. Partial: limited custom fields or fixed schema. None: basic contact only.	Review data model documentation; test field creation	Essential
F1.2	Organisation records	Management of companies, foundations, government entities as distinct record types with hierarchies	Full: organisation hierarchies, affiliations, custom fields. Partial: flat organisation records. None: individuals only.	Review entity relationship documentation	Essential
F1.3	Relationship mapping	Linking contacts to organisations and to each other with typed relationships	Full: configurable relationship types, bidirectional linking, household management. Partial: fixed relationship types. None: no relationship tracking.	Review relationship model documentation	Essential
F1.4	Duplicate management	Detection and merging of duplicate records with configurable matching rules	Full: automated detection, merge preview, field-level selection, audit trail. Partial: manual merge only. None: no dedupe capability.	Review duplicate management documentation	Important
F1.5	Contact segmentation	Creation of dynamic and static contact lists based on attributes and behaviours	Full: complex query builder, saved segments, dynamic refresh. Partial: basic filtering. None: manual list creation only.	Review segmentation and list documentation	Important
F1.6	Custom field types	Support for various data types beyond text fields	Full: dates, numbers, currency, picklists, multi-select, lookups, calculated fields. Partial: limited types. None: text only.	Review custom field documentation	Important
F1.7	Record tagging and categorisation	Flexible labelling system for cross-cutting categorisation	Full: unlimited tags, tag groups, bulk tagging. Partial: limited tags per record. None: no tagging.	Review tagging documentation	Desirable
F1.8	Address standardisation	Validation and formatting of postal addresses	Full: integrated address verification, international formats. Partial: format validation only. None: freeform text.	Review address field documentation	Desirable

Interaction and activity tracking

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
F2.1	Activity timeline	Chronological record of all interactions with a contact displayed in unified view	Full: all activity types in timeline, filtering, date navigation. Partial: separate views per type. None: no unified history.	Review contact record documentation	Essential
F2.2	Manual activity logging	Recording of meetings, calls, notes, and other interactions by staff	Full: configurable activity types, rich text notes, attachments. Partial: fixed types, plain text. None: no manual logging.	Review activity creation documentation	Essential
F2.3	Email tracking	Automatic logging of email communications to contact records	Full: bidirectional email sync, thread tracking, open/click tracking. Partial: manual email logging. None: no email integration.	Review email integration documentation	Important
F2.4	Task management	Creation and assignment of follow-up tasks linked to contacts	Full: due dates, assignments, reminders, completion tracking. Partial: basic task creation. None: no task capability.	Review task management documentation	Important
F2.5	Document attachment	Linking files and documents to contact records	Full: multiple attachments per record, version control, search. Partial: limited attachments. None: no file storage.	Review attachment documentation	Important
F2.6	Communication preferences	Recording of contact preferences for channels and frequency	Full: granular channel preferences, opt-in/out tracking, preference centre. Partial: basic subscription flags. None: no preference tracking.	Review communication preference documentation	Important
F2.7	Interaction scheduling	Calendar integration for scheduling meetings and calls	Full: calendar sync, availability checking, meeting requests. Partial: manual scheduling. None: no scheduling.	Review calendar integration documentation	Desirable

Donation and opportunity management

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
F3.1	Donation recording	Entry and tracking of financial contributions with amounts, dates, and designations	Full: multiple payment types, designations, campaigns, soft credits. Partial: basic amount tracking. None: no financial records.	Review donation documentation	Essential
F3.2	Recurring donation management	Handling of regular giving programmes with schedules and projections	Full: schedule management, payment tracking, upgrade/downgrade, forecasting. Partial: basic recurring records. None: individual transactions only.	Review recurring giving documentation	Essential
F3.3	Pledge tracking	Management of pledges with instalment schedules and fulfilment tracking	Full: pledge schedules, payment matching, reminder workflows. Partial: basic pledge records. None: no pledge support.	Review pledge management documentation	Important
F3.4	Pipeline stages	Configurable stages for tracking donor cultivation and major gift solicitation	Full: custom stages, probability weighting, movement tracking. Partial: fixed stages. None: no pipeline.	Review opportunity/pipeline documentation	Important
F3.5	Soft credit allocation	Attribution of donations to multiple contacts for relationship credit	Full: flexible soft credit rules, household allocation. Partial: simple soft credits. None: single attribution only.	Review soft credit documentation	Important
F3.6	Gift acknowledgement tracking	Recording of thank-you communications and acknowledgement status	Full: automated acknowledgement workflows, letter generation. Partial: manual status tracking. None: no acknowledgement tracking.	Review acknowledgement documentation	Important
F3.7	In-kind donation tracking	Recording of non-cash contributions with valuation	Full: item tracking, fair market value, receipt generation. Partial: basic in-kind records. None: cash only.	Review in-kind documentation	Desirable
F3.8	Grant management	Tracking of grant applications, awards, and reporting requirements	Full: grant lifecycle tracking, deliverables, reporting deadlines. Partial: basic grant records. None: no grant support.	Review grant management documentation	Desirable

Campaign and communication management

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
F4.1	Campaign tracking	Organisation of activities, communications, and responses by campaign	Full: hierarchical campaigns, response attribution, ROI tracking. Partial: flat campaigns. None: no campaign structure.	Review campaign documentation	Essential
F4.2	Email campaign creation	Design and sending of bulk email communications	Full: template builder, personalisation, A/B testing, scheduling. Partial: basic bulk email. None: no email campaigns.	Review email marketing documentation	Important
F4.3	Email deliverability management	Tools for maintaining sender reputation and inbox placement	Full: bounce handling, complaint processing, warm-up tools, authentication. Partial: basic bounce removal. None: no deliverability tools.	Review deliverability documentation	Important
F4.4	Response tracking	Attribution of donations and actions to specific campaign communications	Full: automated attribution, source tracking, conversion metrics. Partial: manual attribution. None: no response tracking.	Review campaign response documentation	Important
F4.5	Communication templates	Reusable templates for emails, letters, and other communications	Full: branded templates, merge fields, conditional content. Partial: basic templates. None: no templates.	Review template documentation	Important
F4.6	Direct mail support	Generation of mailing lists and labels for postal campaigns	Full: address formatting, NCOA integration, postal optimisation. Partial: basic export for printing. None: no direct mail support.	Review direct mail documentation	Desirable
F4.7	SMS/text messaging	Sending of text messages to contacts	Full: two-way SMS, campaigns, automation triggers. Partial: basic outbound SMS. None: no SMS capability.	Review SMS documentation	Desirable
F4.8	Marketing automation	Automated multi-step communication sequences based on triggers and behaviours	Full: workflow builder, branching logic, delay steps, exit conditions. Partial: simple autoresponders. None: manual sending only.	Review automation documentation	Context-dependent

Reporting and analytics

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
F5.1	Standard reports	Pre-built reports covering common CRM metrics and activities	Full: comprehensive report library, export options. Partial: limited standard reports. None: no pre-built reports.	Review report library documentation	Essential
F5.2	Custom report builder	Creation of ad-hoc reports with field selection and filtering	Full: visual report builder, calculated fields, grouping, charts. Partial: basic query tools. None: standard reports only.	Review report builder documentation	Essential
F5.3	Dashboard creation	Configurable dashboards displaying key metrics and visualisations	Full: drag-drop dashboard builder, multiple dashboard support, sharing. Partial: fixed dashboards. None: no dashboards.	Review dashboard documentation	Important
F5.4	Giving analytics	Metrics specific to fundraising performance including LYBUNT, SYBUNT, retention	Full: donor retention analysis, giving pyramids, lifetime value. Partial: basic giving summaries. None: no giving analytics.	Review fundraising analytics documentation	Important
F5.5	Data export	Extraction of data for external analysis	Full: flexible export with field selection, scheduled exports. Partial: fixed export formats. None: no export capability.	Review export documentation	Important
F5.6	Report scheduling	Automated generation and distribution of reports	Full: scheduled generation, email distribution, multiple formats. Partial: manual scheduling. None: ad-hoc only.	Review scheduling documentation	Desirable
F5.7	Comparative analytics	Period-over-period and benchmark comparisons	Full: trend analysis, year-over-year, benchmark comparison. Partial: basic period selection. None: point-in-time only.	Review comparative reporting documentation	Desirable

Event management

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
F6.1	Event creation	Definition of events with details, capacity, and registration settings	Full: event types, sessions, capacity management, waitlists. Partial: basic event records. None: no event support.	Review event documentation	Important
F6.2	Registration management	Processing of event registrations linked to contact records	Full: online registration, multiple ticket types, registration workflows. Partial: manual registration entry. None: no registration tracking.	Review registration documentation	Important
F6.3	Event payment processing	Collection of registration fees and donations during registration	Full: integrated payment, partial payments, refunds. Partial: external payment linking. None: no payment support.	Review event payment documentation	Context-dependent
F6.4	Attendance tracking	Recording of actual attendance at events	Full: check-in tools, attendance reporting, badge printing. Partial: manual attendance entry. None: no attendance tracking.	Review attendance documentation	Desirable
F6.5	Event communications	Automated communications for event lifecycle	Full: confirmation, reminders, follow-up sequences. Partial: basic confirmations. None: manual communications.	Review event communication documentation	Desirable

Membership management

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
F7.1	Membership levels	Definition of membership tiers with benefits and pricing	Full: multiple tiers, benefits tracking, upgrade paths. Partial: single membership type. None: no membership support.	Review membership documentation	Context-dependent
F7.2	Membership lifecycle	Tracking of join dates, renewals, lapses, and reinstatements	Full: automated renewal tracking, grace periods, lapse workflows. Partial: manual status tracking. None: no lifecycle tracking.	Review membership lifecycle documentation	Context-dependent
F7.3	Renewal processing	Handling of membership renewals including reminders and payments	Full: automated reminders, renewal campaigns, payment processing. Partial: manual renewal entry. None: no renewal support.	Review renewal documentation	Context-dependent
F7.4	Member directory	Searchable directory of members for member self-service	Full: configurable directory, privacy controls, member login. Partial: admin-only directory. None: no directory.	Review directory documentation	Desirable

Technical requirements

Infrastructure, architecture, and deployment considerations.

Deployment and hosting

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
T1.1	Self-hosted deployment	Ability to deploy on organisation-controlled infrastructure	Full: complete feature parity with hosted, documented deployment. Partial: self-hosted with limitations. None: SaaS only.	Review deployment documentation	Important
T1.2	Cloud deployment options	Vendor-managed cloud deployment with regional options	Full: multiple regions including EU, documented data residency. Partial: limited regions. None: single region.	Review infrastructure documentation	Important
T1.3	Container deployment	Support for containerised deployment	Full: official Docker images, Kubernetes support. Partial: community containers. None: no container support.	Review container documentation	Desirable
T1.4	Database options	Supported database backends	Document supported databases: PostgreSQL, MySQL, MariaDB, SQL Server, others. Note version requirements.	Review system requirements	Important
T1.5	Multi-tenant architecture	Support for multiple organisations in single deployment	Full: complete tenant isolation, per-tenant customisation. Partial: limited multi-tenancy. None: single-tenant only.	Review multi-tenancy documentation	Context-dependent

Integration architecture

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
T2.1	REST API availability	Programmatic access via REST API	Full: comprehensive API covering all entities, versioned, documented. Partial: limited API coverage. None: no API.	Review API documentation completeness	Essential
T2.2	API authentication	Supported methods for API access security	Document supported methods: API keys, OAuth 2.0, OIDC, JWT	Review API security documentation	Important
T2.3	Webhook support	Event notifications pushed to external systems	Full: configurable webhooks, all events, retry logic. Partial: limited events. None: polling only.	Review webhook documentation	Important
T2.4	Bulk data operations	Support for large-scale data import/export	Full: batch APIs, streaming, async operations. Partial: limited batch size. None: record-by-record only.	Review bulk operation documentation	Important
T2.5	Pre-built integrations	Native connectors to common platforms	List available integrations; note maintenance status	Review integrations documentation	Important
T2.6	Email service integration	Connection to external email delivery services	Full: multiple ESP options, SMTP support. Partial: single provider. None: built-in only.	Review email integration documentation	Important
T2.7	Payment processor integration	Connection to payment gateways for donation processing	Full: multiple processors, PCI compliance. Partial: single provider. None: manual entry only.	Review payment integration documentation	Important

Data management

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
T3.1	Data import tools	Methods for importing data from external sources	Full: import wizards, field mapping, validation, rollback. Partial: basic CSV import. None: API only.	Review import documentation	Essential
T3.2	Data export capabilities	Extraction of data for analysis or migration	Full: flexible export, all entities, scheduled exports. Partial: limited export options. None: no bulk export.	Review export documentation	Essential
T3.3	Audit trail	Tracking of record changes with user and timestamp	Full: field-level audit, reporting, retention controls. Partial: record-level audit. None: no audit trail.	Review audit documentation	Important
T3.4	Data retention controls	Configuration of data retention and deletion policies	Full: configurable retention, automated deletion, legal holds. Partial: manual deletion only. None: no retention controls.	Review data retention documentation	Important
T3.5	Backup and recovery	Data backup and restoration capabilities	Full: automated backups, point-in-time recovery, documented procedures. Partial: manual backup. None: vendor-managed only.	Review backup documentation	Important

Security requirements

Security controls and data protection capabilities.

Authentication and access control

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
S1.1	Multi-factor authentication	MFA support on user accounts	Full: TOTP, WebAuthn, push notifications. Partial: single MFA method. None: password only.	Review authentication documentation	Essential
S1.2	Single sign-on	Federated identity via SSO	Full: SAML 2.0 and OIDC support. Partial: single protocol. None: local auth only.	Review SSO documentation	Essential
S1.3	Role-based access control	Permissions assigned by role rather than individual	Full: custom roles, granular permissions, field-level security. Partial: fixed roles. None: all-or-nothing access.	Review RBAC documentation	Essential
S1.4	Record-level permissions	Access control based on record attributes	Full: ownership-based, team-based, criteria-based access. Partial: limited record security. None: role-level only.	Review record security documentation	Important
S1.5	Password policies	Configurable password requirements	Full: complexity, expiry, history, lockout settings. Partial: basic requirements. None: no policy controls.	Review password policy documentation	Important
S1.6	Session management	Control over user session duration and security	Full: configurable timeout, concurrent session limits, forced logout. Partial: basic timeout. None: no session controls.	Review session documentation	Important

Data protection

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
S2.1	Data encryption at rest	Encryption of stored data	Full: AES-256 encryption, key management. Partial: selective encryption. None: unencrypted storage.	Review encryption documentation	Essential
S2.2	Data encryption in transit	Protection of data during transmission	Full: TLS 1.2+, certificate management. Partial: TLS with older versions. None: unencrypted transmission.	Review transport security documentation	Essential
S2.3	Field-level encryption	Encryption of sensitive individual fields	Full: selective field encryption, searchable encryption. Partial: limited field encryption. None: full-database only.	Review field encryption documentation	Important
S2.4	Data masking	Obfuscation of sensitive data for non-privileged users	Full: configurable masking rules, role-based visibility. Partial: fixed masking. None: no masking.	Review data masking documentation	Desirable
S2.5	GDPR compliance tools	Features supporting data protection regulation compliance	Full: consent management, data portability, erasure workflows, DPIAs. Partial: basic tools. None: manual processes.	Review GDPR/privacy documentation	Important

Operational requirements

Deployment, support, and ongoing management considerations.

Extensibility

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
O1.1	Custom entity creation	Ability to create new data objects beyond standard entities	Full: unlimited custom entities, relationships, UI. Partial: limited custom objects. None: standard entities only.	Review customisation documentation	Important
O1.2	Workflow automation	Creation of automated business processes	Full: visual workflow builder, triggers, conditions, actions. Partial: basic automation. None: manual processes only.	Review workflow documentation	Important
O1.3	Custom field creation	Addition of organisation-specific fields to standard entities	Full: unlimited fields, all types, UI placement. Partial: limited custom fields. None: no customisation.	Review custom field documentation	Essential
O1.4	Extension marketplace	Availability of third-party extensions and add-ons	Full: curated marketplace, quality controls. Partial: community extensions. None: no extension ecosystem.	Review marketplace/extensions	Desirable
O1.5	API for custom development	Ability to build custom functionality via API	Full: comprehensive development platform. Partial: limited development options. None: no custom development.	Review developer documentation	Important

Support and community

ID	Requirement	Description	Assessment criteria	Verification method	Typical priority
O2.1	Documentation quality	Comprehensiveness and currency of product documentation	Full: complete admin, user, and developer docs. Partial: basic documentation. None: minimal documentation.	Review documentation	Important
O2.2	Community resources	Availability of community support and resources	Full: active forums, user groups, conferences. Partial: basic community. None: vendor support only.	Review community resources	Desirable
O2.3	Training resources	Availability of learning materials	Full: certification programmes, courses, tutorials. Partial: basic training. None: documentation only.	Review training offerings	Desirable
O2.4	Professional services	Availability of implementation and customisation services	Full: vendor and partner services, nonprofit specialisation. Partial: limited services. None: self-service only.	Review services offerings	Context-dependent

Comparison matrices

Comparative assessment of evaluated platforms against the requirements taxonomy.

Rating scale

Symbol	Meaning	Definition
●	Full support	Requirement fully met with comprehensive implementation
◐	Partial support	Requirement partially met or met with limitations
○	Minimal/no support	Requirement not met or severely limited
✗	Not applicable	Requirement not relevant to this platform’s design
-	Not assessed	Insufficient documentation to assess

Platform overview

Platform	Type	Licence	Current version	Primary focus	Nonprofit programme
CiviCRM	FOSS	AGPL-3.0	6.10.0	Constituent management for nonprofits	N/A (free)
SuiteCRM	FOSS	AGPL-3.0	8.9.0	General-purpose CRM	N/A (free)
Dolibarr	FOSS	GPL-3.0+	22.0.4	ERP+CRM combined	N/A (free)
EspoCRM	FOSS	AGPL-3.0	9.1.8	General-purpose CRM	N/A (free)
HubSpot CRM	Commercial	Proprietary	Continuous	Marketing and sales	40% discount
Salesforce Nonprofit Cloud	Commercial	Proprietary	Spring ‘26 (v66)	Enterprise nonprofits	Donated licences available
Microsoft Dynamics 365	Commercial	Proprietary	Dataverse	Enterprise CRM/ERP	Discounted pricing
Bloomerang	Commercial	Proprietary	Continuous	Donor management	N/A (nonprofit-focused)

Functional capability matrix

Contact and organisation management (F1)

Requirement	CiviCRM	SuiteCRM	Dolibarr	EspoCRM	HubSpot	Salesforce	Dynamics 365	Bloomerang
F1.1 Individual records	●	●	●	●	●	●	●	●
F1.2 Organisation records	●	●	●	●	●	●	●	●
F1.3 Relationship mapping	●	◐	◐	●	◐	●	●	●
F1.4 Duplicate management	●	●	◐	●	●	●	●	●
F1.5 Contact segmentation	●	●	◐	●	●	●	●	●
F1.6 Custom field types	●	●	●	●	●	●	●	●
F1.7 Record tagging	●	●	●	●	●	●	●	●
F1.8 Address standardisation	◐	○	○	○	●	●	●	◐

Notes:

CiviCRM: Relationship mapping includes household/employer relationships and flexible relationship types. Address standardisation requires extension.
SuiteCRM: Relationships limited to account-contact linking; custom relationship types require development.
Dolibarr: Primarily ERP-focused; contact segmentation basic compared to CRM-focused platforms.
EspoCRM: Metadata-driven architecture enables extensive relationship customisation.
HubSpot: Free tier limits custom fields; relationship mapping basic without Sales Hub.
Salesforce: Nonprofit Cloud includes household management via PartyRelationshipGroup.
Dynamics 365: Dataverse provides full data model customisation; Common Data Model for Nonprofits deprecated December 2025.
Bloomerang: Purpose-built for constituent management with household allocation and duplicate detection.

Interaction and activity tracking (F2)

Requirement	CiviCRM	SuiteCRM	Dolibarr	EspoCRM	HubSpot	Salesforce	Dynamics 365	Bloomerang
F2.1 Activity timeline	●	●	●	●	●	●	●	●
F2.2 Manual activity logging	●	●	●	●	●	●	●	●
F2.3 Email tracking	●	◐	◐	●	●	●	●	◐
F2.4 Task management	●	●	●	●	●	●	●	●
F2.5 Document attachment	●	●	●	●	●	●	●	●
F2.6 Communication preferences	●	◐	○	◐	●	●	●	●
F2.7 Interaction scheduling	●	●	●	●	●	●	●	◐

Notes:

CiviCRM: CiviMail provides full email tracking; standalone mode (v6.0+) simplifies deployment.
SuiteCRM: Email integration requires configuration; email tracking available but limited.
Dolibarr: Email integration basic; focus on ERP activities.
EspoCRM: Built-in email client with full tracking; calendar integration native.
HubSpot: Email tracking comprehensive in free tier; scheduling requires Sales Hub.
Salesforce: Activity capture automatic with Inbox; timeline view native.
Dynamics 365: Outlook integration native; activity tracking comprehensive.
Bloomerang: Constituent timeline purpose-built for nonprofit interactions; scheduling via integrations.

Donation and opportunity management (F3)

Requirement	CiviCRM	SuiteCRM	Dolibarr	EspoCRM	HubSpot	Salesforce	Dynamics 365	Bloomerang
F3.1 Donation recording	●	○	◐	○	○	●	◐	●
F3.2 Recurring donations	●	○	○	○	○	●	◐	●
F3.3 Pledge tracking	●	○	○	○	○	●	◐	●
F3.4 Pipeline stages	●	●	●	●	●	●	●	◐
F3.5 Soft credit allocation	●	○	○	○	○	●	○	●
F3.6 Acknowledgement tracking	●	○	○	○	○	●	○	●
F3.7 In-kind donations	●	○	○	○	○	●	○	●
F3.8 Grant management	●	○	○	○	○	●	○	◐

Notes:

CiviCRM: CiviContribute provides comprehensive fundraising; grant tracking via CiviGrant.
SuiteCRM: Sales-focused opportunities; requires significant customisation for donations.
Dolibarr: Commercial invoicing focus; donation tracking requires customisation.
EspoCRM: Sales opportunity model; nonprofit functionality requires custom entities.
HubSpot: Deal pipeline for sales; no native donation tracking; requires custom objects.
Salesforce: Nonprofit Cloud includes Fundraising with gift entry, pledges, allocations, acknowledgements.
Dynamics 365: Commercial CRM; nonprofit accelerator deprecated; requires customisation for donations.
Bloomerang: Purpose-built donor management with full giving lifecycle, retention analytics.

Campaign and communication management (F4)

Requirement	CiviCRM	SuiteCRM	Dolibarr	EspoCRM	HubSpot	Salesforce	Dynamics 365	Bloomerang
F4.1 Campaign tracking	●	●	◐	●	●	●	●	●
F4.2 Email campaigns	●	◐	◐	●	●	●	●	●
F4.3 Deliverability management	◐	○	○	◐	●	●	●	●
F4.4 Response tracking	●	◐	○	◐	●	●	●	●
F4.5 Communication templates	●	●	●	●	●	●	●	●
F4.6 Direct mail support	●	○	○	○	◐	●	◐	●
F4.7 SMS messaging	●	○	○	●	●	●	●	◐
F4.8 Marketing automation	◐	◐	○	◐	●	●	●	◐

Notes:

CiviCRM: CiviMail for email campaigns; SMS via extensions; automation via CiviRules.
SuiteCRM: Campaign module basic; email marketing limited; v8 improving marketing features.
Dolibarr: Basic mailing; primarily ERP focus.
EspoCRM: Mass email with templates; SMS via extensions; automation via BPM.
HubSpot: Marketing Hub provides full marketing automation; free tier has email limits.
Salesforce: Marketing Cloud or Account Engagement for advanced marketing; native email available.
Dynamics 365: Customer Insights for marketing automation; native email campaigns.
Bloomerang: Integrated email marketing for nonprofits; Mailchimp and other ESP integrations.

Reporting and analytics (F5)

Requirement	CiviCRM	SuiteCRM	Dolibarr	EspoCRM	HubSpot	Salesforce	Dynamics 365	Bloomerang
F5.1 Standard reports	●	●	●	●	●	●	●	●
F5.2 Custom report builder	●	●	◐	●	●	●	●	◐
F5.3 Dashboard creation	●	●	●	●	●	●	●	●
F5.4 Giving analytics	●	○	○	○	○	●	◐	●
F5.5 Data export	●	●	●	●	●	●	●	●
F5.6 Report scheduling	◐	●	○	●	●	●	●	○
F5.7 Comparative analytics	●	◐	◐	◐	●	●	●	●

Notes:

CiviCRM: SearchKit provides advanced reporting; donor retention reports native.
SuiteCRM: Reports module comprehensive; AOR (Advanced OpenReports) in v8.
Dolibarr: Business reporting focus; export via BI connector.
EspoCRM: Report builder with charts; scheduled reports available.
HubSpot: Analytics comprehensive; reporting limits by tier.
Salesforce: Reports and dashboards robust; Einstein Analytics for advanced analytics.
Dynamics 365: Power BI integration native; advanced analytics available.
Bloomerang: Donor retention dashboard purpose-built; LYBUNT/SYBUNT reports native.

Technical capability matrix

Deployment and integration (T1-T2)

Requirement	CiviCRM	SuiteCRM	Dolibarr	EspoCRM	HubSpot	Salesforce	Dynamics 365	Bloomerang
T1.1 Self-hosted deployment	●	●	●	●	○	○	◐	○
T1.2 Cloud deployment	●	●	●	●	●	●	●	●
T1.3 Container deployment	●	●	●	●	✗	✗	✗	✗
T1.4 Database options	◐	●	●	●	✗	✗	✗	✗
T2.1 REST API	●	●	●	●	●	●	●	●
T2.2 API authentication	●	●	◐	●	●	●	●	●
T2.3 Webhook support	◐	●	◐	●	●	●	●	○
T2.4 Bulk operations	●	●	●	●	●	●	●	●
T2.5 Pre-built integrations	●	◐	◐	◐	●	●	●	◐

Notes:

CiviCRM: Runs on Backdrop, Drupal, Joomla, WordPress, or standalone (v6+). MySQL/MariaDB only.
SuiteCRM: Docker images official (v8); supports MySQL/MariaDB and PostgreSQL.
Dolibarr: Docker images official; supports MySQL/MariaDB and PostgreSQL.
EspoCRM: Docker images official; supports MySQL/MariaDB and PostgreSQL.
HubSpot: SaaS only; comprehensive API with OAuth 2.0.
Salesforce: Multi-tenant cloud; on-premises via Customer 360 (enterprise only).
Dynamics 365: Cloud-primary; on-premises available for some products.
Bloomerang: SaaS only; REST API with private key and OAuth 2.0 authentication.

Security capability matrix (S1-S2)

Requirement	CiviCRM	SuiteCRM	Dolibarr	EspoCRM	HubSpot	Salesforce	Dynamics 365	Bloomerang
S1.1 MFA	◐	◐	◐	●	●	●	●	●
S1.2 SSO	●	●	◐	●	●	●	●	◐
S1.3 Role-based access	●	●	●	●	●	●	●	●
S1.4 Record-level security	●	●	◐	●	●	●	●	◐
S2.1 Encryption at rest	◐	◐	◐	◐	●	●	●	●
S2.2 Encryption in transit	●	●	●	●	●	●	●	●
S2.5 GDPR tools	●	◐	◐	●	●	●	●	●

Notes:

FOSS platforms: Encryption at rest depends on deployment configuration; database-level encryption supported.
CiviCRM: GDPR extension provides data export, erasure workflows; MFA via CMS or extension.
SuiteCRM: GDPR module available; MFA requires configuration.
EspoCRM: Built-in MFA with TOTP; GDPR features native.
Commercial platforms: Encryption at rest standard; compliance certifications available.

Individual platform assessments

CiviCRM

Category: FOSS constituent relationship management

Version assessed: 6.10.0 (January 2026)

Licence: AGPL-3.0

Repository: github.com/civicrm/civicrm-core

CiviCRM is purpose-built for nonprofit organisations, providing integrated contact management, fundraising, event registration, membership, email marketing, and case management. Version 6.0 (March 2025) introduced standalone deployment mode, removing the requirement for a CMS integration.

Architecture: CiviCRM operates as an application integrated with content management systems (Backdrop, Drupal, Joomla, WordPress) or in standalone mode. Data storage uses MySQL or MariaDB. The application provides modular components (CiviContribute, CiviEvent, CiviMember, CiviMail, CiviCase, CiviGrant) activated based on organisational needs.

Key capabilities:

SearchKit: Visual query builder with configurable displays, enabling complex reports and dashboards
CiviContribute: Donation processing with payment processor integrations, recurring giving, pledges, soft credits
CiviMail: Bulk email with A/B testing, open/click tracking, unsubscribe management
CiviEvent: Event registration with multiple pricing options, waitlists, participant management
CiviMember: Membership management with renewal tracking, grace periods, member directories
CiviGrant: Grant tracking for organisations making grants
RiverLea theme: Modern administrative interface (v6.0+)

API and integration:

REST API (APIv4): Full CRUD operations on all entities, chaining support, joins
External integrations: WordPress, Drupal, Mailchimp, Stripe, PayPal, Authorize.Net
Extension framework: 200+ extensions in extension directory

Deployment requirements:

PHP 8.1+
MySQL 5.7.5+ or MariaDB 10.4.3+
Web server: Apache or Nginx
CMS: Backdrop 1.x, Drupal 9/10, Joomla 4.x, WordPress 6.x, or standalone

Limitations:

Database limited to MySQL/MariaDB
User interface modernisation ongoing; some areas retain legacy design
Extension quality varies; core extensions well-maintained, community extensions may lag
Learning curve for configuration and customisation

Suitability: CiviCRM suits organisations requiring comprehensive nonprofit CRM functionality without licensing costs. Standalone mode (v6+) simplifies deployment for organisations not requiring CMS integration. Organisations with technical capacity for self-hosting gain full data sovereignty.

Documentation: docs.civicrm.org

SuiteCRM

Category: FOSS general-purpose CRM

Version assessed: 8.9.0 (September 2025), 7.14.x parallel maintenance

Licence: AGPL-3.0

Repository: github.com/salesagility/SuiteCRM-Core (v8), github.com/SuiteCRM/SuiteCRM (v7)

SuiteCRM is a general-purpose CRM platform forked from SugarCRM Community Edition, providing sales, marketing, and support functionality. Version 8 represents a complete architecture rebuild using Symfony framework with Vue.js frontend.

Architecture: SuiteCRM 8 uses Symfony backend with Vue.js frontend, deployed via Docker or traditional web server. Database options include MySQL, MariaDB, and PostgreSQL. SuiteCRM 7.x remains in maintenance for organisations not yet migrating.

Key capabilities:

Contact and account management with custom fields and relationships
Opportunity tracking with sales pipeline stages
Campaign management with email marketing
Case management for customer support
Meeting and call scheduling
Document management
Workflow automation with process definitions
Report module with charting

API and integration:

REST API (V8 API): GraphQL-style queries, CRUD operations
OAuth 2.0 authentication
Webhook support for event-driven integrations
Integrations: Asterisk, Joomla, various marketing platforms

Deployment requirements:

PHP 8.1+
MySQL 5.7+, MariaDB 10.4+, or PostgreSQL 13+
Web server: Apache or Nginx
Node.js for frontend build (v8)

Limitations:

Version 8 feature parity with v7 still progressing (levelling up phase)
Nonprofit-specific functionality requires customisation
Donation and fundraising tracking not native
Migration from v7 to v8 requires planning

Suitability: SuiteCRM suits organisations requiring general CRM functionality with full data control. Sales-focused feature set requires customisation for nonprofit donation tracking. Organisations with development capacity can extend the platform significantly.

Documentation: docs.suitecrm.com

Dolibarr

Category: FOSS ERP and CRM suite

Version assessed: 22.0.4 (December 2025)

Licence: GPL-3.0-or-later

Repository: github.com/Dolibarr/dolibarr

Dolibarr combines ERP and CRM functionality in a modular application, providing invoicing, proposals, orders, stock management, HR, and basic CRM capabilities. The platform serves small and medium organisations requiring integrated business management.

Architecture: Dolibarr uses PHP with MySQL/MariaDB or PostgreSQL database. Modular design enables activation of required components. Deployment via web installer, Docker, or cloud platforms.

Key capabilities:

Third-party management (customers, suppliers, prospects)
Contact management with unlimited custom fields
Commercial proposals and customer orders
Invoicing with payment tracking
Product and service catalogue
Stock management
Project management with task tracking
Agenda and scheduling
Email mailing campaigns (basic)
Accounting integration

API and integration:

REST API: CRUD operations on all modules
API Explorer with Swagger documentation
Module marketplace with community contributions
Import/export wizards

Deployment requirements:

PHP 7.1+ (8.x recommended)
MySQL 5.1+, MariaDB 5.1+, or PostgreSQL 9.1+
Web server: Apache or Nginx
Auto-installers available: DoliWamp, DoliDeb, DoliRpm

Limitations:

CRM functionality secondary to ERP focus
No native nonprofit/donation features
Email marketing basic compared to dedicated platforms
Segmentation and campaign management limited

Suitability: Dolibarr suits organisations requiring combined ERP and CRM in a single self-hosted platform. Organisations with invoicing, stock, and project management needs benefit from integrated modules. Not optimal for organisations prioritising fundraising or donor management.

Documentation: wiki.dolibarr.org

EspoCRM

Category: FOSS general-purpose CRM

Version assessed: 9.1.8 (July 2025)

Licence: AGPL-3.0

Repository: github.com/espocrm/espocrm

EspoCRM is a web application with single-page application frontend and REST API backend, designed for extensibility through metadata-driven architecture. The platform provides sales, marketing, and customer support capabilities with strong customisation options.

Architecture: EspoCRM uses PHP backend with JavaScript single-page application frontend. All entity definitions, layouts, and configurations stored as JSON metadata, enabling extensive customisation without code changes. Docker deployment supported.

Key capabilities:

Contact, account, and lead management
Opportunity tracking with sales pipeline
Email integration with tracking
Calendar and meeting scheduling
Task management
Campaign management
Mass email with templates
Knowledge base
Workflow automation (BPM processes)
Report builder with charts

API and integration:

REST API: Full CRUD on all entities with filtering and pagination
API documented with JSON Schema
OAuth 2.0 and API key authentication
Webhook support for event notifications
Extensions: SMS providers, VoIP, various integrations

Deployment requirements:

PHP 8.1+
MySQL 8.0+, MariaDB 10.3+, or PostgreSQL 15.0+
Web server: Apache or Nginx
Docker images official

Limitations:

No native nonprofit/donation functionality
Requires custom entity creation for fundraising
Community smaller than major platforms
Enterprise features in commercial extensions

Suitability: EspoCRM suits organisations requiring customisable CRM with full self-hosting control. Metadata-driven architecture enables significant adaptation without development. Organisations with technical capacity can build nonprofit-specific functionality through custom entities.

Documentation: docs.espocrm.com

HubSpot CRM

Category: Commercial marketing and sales platform

Version assessed: Continuous release (December 2025 changelog)

Licence: Proprietary

Documentation: developers.hubspot.com

HubSpot provides integrated marketing, sales, service, and CMS functionality with a free CRM tier and tiered paid products (Marketing Hub, Sales Hub, Service Hub, Operations Hub). The platform emphasises usability and marketing automation.

Architecture: HubSpot operates as multi-tenant SaaS with data centres in multiple regions. The platform provides extensive API coverage with OAuth 2.0 authentication. Custom objects available in paid tiers.

Key capabilities:

Contact and company management
Deal pipeline tracking
Email marketing with automation
Landing pages and forms
Meeting scheduling
Live chat and chatbots
Ticketing for customer service
Reporting and dashboards
Marketing automation workflows
Content management system

API and integration:

REST API: Comprehensive coverage of CRM objects
OAuth 2.0 and private app authentication
Webhooks for all object events
HubSpot CLI for development
Native integrations: 1,500+ in marketplace
Recent additions: Projects API, IP Ranges API, property validation rules

Deployment requirements:

SaaS only; no self-hosting option
Internet connectivity required

Nonprofit programme:

40% discount on paid products for eligible nonprofits

Limitations:

No native donation tracking
Custom objects limited in free tier
Free tier has email and feature restrictions
Marketing automation requires paid tiers
Data stored in HubSpot data centres (US-headquartered; CLOUD Act applies)

Suitability: HubSpot suits organisations prioritising marketing automation and inbound methodology. Free tier provides functional CRM for contact management and pipeline tracking. Nonprofit discount reduces cost for paid features. Not optimal for organisations requiring dedicated fundraising functionality.

Salesforce Nonprofit Cloud

Category: Commercial enterprise CRM for nonprofits

Version assessed: Version 66.0, Spring ‘26 (preview December 2025)

Licence: Proprietary

Documentation: developer.salesforce.com/developer-centers/nonprofit-cloud

Salesforce Nonprofit Cloud provides purpose-built functionality for nonprofit organisations on the Salesforce platform, including fundraising, programme management, case management, and marketing capabilities.

Architecture: Salesforce operates as multi-tenant SaaS on proprietary infrastructure with regional data centre options. Nonprofit Cloud includes standard objects for nonprofit operations. Customisation via declarative tools (flows, process builder) and Apex development.

Key capabilities:

Constituent management with relationships and households
Fundraising with gift entry, allocations, pledges, recurring giving
Programme management with enrolment tracking
Case management for services delivery
Grant management
Marketing Cloud integration for campaigns
Extensive reporting and dashboards
Einstein Analytics for AI-powered insights
Flow Builder for automation

API and integration:

REST API: Full access to all standard and custom objects
SOAP API for enterprise integrations
Tooling API for metadata operations
Bulk API for large data operations
Streaming API and Platform Events for real-time
AppExchange marketplace: thousands of integrations

Nonprofit programme:

Power of Us programme: 10 donated licences for eligible nonprofits
Discounted additional licences
Implementation grants available

Deployment requirements:

SaaS only; no self-hosting option
Internet connectivity required

Limitations:

Complexity requires training and potentially consultant support
Implementation costs can be significant
Licensing structure complex; costs scale with users and features
Platform changes require ongoing learning
US-headquartered; CLOUD Act applies

Suitability: Salesforce Nonprofit Cloud suits organisations requiring enterprise-grade CRM with comprehensive nonprofit functionality. Donated licences reduce entry cost, but implementation and customisation require investment. Organisations with Salesforce expertise or consultant relationships benefit most.

Microsoft Dynamics 365

Category: Commercial enterprise CRM and ERP

Version assessed: Dataverse, continuous release

Licence: Proprietary

Documentation: learn.microsoft.com/en-us/dynamics365/

Microsoft Dynamics 365 provides CRM (Sales, Customer Service, Marketing) and ERP (Finance, Supply Chain) applications on the Dataverse platform. The Nonprofit Accelerator (retired December 2025) provided nonprofit data models; organisations now use core Dynamics with customisation.

Architecture: Dynamics 365 operates on Microsoft Azure infrastructure with Dataverse as the underlying data platform. Power Platform (Power Apps, Power Automate, Power BI) extends functionality. On-premises deployment available for some products.

Key capabilities:

Contact, account, and lead management
Opportunity and pipeline management
Customer service case management
Marketing automation (Customer Insights)
Project management
Integration with Microsoft 365
Power BI analytics
Power Automate workflows
AI Builder for intelligence features

API and integration:

Web API: OData v4 RESTful access
Organization Service (SOAP)
Dataverse SDK for .NET development
Power Platform connectors
Azure Logic Apps integration
Native Microsoft 365 integration

Nonprofit programme:

Microsoft Tech for Social Impact pricing:
- Dynamics 365 Sales Enterprise: $23.80 USD/user/month
- Dynamics 365 Business Central: $28.00 USD/user/month
Common Data Model for Nonprofits available via GitHub and AppSource

Deployment requirements:

Cloud deployment via Azure
On-premises available for Customer Engagement (on-premises)
Internet connectivity required for cloud

Limitations:

Nonprofit Accelerator retired December 2025
Nonprofit functionality requires customisation or partner solutions
Complexity requires training
Licensing structure complex
US-headquartered; CLOUD Act applies

Suitability: Dynamics 365 suits organisations already invested in Microsoft ecosystem requiring enterprise CRM integrated with Office 365 and Azure. Nonprofit pricing reduces cost. Organisations need to build or procure nonprofit-specific customisations since accelerator retirement.

Bloomerang

Category: Commercial donor management platform

Version assessed: Continuous release (September 2025 API documentation)

Licence: Proprietary

Documentation: bloomerang.co/product/integrations-data-management/api/

Bloomerang provides purpose-built donor management for small to medium nonprofits, emphasising donor retention analytics and ease of use. The platform focuses on fundraising rather than general-purpose CRM.

Architecture: Bloomerang operates as SaaS with US-based hosting. The platform provides REST API for integrations and Bloomerang.js for client-side donation form integration.

Key capabilities:

Constituent management with households
Donation tracking with designations
Recurring giving management
Pledge tracking
Donor retention analytics (engagement meter)
LYBUNT/SYBUNT reporting
Email marketing integration
Online donation forms
Event management
Grant tracking (basic)
Mobile app

API and integration:

REST API v2: Constituents, donations, interactions, transactions
Private key and OAuth 2.0 authentication
Bloomerang.js: Client-side form integration with Spreedly tokenisation
Integrations: Mailchimp, Constant Contact, QuickBooks, payment processors

Deployment requirements:

SaaS only; no self-hosting option
Internet connectivity required
Payment processing: Stripe, Authorize.Net, BluePay

Limitations:

No sandbox/test environment for API development
Webhooks not documented
Limited workflow automation
Custom reporting less flexible than larger platforms
Single focus on donor management; limited general CRM features

Suitability: Bloomerang suits small to medium nonprofits prioritising donor retention and ease of use over platform flexibility. Purpose-built donor management removes customisation burden. Organisations requiring complex workflow automation or extensive customisation may find limitations.

Selection guidance

Decision framework

Platform selection depends on organisational context, technical capacity, and functional priorities.

                                 START
                                   |
                   +---------------v---------------+
                   | Primary need: Donor           |
                   | management/fundraising?       |
                   +---------------+---------------+
                                   |
              +--------------------+--------------------+
              |                                         |
              v Yes                                     v No
+-------------+-------------+              +------------+------------+
| Technical capacity for    |              | General CRM with sales/ |
| self-hosting?             |              | marketing focus?        |
+-------------+-------------+              +------------+------------+
              |                                         |
     +--------+--------+                       +--------+---------+
     |                 |                       |                  |
     v Yes             v No                    v Yes              v No
+----+----+      +-----+-----+           +-----+-----+      +-----+-----+
|CiviCRM  |      |Bloomerang |           |Self-host  |      |Enterprise |
|         |      |Salesforce |           |capability?|      |needs?     |
+---------+      |Nonprofit  |           +-----+-----+      +-----+-----+
                 +-----------+                 |                  |
                                      +--------+--------+    +----+-----+
                                      |                 |    |          |
                                      v Yes             v No v          v Yes
                                +-----+-----+     +-----+----+-+  +-----+-----+
                                | SuiteCRM  |     | HubSpot    |  |Salesforce/|
                                | EspoCRM   |     | Free tier  |  |Dynamics   |
                                | Dolibarr  |     +------------+  +-----------+
                                +-----------+

Recommendations by context

Organisations with limited IT capacity

Recommended: Bloomerang or HubSpot Free

Bloomerang provides purpose-built donor management without technical complexity. Pricing starts at approximately $119/month for small organisations. The platform handles compliance, security, and updates.

HubSpot Free tier provides functional CRM for contact management without cost. Marketing and sales features require paid upgrades. Suitable for organisations starting CRM adoption.

Considerations:

Bloomerang: Fundraising focus; limited if general CRM needed
HubSpot: No native nonprofit features; custom objects require paid tier

Organisations with technical capacity for self-hosting

Recommended: CiviCRM or EspoCRM

CiviCRM provides comprehensive nonprofit functionality (fundraising, events, memberships, email) in a single self-hosted platform. Standalone mode (v6+) simplifies deployment. No licensing costs.

EspoCRM provides customisable general CRM with metadata-driven architecture. Organisations can build nonprofit functionality through custom entities. Strong API for integration.

Considerations:

CiviCRM: MySQL/MariaDB only; CMS integration required (or standalone mode)
EspoCRM: Nonprofit features require custom development
Both require hosting infrastructure and maintenance capacity

Enterprise organisations

Recommended: Salesforce Nonprofit Cloud or Microsoft Dynamics 365

Salesforce Nonprofit Cloud provides comprehensive functionality with donated licences for eligible nonprofits. Ecosystem of partners and applications. Complex but capable.

Dynamics 365 suits organisations invested in Microsoft ecosystem. Nonprofit pricing available. Requires customisation for nonprofit functionality since accelerator retirement.

Considerations:

Implementation complexity and cost
Ongoing administration requirements
Consultant support often beneficial
Both US-headquartered (CLOUD Act jurisdictional considerations)

Organisations requiring ERP and CRM

Recommended: Dolibarr or Dynamics 365 Business Central

Dolibarr combines ERP (invoicing, stock, projects) and basic CRM in single self-hosted platform. No licensing costs. Suitable for organisations prioritising operational management.

Dynamics 365 Business Central provides integrated ERP with CRM linkage. Nonprofit pricing at $28/user/month. Requires cloud deployment.

Considerations:

Dolibarr: CRM functionality basic; no native fundraising
Business Central: CRM features limited without Dynamics 365 Sales addition

Migration considerations

From spreadsheets

All platforms support CSV import. Key decisions:

Data cleaning before migration
Field mapping to new structure
Duplicate handling strategy
Historical data requirements

From legacy CRM

Migration complexity increases with:

Custom field volume
Relationship complexity
Integration dependencies
Data volume

CiviCRM, Salesforce, and Dynamics 365 have established migration tooling and partner ecosystems. Smaller platforms require more manual migration work.

Exit planning

Data portability varies:

FOSS platforms: Full database access; export all data
Commercial platforms: API export; check data portability terms
Bloomerang: REST API export; no bulk database access

Build exit strategy into vendor agreements. Ensure data export capabilities meet retention and migration requirements.

External resources

Documentation links

FOSS platforms

Platform	Documentation	API reference	Repository
CiviCRM	docs.civicrm.org	docs.civicrm.org/dev/en/latest/api/	github.com/civicrm/civicrm-core
SuiteCRM	docs.suitecrm.com	docs.suitecrm.com/8.x/admin/api/	github.com/salesagility/SuiteCRM-Core
Dolibarr	wiki.dolibarr.org	wiki.dolibarr.org/index.php/API	github.com/Dolibarr/dolibarr
EspoCRM	docs.espocrm.com	docs.espocrm.com/development/api/	github.com/espocrm/espocrm

Commercial platforms

Platform	Documentation	API reference	Nonprofit programme	Trust centre
HubSpot	knowledge.hubspot.com	developers.hubspot.com	hubspot.com/nonprofits	trust.hubspot.com
Salesforce	help.salesforce.com	developer.salesforce.com	salesforce.org	trust.salesforce.com
Dynamics 365	learn.microsoft.com/dynamics365	learn.microsoft.com/dynamics365/developer	microsoft.com/nonprofits	servicetrust.microsoft.com
Bloomerang	support.bloomerang.co	bloomerang.co/product/integrations-data-management/api/	N/A (nonprofit-focused)	bloomerang.co/security

CRM Platforms

Requirements taxonomy

Functional requirements

Contact and organisation management

Interaction and activity tracking

Donation and opportunity management

Campaign and communication management

Reporting and analytics

Event management

Membership management

Technical requirements

Deployment and hosting

Integration architecture

Data management

Security requirements

Authentication and access control

Data protection

Operational requirements

Extensibility

Support and community

Comparison matrices

Rating scale

Platform overview

Functional capability matrix

Contact and organisation management (F1)

Interaction and activity tracking (F2)

Donation and opportunity management (F3)

Campaign and communication management (F4)

Reporting and analytics (F5)

Technical capability matrix

Deployment and integration (T1-T2)

Security capability matrix (S1-S2)

Individual platform assessments

CiviCRM

SuiteCRM

Dolibarr

EspoCRM

HubSpot CRM

Salesforce Nonprofit Cloud

Microsoft Dynamics 365

Bloomerang

Selection guidance

Decision framework

Recommendations by context

Organisations with limited IT capacity

Organisations with technical capacity for self-hosting

Enterprise organisations

Organisations requiring ERP and CRM

Migration considerations

From spreadsheets

From legacy CRM

Exit planning

External resources

Documentation links

FOSS platforms

Commercial platforms

See also