FluentCRM vs PloverCRM FAQ

What’s the difference between FluentCRM and PloverCRM? #

PloverCRM is a plugin, FluentCRM is a CRM backend option:

PloverCRM (The Plugin):

• WordPress plugin that provides:
  • 📱 Native mobile apps (iOS & Android)
  • 🔗 15+ form builder integrations
  • 🔐 Advanced role-based permissions
  • 📊 Contact management interface
  • 🎯 UTM tracking and enrichment
  • 🔔 Push notifications
  • ⏰ Reminders system

FluentCRM (CRM Backend Option):

• Separate WordPress plugin for email marketing
• Can be used as PloverCRM’s data storage backend
• Provides:
  • 📧 Email marketing campaigns
  • 🤖 Marketing automation
  • 📈 Advanced funnels and sequences
  • 📊 Email analytics
  • 🎨 Email templates

Think of it this way:

• PloverCRM = Frontend (mobile apps, forms, UI)
• FluentCRM = Backend option (data storage + email marketing)

You can use:

1. PloverCRM with built-in backend (WordPress CPT)
2. PloverCRM with FluentCRM backend (FluentCRM tables)

Learn more: Choosing CRM Provider

---

Do I need both PloverCRM and FluentCRM? #

No, you don’t need both:

Option 1: PloverCRM Only (Built-in Backend)

• ✅ Install PloverCRM only
• ✅ Use built-in WordPress storage
• ✅ Get mobile apps, forms, permissions
• ❌ No email marketing features
• Best for: Contact management, mobile access, sales teams

Option 2: PloverCRM + FluentCRM

• ✅ Install both plugins
• ✅ PloverCRM uses FluentCRM for storage
• ✅ Get mobile apps + email marketing
• ✅ Access to FluentCRM’s automation
• Best for: Marketing + sales teams, email campaigns

Decision Matrix:

Need	PloverCRM Only	PloverCRM + FluentCRM
Mobile app access	✅	✅
Form integrations	✅	✅
Contact management	✅	✅
Advanced permissions	✅	✅
Email marketing	❌	✅
Marketing automation	❌	✅
Email funnels	❌	✅
Email templates	❌	✅
Simple setup	✅	❌ (two plugins)
Lightweight	✅	❌ (more features)
Cost	Lower	Higher (two licenses)

Recommendation:

• Start with PloverCRM only
• Add FluentCRM later if you need email marketing
• Both options support mobile apps and forms

---

Which CRM backend should I choose? #

Choose based on your needs:

PloverCRM Backend (Built-in):

Pros:

• ✅ Simple setup (one plugin)
• ✅ Lightweight and fast
• ✅ Uses WordPress native features (CPT, taxonomies)
• ✅ Familiar WordPress structure
• ✅ Lower cost (one license)
• ✅ Easy to understand
• ✅ Good for < 10,000 contacts

Cons:

• ❌ No email marketing features
• ❌ No automation workflows
• ❌ Less optimized for large datasets
• ❌ Basic contact storage only

Best For:

• Sales teams (no email marketing)
• Support teams (ticket tracking)
• Small businesses (< 10,000 contacts)
• Simple contact management
• Mobile-first teams
• Budget-conscious users

---

FluentCRM Backend:

Pros:

• ✅ Email marketing included
• ✅ Advanced automation
• ✅ Funnels and sequences
• ✅ Email templates
• ✅ Optimized database structure
• ✅ Better for large datasets (10,000+ contacts)
• ✅ More features overall

Cons:

• ❌ Two plugins to manage
• ❌ More complex setup
• ❌ Higher cost (two licenses)
• ❌ Steeper learning curve
• ❌ More server resources required

Best For:

• Marketing teams (email campaigns)
• Marketing + sales teams
• Large contact lists (10,000+)
• Email automation needs
• Advanced segmentation
• E-commerce businesses

---

Quick Decision Guide:

Choose PloverCRM Backend if:

• You don’t need email marketing
• You have < 10,000 contacts
• You want simple setup
• You’re on a budget
• You primarily need mobile access

Choose FluentCRM Backend if:

• You need email marketing
• You have 10,000+ contacts
• You want automation workflows
• You need advanced features
• You’re willing to manage two plugins

Learn more: Choosing CRM Provider | Multi-CRM Architecture

---

Can I switch between backends later? #

Yes, but with limitations:

Switching Process:

1. Export contacts from current backend (CSV)
2. Change CRM provider in settings
3. Import contacts to new backend
4. Recreate custom fields
5. Recreate lists and tags
6. Reassign owners

What Transfers:

• ✅ Contact information (via CSV)
• ✅ Standard fields
• ✅ Custom field values (recreate fields first)

What Doesn’t Transfer:

• ❌ Notes (export separately if needed)
• ❌ Reminders (recreate manually)
• ❌ Activity history
• ❌ Email campaign history (FluentCRM only)
• ❌ Automation workflows (FluentCRM only)

Important Considerations:

• No automatic migration – Manual export/import required
• Downtime – CRM unavailable during switch
• Data loss risk – Backup everything first
• Team disruption – Training on new system
• Time investment – Several hours to days

Recommendation:

• Choose carefully during initial setup
• Switching later is possible but painful
• Test both options before deciding
• Consider long-term needs

Learn more: Choosing CRM Provider

---

Does PloverCRM work without FluentCRM? #

Yes! PloverCRM works completely independently:

PloverCRM Standalone Features:

• ✅ Full contact management
• ✅ Mobile apps (iOS & Android)
• ✅ 15+ form integrations
• ✅ Custom fields
• ✅ Lists and tags
• ✅ Contact stages
• ✅ Notes and activities
• ✅ Reminders
• ✅ Advanced permissions
• ✅ UTM tracking
• ✅ Push notifications
• ✅ REST API
• ✅ CSV import/export

What You Don’t Get (Without FluentCRM):

• ❌ Email marketing campaigns
• ❌ Marketing automation
• ❌ Email funnels
• ❌ Email templates
• ❌ Email analytics
• ❌ Advanced segmentation (FluentCRM-specific)

FluentCRM is Optional:

• Not required for PloverCRM to work
• Only needed if you want email marketing
• Can be added later if needed

Common Misconception:

• ❌ “I need FluentCRM to use PloverCRM” – FALSE
• ✅ “PloverCRM works standalone” – TRUE
• ✅ “FluentCRM is an optional enhancement” – TRUE

---

Can I use FluentCRM’s email features with PloverCRM? #

Yes! When using FluentCRM backend:

Available FluentCRM Features:

• ✅ Email campaigns
• ✅ Email automation
• ✅ Email funnels
• ✅ Email sequences
• ✅ Email templates
• ✅ Email analytics
• ✅ Advanced segmentation
• ✅ Double opt-in
• ✅ Unsubscribe management

How It Works:

1. Install both PloverCRM and FluentCRM
2. Set CRM provider to “FluentCRM” in PloverCRM settings
3. Contacts stored in FluentCRM database
4. Access FluentCRM features from FluentCRM menu
5. Use PloverCRM for mobile app and forms

Workflow Example:

<span class="hljs-number">1.</span> Form submission → PloverCRM captures
<span class="hljs-number">2.</span> Contact created in FluentCRM database
<span class="hljs-number">3.</span> FluentCRM automation triggered
<span class="hljs-number">4.</span> Welcome <span class="hljs-section">email</span> sent via FluentCRM
<span class="hljs-number">5.</span> Contact visible in PloverCRM mobile app
<span class="hljs-number">6.</span> Sales rep follows up via mobile

Best of Both Worlds:

• PloverCRM: Mobile apps, forms, permissions
• FluentCRM: Email marketing, automation
• Shared contact database
• Seamless integration

Learn more: FluentCRM Module

---

Which backend is faster? #

Performance Comparison:

PloverCRM Backend:

• Small datasets (< 1,000): Very fast ⚡⚡⚡
• Medium datasets (1,000-10,000): Fast ⚡⚡
• Large datasets (10,000+): Slower ⚡
• Uses WordPress Custom Post Types
• Leverages WordPress caching
• Good for most use cases

FluentCRM Backend:

• Small datasets (< 1,000): Fast ⚡⚡
• Medium datasets (1,000-10,000): Fast ⚡⚡
• Large datasets (10,000+): Very fast ⚡⚡⚡
• Optimized database structure
• Custom tables for contacts
• Better for large datasets

Benchmarks:

Contact List Loading (1,000 contacts):

• PloverCRM: ~0.3 seconds
• FluentCRM: ~0.2 seconds

Contact List Loading (10,000 contacts):

• PloverCRM: ~1.5 seconds
• FluentCRM: ~0.5 seconds

Contact Search (10,000 contacts):

• PloverCRM: ~0.8 seconds
• FluentCRM: ~0.3 seconds

Recommendation:

• < 10,000 contacts: Either backend works well
• 10,000+ contacts: FluentCRM backend recommended
• Enable object caching (Redis/Memcached) for best performance

Optimization Tips:

• Use pagination (20 contacts per page)
• Enable object caching
• Optimize database indexes
• Use CDN for admin assets
• Upgrade hosting if needed

---

Can I use both backends simultaneously? #

No, you must choose one:

How It Works:

• PloverCRM → Settings → General → CRM Provider
• Select either “PloverCRM” or “FluentCRM”
• Only one backend active at a time
• Switching changes where data is stored

Why Not Both?

• Contacts would be in two places
• Data synchronization issues
• Duplicate management problems
• Confusing for users
• Performance overhead

Switching Between:

• Change setting anytime
• Requires data migration (export/import)
• No automatic sync
• Choose carefully initially

Multi-Site Exception:

• Different sites can use different backends
• Site 1: PloverCRM backend
• Site 2: FluentCRM backend
• Each site independent

---

Does PloverCRM replace FluentCRM? #

No, they serve different purposes:

PloverCRM:

• Purpose: Mobile CRM, form integrations, permissions
• Focus: Contact management, mobile access, sales teams
• Strength: Mobile apps, advanced permissions, form integrations

FluentCRM:

• Purpose: Email marketing, automation
• Focus: Email campaigns, marketing automation, funnels
• Strength: Email features, automation workflows, segmentation

They Complement Each Other:

• PloverCRM provides mobile access to FluentCRM contacts
• FluentCRM provides email marketing for PloverCRM contacts
• Together: Complete marketing + sales solution

Use Cases:

PloverCRM Only:

• Sales team needs mobile CRM
• No email marketing required
• Simple contact management

FluentCRM Only:

• Email marketing focus
• No mobile app needed
• Desktop-only team

Both Together:

• Marketing + sales teams
• Email campaigns + mobile follow-up
• Complete CRM solution

Learn more: What is PloverCRM?

---

Which one should I buy first? #

Recommendation based on needs:

Buy PloverCRM First If:

• ✅ You need mobile app access
• ✅ You want form integrations
• ✅ You need advanced permissions
• ✅ You have sales team
• ✅ You don’t need email marketing yet
• ✅ You want to start simple

Buy FluentCRM First If:

• ✅ You need email marketing now
• ✅ You want automation workflows
• ✅ You don’t need mobile app
• ✅ You have marketing team
• ✅ Desktop-only team

Buy Both Together If:

• ✅ You need mobile + email marketing
• ✅ You have marketing + sales teams
• ✅ You want complete solution
• ✅ You have budget for both

Typical Purchase Path:

1. Start with PloverCRM (mobile + forms)
2. Add FluentCRM later (email marketing)
3. Switch to FluentCRM backend
4. Migrate contacts (one-time)
5. Use both features

Budget Consideration:

• PloverCRM: $XX (one-time)
• FluentCRM: $XX (one-time)
• Both: $XX total
• Consider long-term needs

---

Can I get support for both plugins? #

Yes, but from different teams:

PloverCRM Support:

• Email: [email protected]
• Covers: PloverCRM plugin, mobile apps, integrations
• Response: 24-48 hours
• Documentation: docs.webplover.com

FluentCRM Support:

• Email: [email protected]
• Covers: FluentCRM plugin, email marketing, automation
• Response: 24-48 hours
• Documentation: fluentcrm.com/docs

Integration Issues:

• Contact PloverCRM support first
• They’ll coordinate with FluentCRM if needed
• Most issues are PloverCRM-specific

What Each Team Supports:

PloverCRM Team:

• Mobile app issues
• Form integration problems
• Permission configuration
• API questions
• PloverCRM backend issues

FluentCRM Team:

• Email campaign issues
• Automation workflow problems
• Email template questions
• FluentCRM backend issues
• Segmentation questions

Best Practice:

• Identify which plugin has the issue
• Contact appropriate support team
• Provide details about both plugins if using together

---

Related FAQs #

• General FAQs
• Technical FAQs
• Choosing CRM Provider
• Multi-CRM Architecture

---

Still confused? Contact [email protected] for personalized recommendations.