folk CRM vs AdvisorEngine CRM: Architecture, TCO & Migration

folk CRM is a lightweight, relationship-first CRM designed for agencies, VCs, and small sales teams that live in LinkedIn and email. AdvisorEngine CRM is a purpose-built wealth management platform — the successor to Junxure CRM — owned by Franklin Templeton and designed exclusively for financial advisors and RIAs. These tools share the label "CRM" but solve fundamentally different problems. Choosing between them is a business-model question, not a feature comparison.

One-line verdict: Choose folk CRM if you're a relationship-driven team under 50 people that needs fast, flexible contact management with API access. Choose AdvisorEngine CRM if you're a registered investment advisor (RIA) or wealth management firm that needs custodian integrations, household-level data hierarchies, and compliance-oriented workflows.

Why This Comparison Exists (and What It Excludes)

This article covers folk CRM and AdvisorEngine CRM specifically because we see migration requests between them — typically from small RIAs that outgrow folk's flat data model, or from advisory firms that want a lighter tool for non-client relationship management. We do not cover Wealthbox, Redtail, or Salesforce Financial Services Cloud here, though all three are direct AdvisorEngine competitors in the RIA space. If your shortlist includes those tools, this article will still help you understand AdvisorEngine's data model constraints and export limitations, but it won't give you a head-to-head against those alternatives.

What Is the Core Architecture Difference Between folk CRM and AdvisorEngine CRM?

folk CRM is a contact-first platform with a flat, spreadsheet-like data model. AdvisorEngine CRM is a record-hierarchy platform built around the household → individual → action structure that wealth management compliance requires. This architectural divergence means data never maps 1:1 between them — the single biggest factor in any migration.

folk CRM: Contact-Centric and API-Accessible

folk is a modern, lightweight CRM designed for people who manage relationships rather than pipelines. Unlike Salesforce or HubSpot, folk is built around contact management first — with a clean spreadsheet-like interface, AI-powered contact enrichment, email sequences, and pipeline views.

The data model is flat by default. People and Companies are top-level objects that live across the workspace, while Groups act as workflow-specific databases with their own custom fields, filters, collaborators, and views. This design has an important architectural consequence: the same person can look different across groups because group-scoped custom fields do not travel with the record. For teams running sales, recruiting, and partnerships in parallel, that's a feature. For migrations into a rigid household model, it's friction.

On Premium and above, custom objects, deal objects, email sequences, advanced roles and permissions, dashboards, API access, full interaction history, and doubled credit limits become available. But there is no native concept of a "household" or multi-level client hierarchy — a gap that matters enormously if your workflows are financial-services oriented.

folk recently released a developer REST API (alongside their longstanding Zapier connector), although it's fairly basic compared to other, more mature CRMs. The API uses REST, authenticated with API key (Bearer token). Changes are detected via webhook subscriptions for record events, with polling of list endpoints as a fallback. The current rate limit is 600 requests per minute per user.

folk's documented hard limits for scale planning:

• 500 groups per workspace
• 100 members per workspace
• 100,000 contacts per group
• 100 custom fields per group
• 100,000 CSV rows per import
• Enrichment limited to 500 credits per workspace per month on Standard — shared across the entire team, not per user

Key constraints:

• API access is gated to Premium ($48/user/month annual) and above — Standard users have no programmatic access
• The API surface area matches folk's product positioning as a contact-first relationship CRM. No native LinkedIn / Telegram / WhatsApp conversation endpoints despite the "folk MCP" marketing.
• There is still no native workflow automation, no mobile app, and no phone support.

API status note (as of June 2025): folk's Interactions API endpoint is marked private beta. Migration teams should verify current availability directly with folk support before planning extraction workflows that depend on interaction data. folk's developer surface is actively evolving; these constraints may change.

AdvisorEngine CRM: Wealth Management Hierarchy Engine

AdvisorEngine CRM is a sophisticated software platform designed specifically for financial advisors and wealth management professionals. It integrates advanced customer relationship management (CRM) capabilities with financial planning tools, creating a comprehensive solution for managing client relationships and investment portfolios.

AdvisorEngine CRM is the successor to Junxure CRM, delivering an entirely new technology foundation and enhanced productivity capabilities. AdvisorEngine is a wholly owned subsidiary of Franklin Templeton, one of the world's largest asset managers.

The data model is purpose-built around a Record → Person → Action hierarchy:

• Record: Represents a household, entity, or trust (e.g., "The Smith Family Trust"). This is the core container object.
• Person: Represents an individual within that household. Each Record can contain up to two Persons, but a Person can appear in more than one Record — supporting household, business, and linked-relationship scenarios.
• Action: Every communication, task, or document logged in the system belongs to one Record. Actions can be chained into Workflows, and Workflow Templates can prefill notes, assignees, and step order.

This rigidity is not a flaw — it's a regulatory requirement. Financial advisors must track exactly who was spoken to, what was said, and when it happened to satisfy SEC and FINRA audits. The platform prevents easy deletion of records and enforces referential integrity across the hierarchy.

AdvisorEngine features support for multi-custody data integration, performance reporting, rebalancing, and fee billing. This level of vertical integration doesn't exist in folk or in most general-purpose CRMs.

The critical technical limitations: There is no bulk document download feature in AdvisorEngine CRM. Documents must be downloaded individually from each Record's document storage area. There is no public REST API for programmatic data extraction. Bulk import uses a locally installed tool and is capped at 1,000 Records per import.

How Do Operational Workflows Compare Between folk CRM and AdvisorEngine CRM?

folk CRM is optimized for speed-to-value: fast contact capture, quick pipeline views, and email sequences. AdvisorEngine CRM is optimized for compliance-driven practice management: multi-step workflows, audit-ready action logging, and custodian data synchronization. They're built for different operational cadences.

Capability	folk CRM	AdvisorEngine CRM	Winner
Contact capture speed	folkX Chrome extension pulls from LinkedIn in one click	Manual entry or custodian sync	folk CRM
Household/entity hierarchies	Not supported natively	Record → Person → Action hierarchy	AdvisorEngine CRM
Pipeline management	Kanban + table views on all tiers	Pipeline views with custodian-linked data	folk CRM
Workflow automation	No native workflow engine	Purpose-built workflow engine with templates	AdvisorEngine CRM
Email sequences	Available on Premium ($48/user/mo)	Not a core feature; uses Constant Contact integration	folk CRM
Compliance action logging	Basic interaction history (30 interactions on Standard)	Full audit-trail Actions tied to Records/Persons	AdvisorEngine CRM
Document management	No native document storage	Unlimited document storage, per-Record filing	AdvisorEngine CRM
Custodian data integration	Not available	Schwab, Fidelity, Pershing, SEI	AdvisorEngine CRM
SLA tracking	Not supported	Workflow-based task deadlines (not ITSM-grade)	AdvisorEngine CRM
AI enrichment	Magic Fields auto-fills company data	Not a native feature	folk CRM
Mobile app	None	Mobile-accessible cloud app	AdvisorEngine CRM
Collaboration	Shared pipelines, notes, @mentions	User groups, data entitlements, shared workflows	AdvisorEngine CRM

Summary: folk wins on speed, simplicity, and outbound prospecting. AdvisorEngine wins on everything that matters to a regulated financial advisory practice. Neither is a true service desk with SLA breach clocks — if that's a hard requirement, shortlist a dedicated ITSM tool.

How Do You Migrate Data Between folk CRM and AdvisorEngine CRM?

Migrating between these two systems is not a field-mapping exercise — it's a data model transformation. folk's flat contact model must be restructured into AdvisorEngine's hierarchical Record → Person → Action model (or vice versa). Every migration between them requires custom scripting.

Exporting Data from folk CRM

folk supports CSV exports from its grid views and, on Premium, API-based extraction via its REST API. But the native UI export has important gaps.

folk's UI export is group-by-group, not workspace-wide. The export produces a zip containing contacts and notes CSV files — but interactions and reminders are explicitly excluded. For teams that rely on interaction history, the default export is incomplete by design.

What you get:

• Contacts (People) with all standard and custom fields
• Companies with associated metadata
• Pipeline/deal stage data (Premium only)
• Notes and tags

What you don't get easily:

• Full email thread content (synced from Gmail/Outlook, not stored natively)
• LinkedIn interaction metadata captured via folkX
• Interactions and reminders (excluded from UI export)
• Enrichment data beyond what's written to fields

For deeper extraction, use the REST API and webhooks. The Interactions API endpoint exists but is still marked private beta (as of June 2025), which means migration teams must plan around which activity data is generally available and which is still gated. Verify current status at developer.folk.app before scoping your extraction.

Exporting Data from AdvisorEngine CRM

For a detailed technical breakdown, see our guide: How to Export Data from AdvisorEngine CRM: Methods & Limits.

The short version: For an RIA that has stored years of client agreements, financial plans, compliance correspondence, KYC documentation, signed investment policy statements, and historical tax forms in the CRM, the native export captures your structured data but leaves behind the unstructured data that auditors and compliance officers care about most.

The native Database Export produces a password-protected zip of CSV files covering Records, Persons, Actions, revenue data, and custom fields. The problems:

1. Flattened hierarchies. The export strips the relational mapping between Records and Persons. You lose the exact links showing which individual belongs to which household.
2. Documents excluded entirely. For firms with thousands of stored files across hundreds of client Records, this is a manual, time-intensive process. Documents must be downloaded individually from each Record's document storage area.
3. Action log truncation. Long historical notes are sometimes truncated or split across CSV columns.
4. No public API alternative. There is no REST API to programmatically extract data. You're entirely dependent on UI-driven export tools.

The 5 Most Common Migration Pitfalls (folk → AdvisorEngine)

If you're moving from folk CRM to AdvisorEngine CRM, these are the issues that break migrations when you don't plan for them:

1. Household construction from flat contacts. folk has no household concept. Every contact is a standalone Person. Migrating into AdvisorEngine requires you to construct Record (household) entities and assign Persons to them. This requires either a supplementary mapping spreadsheet or logic that groups contacts by shared email domain, address, or a custom "household" tag — none of which are guaranteed to be clean.

2. Action history reconstruction. folk's interaction history doesn't carry a structured "Action type" field the way AdvisorEngine expects. You'll need to classify each interaction into AdvisorEngine's action taxonomy (phone call, email, meeting, task, etc.) during migration, or they'll land as generic notes. And remember: folk's UI export excludes interactions entirely, so you'll need the API for this data.

3. Document gap. folk has no native document storage. If your team stored files in Google Drive, Dropbox, or email, those documents need to be collected separately and uploaded to AdvisorEngine's per-Record document storage. This is a parallel workstream, not part of the CRM migration itself.

4. Custom field type mismatches. folk's custom fields are flexible but loosely typed. Group-scoped fields add another layer of complexity — you must decide which fields become Record-level data, Person-level data, or User Defined Fields inside AdvisorEngine. Fields that are plain text in folk may need mapping to specific data types (currency, percentages, dates) with validation rules.

5. Revenue and AUM data. folk doesn't model assets under management or revenue per client natively. If you've tracked these in custom fields, the values need validation, normalization, and mapping to AdvisorEngine's revenue and portfolio data structures. AdvisorEngine splits import by data class — Record Data Import, Asset Import, and Revenue Import are documented as separate processes.

The 5 Most Common Migration Pitfalls (AdvisorEngine → folk)

The reverse direction — moving from AdvisorEngine to folk — has its own failure modes, distinct from the forward migration:

1. Hierarchy flattening without data loss. AdvisorEngine's Record → Person → Action structure must collapse into folk's flat contact model. A Record with two Persons, 14 Actions, and linked documents becomes two separate contacts — and the structural relationship between them must be preserved as metadata (tags, custom fields, or notes), not as a native hierarchy. Deciding what to keep, what to merge, and what to tag is the hardest design decision.

2. Action-to-interaction lossy mapping. AdvisorEngine Actions have structured fields: action type, workflow step, assigned user, completion date, and linked Record. folk's interaction model is simpler — it tracks date, type, and content. Migrating Actions into folk interactions loses workflow context, step sequencing, and multi-user assignment chains. Teams must decide whether to preserve this data as structured custom fields or append it as note text.

3. Document extraction bottleneck. Since AdvisorEngine has no bulk document download, extracting files from hundreds or thousands of Records is a manual, click-per-file process. folk has no native document storage to receive them, so you'll need a parallel cloud storage solution (Google Drive, Dropbox, SharePoint) and a linking convention inside folk. This is typically the longest single phase of the migration.

4. Custodian integration re-establishment. If your firm has active data feeds from Schwab, Fidelity, Pershing, or SEI flowing into AdvisorEngine, those pipelines terminate when you leave. folk has no custodian integrations. You'll need a separate portfolio management or reporting tool to receive custodian data, plus a Zapier/Make bridge to sync relevant client data back into folk.

5. Compliance audit trail continuity. AdvisorEngine's action log is designed for SEC/FINRA audit readiness. folk's interaction history is not. Before migrating, confirm with your compliance officer or CCO that the historical action log export (CSV) meets your firm's record-retention requirements as an archive. Some firms maintain read-only AdvisorEngine access for 3–7 years post-migration specifically for audit defensibility.

What a "Structurally Wrong" Migration Looks Like

The warning below references migrations that finish with a green success message but are structurally incorrect. Here's what that means in practice:

A flat Company → Record and Person → Person import can complete without row-level errors but still produce unusable data. The most common failure: contacts imported as standalone Records with no Person linkage, creating 2,000 Records with zero Persons instead of 1,000 Records with 2,000 Persons distributed across them. The import tool reports 2,000 successful imports. But every workflow, report, and compliance action in AdvisorEngine expects the Record → Person relationship to exist. Advisors can't log Actions against Persons who aren't linked to Records. Revenue and AUM data can't be attributed. The CRM looks populated but is functionally broken.

Validation methodology we use: After import, run a count query comparing total Records to total Person linkages. If the ratio is 1:0 or 1:1 across the board (rather than the expected ~1:1.6 for a typical RIA household book), the hierarchy construction failed. Cross-reference a random 5% sample of Records against the source data to verify Person assignments, Action counts, and custom field mapping. Budget 2–4 weeks for a clean migration with validation, not 2–4 days.

Migration Case Reference

In a recent engagement, we migrated a 14-person RIA from folk CRM to AdvisorEngine CRM. The firm had approximately 3,800 contacts in folk across 6 groups, with ~$420M in AUM tracked via custom fields. Key outcomes:

• Household construction required a supplementary mapping spreadsheet built from shared addresses and a custom "household" tag the firm had inconsistently applied. Approximately 22% of contacts required manual household assignment because automated grouping logic produced false positives (e.g., two clients at the same commercial address who were not in the same household).
• Action history covered ~11,000 interactions extracted via folk's API. Classification into AdvisorEngine's action taxonomy took 3 days of scripted mapping plus 2 days of manual review for edge cases.
• Documents were stored in Google Drive, not folk. Linking ~2,400 files to the correct AdvisorEngine Records was a parallel workstream that ran for 2 weeks.
• Total elapsed time: 6 weeks from scoping to validation sign-off. The firm ran both systems in parallel for 3 weeks during the transition.
• Post-migration issues found during validation: 47 Records with incorrect Person linkages (1.2% error rate), 3 custom fields that lost decimal precision during type conversion, and 12 Actions with truncated notes exceeding AdvisorEngine's field character limit.

Switching Costs and Vendor Lock-In

folk CRM's lock-in risk is low. The data model is simple, CSV exports are available, and the API (on Premium) supports full extraction. The main switching cost is rebuilding any Zapier/Make automations you've built around folk.

AdvisorEngine CRM's lock-in risk is moderate to high. The lack of a public API means you're dependent on native export tools that flatten relational data and exclude documents. Custodian integrations create functional lock-in — your data pipelines from Schwab, Fidelity, or Pershing will need to be re-established on whatever platform you migrate to. Database export, record/person reconstruction, documents, assets, revenue, and workflow context all live on separate rails.

If you're planning a cutover from AdvisorEngine, strongly consider a parallel-run approach.

What Does folk CRM vs AdvisorEngine CRM Actually Cost?

folk CRM uses transparent per-seat pricing. AdvisorEngine CRM uses a single-tier model with a minimum seat requirement. The sticker prices are closer than you'd expect, but the TCO diverges based on team size and required feature tier.

folk CRM Pricing (as of mid-2025)

folk CRM pricing starts at $24/user/month (billed annually) or $30/user/month (billed monthly) for the Standard plan. The Premium plan costs $48/user/month annually or $60/user/month. Custom plans start at $80/user/month annually with tailored features.

Hidden cost drivers:

• Deal management is gated behind Premium, and the price doubles the moment you need core sales features.
• Zapier/Make subscriptions add $20–$100+/month depending on automation volume
• Enrichment credits are shared workspace-wide on Standard: 500 credits per month for the entire team, not per user.
• API access requires Premium — Standard users have no programmatic access

Team Size	Standard (Annual)	Premium (Annual)
5 users	$1,440/year	$2,880/year
10 users	$2,880/year	$5,760/year
20 users	$5,760/year	$11,520/year
25 users	$7,200/year	$14,400/year

AdvisorEngine CRM Pricing

$69 per user, per month, billed annually, with access to all features, priority support, and unlimited document storage. Minimum three users. This pricing is published on AdvisorEngine's website (advisorengine.com/crm, accessed June 2025).

Team Size	Annual Cost
3 users (minimum)	$2,484/year
5 users	$4,140/year
10 users	$8,280/year
20 users	$16,560/year
25 users	$20,700/year

The Real TCO Comparison

AdvisorEngine includes all features at a single price point — no tier-gating. The CRM includes unlimited data storage, a powerful workflow engine, and industry-leading tech support provided without any risk of additional costs or upcharges.

folk requires Premium ($48/user/month) to access API, deals, and sequences — so the realistic comparison for a team that needs more than basic contact management is $48 vs. $69 per user.

At 10 users on folk Premium, you're at $5,760/year. At 10 users on AdvisorEngine, you're at $8,280/year — a $2,520/year difference. But folk doesn't include document storage, custodian integrations, or compliance workflows. For wealth management firms, AdvisorEngine's bundled capabilities eliminate costs that would otherwise require separate middleware.

At 25 seats, the math is $14,400/year (folk Premium) vs. $20,700/year (AdvisorEngine). If you need folk's Custom/Enterprise controls, the published floor rises to $24,000/year at 25 seats.

For mid-market non-RIA teams, folk is the cheaper and less risky bet. For RIAs, AdvisorEngine's higher seat price often still wins because it avoids rebuilding advisor workflows in a generalist CRM.

How Do folk CRM and AdvisorEngine CRM Compare on Security and Compliance?

AdvisorEngine CRM is designed for SEC-regulated environments. folk CRM is designed for general business use. The compliance postures reflect these different audiences.

folk CRM Security

folk publicly states SOC 2 Type 1 certification and indicates it is pursuing SOC 2 Type 2 (no completion date published as of June 2025). folk has SOC 2 and GDPR compliance. The platform publishes a GDPR statement and notes that EU/UK data may be stored in the United States under the EU-US Data Privacy Framework. Data is encrypted at rest and uses secure protocols in transit. SSO is available via Google and Microsoft. Role-based access controls are available on Premium and above.

What folk does not publicly document:

• No published ISO 27001 certification
• No documented audit log functionality for compliance-oriented firms (admin audit logs reportedly available under NDA)
• 2FA and IP restriction features are not prominently documented in public help center materials

AdvisorEngine CRM Security

AdvisorEngine provides enhanced login security features such as two-factor authentication, IP restriction, and security question maintenance.

Administrators can manage which areas and features each user/user group has access to and easily apply data entitlements to control information access and action across your firm.

The help center (help.advisorengine.com) documents enterprise firewalls, SSL-encrypted session traffic, SSAE 16 Type II SOC 1 hosting facilities, audit logs for table changes and login history, MFA, password rotation, banned-password lists, IP allowlists, and configurable inactivity logoff. As a Franklin Templeton subsidiary serving RIAs managing billions in assets, AdvisorEngine operates under the compliance and security standards expected of financial services infrastructure.

Security Feature	folk CRM	AdvisorEngine CRM
SOC 2	Type 1 (pursuing Type 2, no date published)	Expected (Franklin Templeton subsidiary)
GDPR	Yes	Not prominently marketed (US-focused)
2FA	Not documented publicly	Yes
IP restriction	Not documented publicly	Yes
Role-based access	Premium+ only	All users
Audit logs	Not documented publicly	Action-level audit trail
Field-level access control	Not available	Granular by user group
SEC regulatory alignment	Not applicable	Designed for it

Verdict: If you're in a regulated financial services environment, AdvisorEngine's security and admin tooling is materially ahead. For general B2B use, folk's SOC 2 and GDPR posture is adequate.

How Do the Integration Ecosystems and Developer Experience Compare?

folk CRM's integration strategy is breadth via Zapier/Make and a public API. AdvisorEngine CRM's integration strategy is depth via custodian and fintech partnerships. Neither has a general-purpose app marketplace.

folk CRM Integrations

Folk CRM supports over 5,000 integrations on its pricing page. After research, they natively integrate only with Gmail, Outlook, LinkedIn, and WhatsApp. All of the other 4,900+ integrations and third-party apps are through Zapier or Make.com.

The public developer portal at developer.folk.app provides REST API documentation, webhooks for real-time notifications, and published rate limits. The API covers contacts, companies, deals, groups, users, notes, reminders, interactions, and webhooks — though the Interactions API is still in private beta (as of June 2025).

Where folk starts to feel limited is when your operations grow and you need your CRM to actually talk to your other tools in any meaningful way. Their API is fairly light, so if you're planning to build integrations with your accounting software or automate workflows beyond basic email sequences, you will likely feel limited.

AdvisorEngine CRM Integrations

AdvisorEngine is a pioneer in full integration with the largest custodians including Schwab, Fidelity, TD Ameritrade, Pershing, and SEI.

The platform offers a variety of integrations across functions including Constant Contact, Office 365, eMoney, Riskalyze, and many more.

The integration list extends to wealth-management-specific tools: Orion, Tamarac, MoneyGuide, PreciseFP, Docupace, Laser App, Laserfiche, MyRepChat, and DocuSign. These integrations are narrow but deep — built for the wealth management tech stack specifically. You won't find Slack, Notion, or Shopify integrations here.

Zapier support exists for AdvisorEngine, but the trigger/action set is narrower and centered on prospects, households, opportunities, and contact updates. There is no public developer portal comparable to folk's.

API Developer Experience

API Factor	folk CRM	AdvisorEngine CRM
Public REST API	Yes (Premium+ only)	No public API
Authentication	Bearer token (API key)	N/A
Webhooks	Yes	N/A
Rate limits	600 req/min per user	N/A
Bulk operations	Limited	N/A
Developer docs	developer.folk.app	N/A

folk has a clear advantage for teams that want to build custom integrations. AdvisorEngine relies entirely on its pre-built partnerships and native export tools for data movement.

Choose folk CRM If… / Choose AdvisorEngine CRM If…

Do not choose a CRM based on UI aesthetics or demo quality. Choose it based on whether the data model matches your business.

Choose folk CRM if:

• You're a team of under 50 people in agencies, VC, recruiting, or SaaS sales
• Your prospecting starts on LinkedIn and you need one-click contact capture
• You want a CRM running in under an hour with minimal configuration
• You value API access and plan to build custom integrations via REST
• You don't need household hierarchies, custodian integrations, or compliance-grade audit logs
• You want to keep software overhead under $50/user/month

Choose AdvisorEngine CRM if:

• You're a registered investment advisor (RIA) or wealth management firm
• You need native integrations with Schwab, Fidelity, Pershing, or SEI
• Your compliance workflow requires structured action logging tied to client households
• You store client documents (IPS, KYC, financial plans) inside the CRM
• You need role-based data entitlements, 2FA, and IP restriction out of the box
• You manage complex household hierarchies, not simple B2B accounts

These tools don't compete with each other. They serve entirely different markets. The question isn't which is "better" — it's which matches your operational reality. The wrong choice in either direction shows up later as migration cost, workflow friction, and reporting noise.

If you're planning a migration between folk CRM and AdvisorEngine CRM — in either direction — the data model transformation is the hardest part. Underestimating the structural gap between flat and hierarchical data models is the #1 cause of migration failures in cross-platform CRM moves.

Sources and Access Dates

• folk CRM Help Center: help.folk.app (accessed June 2025)
• folk Developer API Documentation: developer.folk.app (accessed June 2025)
• folk CRM Pricing Page: folk.app/pricing (accessed June 2025)
• AdvisorEngine CRM Help Center: help.advisorengine.com (accessed June 2025)
• AdvisorEngine CRM Pricing: advisorengine.com/crm (accessed June 2025)
• AdvisorEngine CRM Product Page: advisorengine.com (accessed June 2025)