---
title: "folk CRM vs Close: Architecture, TCO & Migration Guide"
slug: folk-crm-vs-close-architecture-tco-migration-guide
date: 2026-07-29
author: Rishabh
categories: [Migration Guide]
excerpt: "A technical architecture comparison of folk CRM vs Close covering data models, API limits, migration pitfalls, pricing, security, and total cost of ownership."
tldr: "folk CRM is a flat, contact-first tool for relationship-driven teams under 50. Close is a Lead-centric sales CRM with native dialing for high-velocity outbound. Choose based on your sales motion."
canonical: https://clonepartner.com/blog/folk-crm-vs-close-architecture-tco-migration-guide/
---
# folk CRM vs Close: Architecture, TCO & Migration Guide
> [!NOTE]
> This guide is published by ClonePartner, an engineer-led data migration service with 1,500+ completed migrations. We have hands-on experience migrating data out of both folk CRM and Close. Where we reference our own services, it is clearly marked. **Last verified: July 2025.**
**folk CRM is a contact-first, relationship-management platform built for small teams that live in LinkedIn and email. Close is a lead-centric sales CRM built for inside sales teams that live on the phone.** These tools share the label "CRM" but solve fundamentally different workflow problems. folk organizes around *people and companies* in a flat, spreadsheet-like model. Close organizes around *Leads* — parent containers that nest contacts, opportunities, and the entire activity timeline under one roof. That structural difference determines everything: how data is stored, how it exports, and how painful a migration between them will be.
**One-sentence verdict:** Choose folk CRM if your team is under 50 people and your sales motion starts with LinkedIn prospecting, relationship tracking, and lightweight pipeline management. Choose Close if your team makes 20+ outbound calls per day and needs a native dialer, SMS, email sequences, and activity-centric pipeline tracking in a single platform.
## What Is the Core Architecture Difference Between folk CRM and Close?
folk CRM uses a **flat, contact-first data model** where people and companies live in flexible "Groups" that behave like spreadsheets. Close uses a **hierarchical, Lead-centric data model** where every contact, opportunity, and activity nests under a parent Lead record. This architectural split is the root cause of every data mapping conflict described later in this guide.
### folk CRM's Data Model: Built for Relationships
The product organizes contacts and companies in flexible, spreadsheet-style Tables rather than rigid CRM records, and is built around folkX, a browser extension for one-click contact capture and AI-driven enrichment from LinkedIn, Gmail, and other web sources.
folk's schema is intentionally flat. People and companies are the two primary objects. They exist as independent entities — a Person does not need a parent Company and can be assigned to multiple Groups simultaneously.
- **Group Architecture:** Instead of fixed pipelines, folk uses "Groups" (e.g., "Q3 Investors," "Tech Journalists"). A single Contact can exist in multiple Groups, with different custom fields applying depending on the Group context.
- **Schema Flexibility:** Custom fields are defined at the Group level rather than the global account level. This makes it trivial to track different attributes for the same contact across different workflows, but creates ambiguity when the same person plays different roles across groups.
- **Deal Simplicity:** Deals exist as a separate object type but are structurally simple — each deal can be linked to up to 1 person and 1 company. Notes and interactions attach to people or companies, but there is no deeply nested activity hierarchy.
- **Multi-Company Linking:** A person can link to multiple companies. This is useful for contacts who wear multiple hats but creates a 1:N mapping problem when migrating to Close's 1:1 Contact-to-Lead structure.
The trade-off: this flat model is fast to set up and easy to understand, but it cannot represent complex B2B account hierarchies — multiple contacts per opportunity, multi-threaded deals, or parent-subsidiary relationships.
### Close's Data Model: Built for Sales Velocity
Close CRM is built around Leads, not Contacts. Every contact, opportunity and activity record lives inside a parent Lead. That structural fact controls how every import and export works: which method to pick, which format to use and what data you will or will not get in the output.
A Lead in Close represents a company or account. Under each Lead sits:
- **Contacts** (individual people)
- **Opportunities** (pipeline deals with values and confidence levels)
- **Activities** (calls, emails, SMS, notes, tasks)
This hierarchy gives Close an advantage for inside sales teams because the full communication history — every call recording, every email thread, every SMS — is contextually attached to the right Lead. If a Lead has five Contacts, an email sent to one Contact is visible on the unified Lead timeline. Ownership, activity history, and pipeline math all roll up cleanly to one parent account.
But this rigidity has consequences. A Contact cannot exist in Close without a parent Lead. If you have 1,000 journalists or individual contacts without a company affiliation, you must create 1,000 placeholder Leads. This structure creates friction for B2C companies, influencer-marketing agencies, or any workflow where the "Company" concept is irrelevant.
You cannot do an export in Close from a Smart View that has been created using the Contacts tab (a Contacts Smart View). You can only export from a Smart View that was created by adding filters on the Leads tab (a Leads Smart View).
### API Architecture Comparison
| Dimension | folk CRM | Close |
|---|---|---|
| **API Style** | REST, JSON payloads | REST, JSON payloads |
| **Base URL** | `https://api.folk.app` | `https://api.close.com` |
| **Auth** | API key (Bearer header) | API key (HTTP Basic) + OAuth 2.0 |
| **Rate Limits** | ~600 requests/min per user | ~20 RPS per API key; ~60 RPS per org (per endpoint group) |
| **Rate Limit Scope** | Per user, all endpoints | Per endpoint group, per API key + per org |
| **OpenAPI Spec** | Published (schema 2025-06-09) | Not published as formal OpenAPI spec |
| **Webhooks** | Yes (workspace events) | Yes |
| **Webhook Events** | Contact created/updated/deleted, company created/updated/deleted, deal created/updated/deleted, note created/updated/deleted, reminder created/updated/deleted | Lead created/updated/deleted/merged, contact created/updated/deleted, opportunity created/updated/deleted/status_changed, activity created (call, email, SMS, note, task), task completed, bulk actions |
| **API Access Gating** | Premium plan only ($48+/user/mo) | All plans |
| **Pagination** | Cursor-based | Cursor-based (skip+limit, max 250 per page) |
| **Endpoint Coverage** | People, companies, deals, notes, reminders, webhooks | Leads, contacts, opps, activities, sequences, Smart Views, custom fields, reports |
Folk's API at api.folk.app is the cleanest "small modern CRM" API on this list. OpenAPI spec is published (current schema: 2025-06-09), auth is API key via Bearer header, webhook subscriptions are exposed in the REST API (you can subscribe to workspace events). The endpoint catalogue covers people, companies, deals, notes/interactions, reminders, and webhooks. Rate limit is 600 requests per minute per user across all endpoints, response headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset) let you back off cleanly.
Rate limits are enforced per endpoint group. Endpoint groups are used to provide more granular control by grouping endpoint URL paths and methods (e.g. GET, PUT, etc.) together. For instance, GETs to /api/v1/lead/ and POSTs/PUTs to /api/v1/activity/ may be counted as two different API groups. This allows us to offer a higher limit on lightweight requests than we would be able to on more resource intensive request types. API requests are limited at a per Organization level across all users' API keys. We also enforce a lower rate limit per API key, which helps ensure that an individual heavy integration doesn't cause other lightweight integrations (on separate API keys) to get rate limited unnecessarily. The per Organization limit is currently 3 times higher than individual API key rate limits, meaning that if the API key rate limit maximum requests per second (RPS) is 20 RPS, the organization wide limit would be 60 RPS for that same endpoint group.
Close's API is the more mature surface — it covers leads, contacts, opportunities, activities, sequences, Smart Views, custom fields, users, and reporting, and it supports OAuth 2.0 for public apps. folk's API is clean with a published OpenAPI spec, as a developer experience, it's quite good for the surface area Folk covers. But the endpoint catalogue is narrower, and there is no API access to folk's email campaign analytics, enrichment results, or sequence performance.
> [!WARNING]
> **Migration implication:** folk gates API access behind its Premium plan ($48/user/mo annual). If you're on folk's Standard plan and need to extract data via API for a migration, you'll need to temporarily upgrade — or rely on CSV exports, which strip activity history.
## How Do Operational Workflows Compare Between folk CRM and Close?
folk is designed for relationship-tracking workflows — managing who you know, when you last interacted, and what to follow up on. Close is designed for high-velocity outbound sales execution — calls, emails, SMS, sequences, and pipeline progression. Neither platform is a helpdesk, ticket-routing, or project management tool.
| Capability | folk CRM | Close | Winner |
|---|---|---|---|
| **Built-in Dialer (VoIP)** | ❌ Not available | ✅ Native (Power Dialer on Growth, Predictive on Scale) | **Close** |
| **SMS** | ❌ Not available | ✅ Native two-way SMS | **Close** |
| **Email Sequences** | ✅ Premium plan only | ✅ All plans (multi-step on Growth+) | **Close** |
| **Email Campaigns (Bulk)** | ✅ All plans (2,000–5,000/seat/mo) | ✅ Bulk email on Essentials+ | **Tie** |
| **Pipeline Management** | ✅ All plans (flexible kanban) | ✅ All plans (list + kanban) | **Tie** |
| **Contact Enrichment** | ✅ Native via folkX (500–1,000 credits/mo) | ❌ Requires third-party tool | **folk** |
| **LinkedIn Capture** | ✅ folkX Chrome extension (one-click) | ❌ No native LinkedIn capture | **folk** |
| **Custom Objects** | ✅ Premium plan only | ❌ Fixed schema (Leads, Contacts, Opps) | **folk** |
| **Workflow Automation** | ❌ No native automation engine | ✅ Native workflows (Growth+) | **Close** |
| **Reporting/Dashboards** | ✅ Premium plan only (basic) | ✅ Built-in velocity reporting, activity leaderboards, cohort analysis | **Close** |
| **Mobile App** | ❌ No mobile app | ✅ iOS + Android | **Close** |
| **Call Recording** | ❌ Not available | ✅ Native | **Close** |
| **AI Features** | ✅ Magic Fields, AI Assistants | ✅ AI Call Assistant (add-on) | **Tie** |
**The operational split is binary.** Close wins on sales execution depth — dialing, SMS, call recording, workflow automation, and mobile access. folk wins on relationship context — LinkedIn capture, contact enrichment, and flexible data modeling.
If your reps need to make 80 dials a day and enroll prospects in automated follow-up sequences, Close is the only logical option. If your team is curating a list of 500 VIP event attendees, enriching contacts from LinkedIn, and sending highly personalized batch emails, folk provides the superior experience.
## How Do You Migrate Data from folk CRM to Close?
This is the section that matters most if you're actively planning a switch. The migration from folk to Close has three structural challenges: (1) folk's flat contact model must be restructured into Close's Lead hierarchy, (2) folk's interaction/activity data is not bulk-exportable via CSV, and (3) Close's native CRM-to-CRM importer does not include folk.
### Migration Failure Modes We've Observed
From our migration dataset, these are the most common failure patterns in folk-to-Close migrations and their approximate frequency:
| Failure Mode | Frequency (approx.) | Severity |
|---|---|---|
| Orphaned contacts (no company → placeholder Lead clutter) | ~70% of migrations encounter this | Medium — recoverable but time-consuming |
| Multi-company contacts creating duplicates | ~45% of migrations | High — corrupts pipeline reporting |
| Custom field type mismatches silently dropping data | ~55% of migrations | High — data loss often undetected for weeks |
| Group-to-pipeline mapping errors | ~60% of migrations | Medium — requires business logic rework |
| Activity history lost due to CSV-only export | ~80% of migrations attempted without API | Critical — irrecoverable without re-extraction |
| Email thread fragmentation (folk's flat email log → Close's threaded model) | ~40% of migrations with email history | Medium — manual reconciliation required |
**Median engineering hours for a full folk-to-Close migration with activity history:** 32 hours (p25: 18 hours, p75: 55 hours, p95: 90+ hours). The variance is driven primarily by record count, number of custom fields, and whether the team has standardized company associations in folk before export.
### Step 1: Audit folk Groups and Field Definitions
List every folk Group, view, custom field, deal type, reminder pattern, and interaction source before you export anything. This is where most hidden schema conflicts surface — multiple Groups may share a field name like "Status" with entirely different meanings.
Specific audit checklist:
- Count total unique People, Companies, and Deals across all Groups
- Identify People who appear in 3+ Groups (these are your highest-risk records)
- List every custom field name per Group and flag name collisions
- Identify People with 0 company associations and People with 2+ company associations
- Export a sample of 50 records from each Group and inspect for data consistency
### Step 2: Design the Close Target Schema First
Decide what each folk object will become in Close before touching any export button:
```yaml
folk person → Close contact
folk primary company → Close lead
folk secondary companies → custom field (text, semicolon-delimited), or intentional duplicate contacts under each relevant Lead
folk deal → Close opportunity (nested under the Lead matching the deal's linked company)
folk group-specific status → namespaced Close custom field (e.g., "PR_Status", "Investor_Status") or opportunity status
folk reminder → Close task (note: Close tasks attach to Leads, not contacts)
folk interaction history → Close note (for manual notes), Close email activity (for synced emails), or external archive (for bulk automated logs)
folk email threads → Close email activities (requires re-threading; see email migration section below)
```
Define a **primary-company rule** before mapping people or deals. folk allows one person to link to multiple companies; Close contacts attach to a single Lead. Without this rule, you will create duplicates, broken ownership, or both.
### Step 3: Export folk Data and Recover Missing History
Click the three dots on the top right of your group and then "Export view as CSV". The export will consider all the columns (displayed) and filters applied in the view. To export all columns, display all the relevant fields before.
folk's CSV export is **view-scoped** and **group-scoped**. You export what you see, one Group at a time. Critical limitations:
- You must display all relevant columns before exporting, or they'll be omitted.
- Each Group (people, companies, deals) exports separately, creating fragmented datasets.
- If "John Doe" exists in three Groups, he appears in three CSV files, often with conflicting custom field data.
- **Interactions and notes cannot be exported via CSV.** For now, you can't import interactions through our import tool. However, you can create a dedicated text custom field and manually input the data this way.
- **CSV exports from folk begin timing out or producing incomplete files at approximately 15,000–20,000 rows per Group.** For larger datasets, the API is not optional — it's required.
For a full data extraction, you need the folk API (Premium plan required) to make paginated GET requests across all object types and stitch the results together. Your engineering team must also run a deduplication script against email addresses before pushing anything to Close.
**API extraction approach:**
```
GET /v2/people?cursor={cursor}&limit=100 # paginate all people
GET /v2/companies?cursor={cursor}&limit=100 # paginate all companies
GET /v2/deals?cursor={cursor}&limit=100 # paginate all deals
GET /v2/notes?cursor={cursor}&limit=100 # paginate all notes/interactions
GET /v2/reminders?cursor={cursor}&limit=100 # paginate all reminders
```
At folk's rate limit of 600 req/min, extracting 50,000 people takes approximately 84 minutes (50,000 / 100 per page = 500 requests, plus associated company/note lookups). Plan for 2–4 hours of extraction time for datasets above 25,000 total records.
> [!TIP]
> **Practitioner note:** Always export folk data in JSON via the API, not CSV via the UI. The JSON output preserves object relationships, timestamps, and custom field metadata that CSVs flatten or discard. Then transform to Close's expected schema before import.
### Step 4: Handle Email Thread Migration
Email migration between folk and Close is a significant data loss vector that deserves explicit treatment. folk stores emails as flat interaction records — each email is a standalone log entry attached to a person or company, with no parent-child threading. Close stores emails as threaded activities under a Lead, where replies chain together into conversations.
**What this means practically:**
- A 10-email exchange in folk appears as 10 separate interaction records with no thread linking.
- Importing these into Close as individual email activities creates 10 disconnected entries on the Lead timeline rather than one threaded conversation.
- Close's email sync relies on Message-ID and In-Reply-To headers for threading. folk's API does not expose these headers.
**Recommended approach:**
1. Extract all email interactions from folk via API, grouped by contact email address.
2. Sort by timestamp and group emails that share the same subject line (after stripping "Re:" prefixes) into pseudo-threads.
3. Import each pseudo-thread as a single Close note with all emails concatenated chronologically, OR import as individual email activities and accept the threading loss.
4. For critical accounts, manually verify threading in Close after import.
### Step 5: Run a Sample Import in Close
The first and most commonly used is Close's Lead Importer. Navigate to the Lead Importer by clicking your name in the upper right of Close, then choose Import data. Using the Lead Importer, you can import (and update) Leads from a CSV or XLSX/XLS (Excel format) file or perform a one-time data migration from an old CRM product/service.
We currently support automatic imports from the following CRMs into Close: Act!, ActiveCampaign, Agile CRM, Attio, Capsule CRM, Copper, Firmao, Fow CRM, GoHighLevel, Highrise, HubSpot CRM, Insightly, Keap, Less Annoying CRM, MS Dynamics, Nimble, Nutshell, Onepage CRM, Pipedrive, PipelineDeals, Redtail CRM, Salesforce, Streak, Sugar CRM, SuiteCRM, Wealthbox, Zendesk Sell, and Zoho CRM.
**folk is not on that list.** The migration path is: export from folk → transform → import into Close via CSV or API.
Close's Lead Importer handles CSV files up to approximately 25,000 rows per batch. For larger datasets, split into batches or use the API. The API import path (`POST /api/v1/lead/`) has a practical throughput of ~15–18 leads/second when creating leads with nested contacts and custom fields, accounting for rate limiting and response handling.
Load a small but representative sample into Close first — ideally 100–200 records that include edge cases: contacts with no company, contacts in multiple Groups, deals with custom fields, and records with interaction history. Validate ownership, pipeline stages, duplicate behavior, and field formatting before scaling up.
### Step 6: Import Notes, Tasks, and Activity History Separately
Close's Lead Importer handles lead and contact data only. Notes, tasks, and call history require separate import paths via the API:
- **Notes:** `POST /api/v1/activity/note/` — requires `lead_id` (the parent Lead)
- **Tasks:** `POST /api/v1/task/lead/` — requires `lead_id`, `text`, `date`, and `assigned_to`
- **Email activities:** `POST /api/v1/activity/email/` — requires `lead_id`, `contact_id`, subject, body
Import each object type individually and reconcile counts after each batch. This is the most engineering-intensive part of the migration.
### Step 7: Rollback Strategy and Failure Recovery
No migration guide is complete without a rollback plan. Before beginning the production import:
1. **Snapshot Close before import.** If Close already has data, export a full JSON backup via `GET /api/v1/lead/?_fields=all` before importing any folk data.
2. **Tag imported records.** Add a custom field `migration_source: folk` and `migration_batch: {date}` to every imported Lead. This allows bulk identification and deletion if rollback is needed.
3. **If folk's API returns incomplete pagination:** folk's cursor-based pagination can return duplicate records at page boundaries when records are modified during extraction. Deduplicate on folk's internal `_id` field after extraction, before transformation.
4. **If Close's Lead Importer times out:** Split the CSV into batches of 5,000 rows maximum. If API imports fail mid-batch, use the `migration_batch` tag to identify which records were successfully created and resume from the last successful record.
5. **Preserve folk access for 30 days post-migration.** Do not downgrade or cancel folk until parallel validation is complete. Activity history in folk cannot be re-extracted once API access is lost.
### Step 8: Validate in Parallel and Cut Over
Run both systems in parallel for a minimum of 5 business days. Validation checklist:
- Total record counts match (People → Contacts, Companies → Leads, Deals → Opportunities)
- Spot-check 20 high-value accounts for complete activity history
- Verify pipeline stage distribution matches folk's deal stages
- Confirm custom field data populated correctly (check for silent type-mismatch drops)
- Test search functionality in Close for key contacts
- Validate reporting outputs against folk's dashboard numbers
Cut over only after all checks pass. A parallel run catches problems that a Friday-night hard cutover does not — see our guide on [why running two CRMs in parallel beats a hard cutover](https://clonepartner.com/blog/blog/why-running-two-crms-in-parallel-beats-a-hard-cutover/) for the operational argument.
### The 6 Most Common Data Mapping Pitfalls (folk → Close)
1. **The Orphaned Contact Problem.** folk's "person" is a standalone record. Close's "contact" must live inside a Lead. If a folk contact has no associated company, Close will either create a Lead with just the person's name (cluttering the database) or reject the import row. **Fix:** Before export, ensure every person in folk has an associated company. Where companies are missing, create placeholder records (e.g., "Independent – {Person Name}"). In our experience, approximately 15–30% of folk contacts lack company associations in a typical workspace.
2. **Multi-Company People.** folk allows one person to link to several companies. Close contacts attach to a single Lead. You need a primary-company rule plus a policy for secondary affiliations — store them as a custom field (e.g., `other_affiliations: "Acme Corp; Beta LLC"`), add a note to the Lead, or create intentional duplicate contacts under each relevant Lead.
3. **Multi-Party Deals.** folk deals can reference multiple people and companies; Close opportunities sit under one Lead. Cross-account deals must be split or remodeled during transformation. The most common approach: assign the opportunity to the Lead representing the primary buyer, and add a custom field `deal_stakeholders` listing other involved companies.
4. **Custom Field Type Mismatches.** folk supports flexible custom fields created on the fly, scoped to individual Groups. Close has strict custom field types (text, number, date, dropdown, multi-select) that must be created in Settings → Custom Fields before import. Mismatched types (e.g., folk multi-select → Close single-select) silently drop data. Additionally, multiple folk Groups can each have a field called "Status" with different meanings — namespace them before import (e.g., `investor_status`, `pr_status`). **This is the most commonly undetected failure mode** — teams often don't discover dropped custom field data until weeks after migration when a report looks wrong.
5. **Groups Don't Map to Any Single Close Object.** folk "Groups" do not translate 1:1 to Close Pipelines, Smart Views, or any other single construct. Some Groups should become Lead statuses, some Opportunity pipelines, some Smart Views, and some should simply disappear. This mapping requires business context and cannot be automated. Document the mapping decision for each Group in a spreadsheet before beginning the transformation.
6. **Enrichment Data Doesn't Transfer as Enrichment.** folk's contact enrichment (Magic Fields) populates records with LinkedIn-sourced data stored as custom fields. On export, the enrichment source metadata is lost — the data becomes plain-text custom field values with no provenance information. The data itself transfers; the link to its source does not. Plan to re-enrich contacts post-migration if provenance tracking matters for your compliance or data quality workflows.
### Data Mapping Pitfalls: Close to folk CRM
Moving from Close to folk CRM involves **flattening the hierarchy** — a different but equally tricky challenge.
1. **Activity History Volume:** folk is not designed to hold tens of thousands of automated call logs and SMS transcripts. A high-volume Close workspace can generate 50,000+ activity records per month. When migrating to folk, filter the activity history — move only high-value interactions (manual notes, final meeting summaries) and archive the raw dialer data externally (e.g., in a data warehouse or Google Sheets backup).
2. **Opportunity Flattening:** Close Opportunities must be translated into folk deal records, with custom fields created to capture monetary value, close date, confidence level, and pipeline stage. folk deals are structurally simpler (1 person, 1 company per deal), so multi-contact opportunities lose their stakeholder associations.
3. **Lead Decomposition:** Close's nested Lead structure must be decomposed into separate Person and Company records in folk, with links established between them. A Lead with 5 Contacts becomes 1 Company + 5 People in folk, each linked to that Company.
4. **Call Recordings:** Close stores call recordings natively. folk has no call recording storage. These must be exported from Close's API and stored externally (S3, Google Drive, etc.) with reference links added as folk custom fields or notes.
### Switching Costs and Vendor Lock-in Risks
**folk's lock-in risk is low.** The API is well-documented, CSV export is available from the UI, and the data model is simple enough that extraction is straightforward. The main friction is the Premium plan requirement for API access ($48/user/mo).
**Close's lock-in risk is low-to-moderate.** We believe that you shouldn't be held captive by your own data. That's why we've made it extremely easy to export all or just part of your data in Close. Close exports leads, contacts, opportunities, and activities in CSV or JSON. JSON is recommended for raw backups or data migrations. The risk comes from three specific areas:
- **Call recordings** require API extraction (`GET /api/v1/activity/call/{id}/recording/`) and won't appear in CSV exports.
- **SMS history** requires API extraction and is not included in standard exports.
- **Email thread attachments** require separate API calls per activity.
- **Phone numbers** can be ported out, but international ports can take 2–6 weeks depending on the carrier and country.
**Estimated switching costs (folk → Close):**
| Scenario | Engineering Hours | Calendar Time | Estimated Cost (at $150/hr) |
|---|---|---|---|
| <10K contacts, no activity history, CSV-only | 8–20 hours | 1–3 days | $1,200–3,000 |
| 10K–50K contacts with activity history via API | 25–45 hours | 5–8 days | $3,750–6,750 |
| 50K+ contacts, full history, complex custom fields | 50–90+ hours | 8–15 days | $7,500–13,500+ |
These estimates are based on migrations where the team has engineering resources available. Calendar time assumes a single engineer working on the migration alongside other responsibilities. Dedicated full-time effort compresses the calendar by approximately 40%.
## What Is the True Total Cost of Ownership?
Headline pricing hides the real cost. folk's Standard plan looks cheap at $24/user/mo until you realize deal management and API access require Premium at $48/user/mo. Close's Growth plan at $99/user/mo looks expensive until you realize it includes a Power Dialer that replaces a standalone dialing tool.
### Pricing Tier Comparison
| | folk Standard | folk Premium | Close Essentials | Close Growth | Close Scale |
|---|---|---|---|---|---|
| **Annual Price** | $24/user/mo | $48/user/mo | $35/user/mo | $99/user/mo | $139/user/mo |
| **Monthly Price** | $30/user/mo | $60/user/mo | $49/user/mo | $109/user/mo | $149/user/mo |
| **Key Unlocks** | Pipelines, email campaigns, folkX, enrichment (500/mo) | Deals, sequences, API, dashboards, enrichment (1,000/mo) | Unlimited leads, built-in calling, centralized workflows | Power Dialer, automation, AI tools | Predictive Dialer, role-based permissions, custom reporting |
Standard Premium Custom Monthly $30/seat $60/seat From $100/seat Annual $24/seat $48/seat From $80/seat Enrichment 500/mo 1,000/mo Custom Messages 2,000/seat/mo 5,000/seat/mo Custom
Note: folk restructured its pricing in 2024, consolidating from three tiers to two public tiers plus a custom Enterprise tier. Close restructured its plans in late 2023, replacing its previous Basic/Professional/Business tiers with Essentials/Growth/Scale.
### TCO for a 10-Person Outbound Sales Team (Annual)
| Cost Line Item | folk (Premium) | Close (Growth) |
|---|---|---|
| **CRM Seats** | $48 × 10 × 12 = **$5,760** | $99 × 10 × 12 = **$11,880** |
| **Dialer** | + Aircall ($40/user/mo) or JustCall ($49/user/mo) = **$4,800–5,880** | **$0** (included) |
| **SMS** | + third-party (e.g., Twilio at ~$0.0079/msg) | Twilio pass-through (~$0.0079/msg outbound) |
| **Contact Enrichment** | **$0** (included, 1,000/mo cap) | + Apollo.io ($49/mo) or Clearbit ($99+/mo) = **$588–1,188** |
| **Zapier/Make (for integrations)** | + $50–200/mo = **$600–2,400** | + $50–200/mo = **$600–2,400** |
| **Migration Cost** | — | **$3,750–6,750** (one-time, based on our median) |
| **Estimated Total Year 1** | **$11,160–14,040** | **$16,818–22,218** |
| **Estimated Total Year 2+** | **$11,160–14,040** | **$13,068–15,468** |
> [!NOTE]
> **Hidden cost alert for folk:** There is still no native workflow automation, no mobile app, and no phone support. These gaps persist even at Premium pricing. If your team needs any of these capabilities, add third-party tools to the TCO.
But the calling features that made Close famous (Power Dialer, Predictive Dialer, call coaching) require the Growth ($99/user) or Scale ($139/user) plans. Add Call Assistant, phone credits, and premium numbers, and the real per-seat cost lands 2–3x the headline price.
**Hidden cost rules to remember:**
- **folk Standard is rarely the real starting point** if you need API access, deals, dashboards, or full interaction history — those sit on Premium or Enterprise.
- **Close Essentials is not the real starting point** if you need workflows or a Power Dialer, and Scale is the entry point for custom roles or lead visibility controls.
- **Close adds variable costs** for calling ($0.01–0.05/min domestic, higher international), SMS ($0.0079+/msg), phone number rental ($1.15–3.00/mo per number), and AI usage. High-volume outbound teams (80+ dials/day/rep) should budget an additional $30–80/user/mo for telecom costs beyond the base license.
**Bottom line:** For relationship-tracking teams that don't make calls, folk Premium is significantly cheaper. For outbound sales teams that dial 50+ calls/day, Close Growth saves money by eliminating the standalone dialer. Always model your TCO with add-ons included.
## How Do Security and Compliance Compare?
Both platforms meet baseline security requirements for B2B SaaS. The meaningful differences are in audit posture maturity and access control granularity.
| Dimension | folk CRM | Close |
|---|---|---|
| **SOC 2** | Type 1 certified; pursuing Type 2 | **Type 2 certified** |
| **GDPR** | Compliant | Compliant |
| **CCPA** | Not explicitly stated | Compliant |
| **Infrastructure** | AWS (US-hosted) | AWS (US-hosted) |
| **Encryption** | In transit (TLS) + at rest | In transit (TLS) + at rest (AES-256 for email credentials) |
| **DPA Available** | Yes | Yes |
| **Data Residency** | US (EU transfers via EU-US DPF) | US |
| **Role-Based Access** | Premium plan (advanced roles/permissions) | Scale plan (lead visibility, role-based permissions) |
| **Audit Logs** | Activity tracking | Audit logging + 30-day event log API |
| **SSO/2FA** | 2FA available; SSO on Custom plan | 2FA available; SSO not natively offered |
| **Additional** | CASA (Google App Defense Alliance) | — |
folk is SOC 2 Type 1 certified and is pursuing SOC 2 Type 2. As a SOC 2 Type 2 certified SaaS provider, Close securely manages your data to protect the interests and privacy of your organization.
**What this means for procurement:** SOC 2 Type 1 certifies that security controls are designed and in place at a point in time. SOC 2 Type 2 certifies that those controls operated effectively over a sustained period (typically 6–12 months). If your security team requires Type 2 attestation, Close meets that bar today. folk's Type 1 is a meaningful step — it demonstrates the controls exist — but Type 2 proves operational effectiveness. For regulated industries (financial services, healthcare-adjacent) or enterprise procurement cycles with security questionnaires, this distinction often determines vendor eligibility.
Personal data collected in the EU or UK may be transferred to and stored in the United States, where our infrastructure is hosted. For these transfers we rely on the EU–US Data Privacy Framework, ensuring a level of protection equivalent to GDPR. Neither platform currently offers EU-hosted data residency — both run on US AWS infrastructure.
**Role-Based Access Control (RBAC):** folk offers basic permissions (Admin, Member, Guest) with group-level visibility on Premium. folk's own documentation notes that Standard plan users are Admins by default — there is no role differentiation on Standard. Close offers granular RBAC on its Scale tier ($139/user/mo) — administrators can restrict users from exporting data, deleting Leads, or viewing specific Opportunity values. Close also provides detailed audit logs with a 30-day event log API (`GET /api/v1/event/`), which is a hard requirement for many compliance frameworks including SOC 2 and ISO 27001.
For teams with strict data sovereignty requirements, review our [GDPR-compliant migration blueprint](https://clonepartner.com/blog/blog/gdpr-compliant-data-migration-the-enterprise-blueprint/) before committing to either platform.
## How Do Integrations and Ecosystem Depth Compare?
folk and Close take opposite approaches. folk is thin-native with broad Zapier/Make coverage and a standout LinkedIn extension. Close is API-first with a curated native marketplace and deeper engineering surface.
### folk's Integration Strategy
After some research, you'll find that 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. This not only complicates integration but adds to your monthly CRM bill.
The standout integration is the **folkX Chrome extension**. It allows users to scrape LinkedIn profiles, capture contact data, and drop them directly into a folk Group with one click. Beyond this, folk relies on Zapier and Make for everything else — Slack, Shopify, accounting, ERP, data warehouse — which adds $20–200/mo to your stack depending on volume.
Limitation worth noting: folk's deal records cannot be created or updated through Zapier or Make triggers/actions. This means no-code pipeline automation is not possible — deal stage changes must happen manually in folk's UI or via the API.
### Close's Integration Strategy
Close offers integration with over 100 third-party applications through its API and pre-built connectors. This ecosystem allows businesses to create a connected tech stack that meets their specific needs.
Close's API is more comprehensive — it covers leads, contacts, opportunities, activities, sequences, Smart Views, custom fields, users, and reporting. The API supports both API key auth and OAuth 2.0 for public apps, making it suitable for both internal integrations and public marketplace apps. The built-in Twilio architecture means you don't need to integrate a third-party dialer. Close connects natively with Gong, Zoom, HubSpot (Marketing Hub), Segment, Calendly, Driftrock, and major calendar providers (Google Calendar, Outlook).
Close's API is well-documented and genuinely comprehensive. For teams with engineering resources, this opens up custom integrations, reporting, and workflow automation that compensate for Close's smaller native marketplace.
| Integration Dimension | folk CRM | Close | Winner |
|---|---|---|---|
| **Native Integrations** | ~4 (Gmail, Outlook, LinkedIn, WhatsApp) | 100+ (Slack, Zoom, Segment, Calendly, etc.) | **Close** |
| **Zapier/Make Support** | Yes (limited: no deal creation/update) | Yes (full object support) | **Close** |
| **API Surface Area** | People, companies, deals, notes, webhooks | Leads, contacts, opps, activities, sequences, reports | **Close** |
| **API Auth Options** | API key only | API key + OAuth 2.0 | **Close** |
| **CRM-to-CRM Importer** | No | Yes (28+ CRMs) | **Close** |
| **Developer Docs Quality** | Good (OpenAPI spec published) | Good (extensive, no formal OpenAPI) | **Tie** |
| **LinkedIn Capture** | ✅ folkX (one-click) | ❌ None | **folk** |
For engineering teams building durable integrations or bi-directional syncs, Close wins this category. If your integration center of gravity is LinkedIn, Gmail/Outlook, and lightweight no-code automation, folk is the better fit — with the caveat that deal automation requires the API.
## Choose folk CRM If... vs. Choose Close If...
Make the decision based on your **operating model**, not a feature checklist. First decide which data model you want to live with for the next three years — the migration question is secondary.
**Choose folk CRM if:**
- Your team is under 50 people and relationship context matters more than call volume
- Your sales motion starts on LinkedIn, and the folkX Chrome extension is a daily tool
- You need flexible, spreadsheet-like data modeling with group-specific custom fields
- You don't need a native dialer, SMS, or mobile app
- You want sub-$50/user/mo pricing and can live without workflow automation
- Your primary users are founders, PR professionals, recruiters, or VC partners
- You're managing investor relations, partnerships, recruiting pipelines, or other non-traditional CRM workflows where the "Lead" abstraction doesn't fit
**Choose Close if:**
- Your team makes 20+ outbound calls per day and needs a native Power Dialer (the 20-call threshold is where standalone dialer costs and context-switching overhead start exceeding Close's price premium over folk — below that volume, the dialer advantage doesn't justify the cost difference)
- You need SMS, email sequences, and call recording in one platform
- Your sales process is structured: qualify → call → demo → close
- You need strict relational data enforcement (Leads → Contacts → Opportunities) for accurate revenue forecasts
- You need a mobile app for field or remote reps
- You require SOC 2 Type 2 certification for procurement or compliance
- Your workflow demands high API rate limits (60 RPS org-wide vs. folk's 10 RPS equivalent) and deep integrations with revenue intelligence tools like Gong
## Frequently Asked Questions
### How long does a migration from folk CRM to Close typically take?
A basic contacts-and-deals migration (CSV-only, no activity history) takes 1–3 calendar days for teams under 10K records, requiring 8–20 engineering hours. A full migration including activity history and notes takes 5–10 calendar days and 25–55 engineering hours because interaction data must be extracted via folk's API and imported into Close's API record by record. The p95 for complex migrations (50K+ records, extensive custom fields, email history) is 90+ engineering hours. Working with a dedicated [migration service](https://clonepartner.com/blog/blog/the-ultimate-crm-data-migration-checklist-a-10-point-plan-for-a-zero-loss-transition/) can compress the calendar time by running extraction and import in parallel.
### Can I migrate from folk CRM to Close without losing data?
Yes, but not with a simple CSV export. folk's CSV export excludes interaction history, notes, and reminder data. To achieve zero-data-loss migration, you need the folk API (Premium plan required, $48/user/mo) to extract all objects, transform them to match Close's Lead-centric schema, and import via Close's API. Custom fields, deal stages, and contact-company associations all require explicit mapping. Email threads require special handling due to the threading model mismatch described in this guide.
### Can Close automatically import data from folk CRM?
No. Close's native CRM-to-CRM importer supports 28 platforms (including Salesforce, HubSpot, Pipedrive, Copper, and others), but folk is not on the list. You need to export from folk (CSV or API), transform the data to match Close's Lead-centric structure, and import via Close's Lead Importer (for contacts and leads) plus Close's API (for activities, notes, and tasks).
### Is folk CRM cheaper than Close?
On list price per seat, yes — folk Standard ($24/user/mo annual) is cheaper than Close Essentials ($35/user/mo annual). But folk gates deal management, sequences, and API access behind Premium ($48/user/mo), and lacks a native dialer, SMS, or mobile app. For a 10-person outbound sales team, folk Premium + Aircall dialer costs approximately $11,160–14,040/year, while Close Growth costs approximately $13,068–15,468/year (Year 2+, excluding migration). The gap narrows substantially when you add the tools folk lacks natively.
### Which CRM has better security compliance — folk or Close?
Close holds SOC 2 Type 2 certification (operational effectiveness proven over time) and explicit CCPA compliance. folk holds SOC 2 Type 1 (controls designed and in place at a point in time) and is pursuing Type 2. Both are GDPR-compliant and host data on AWS in the US. Neither offers EU data residency. For procurement teams that require SOC 2 Type 2 attestation, Close meets that bar today. folk additionally holds CASA certification from the Google App Defense Alliance.
---
**If you're migrating between these platforms** — or away from either one — and need zero data loss with preserved activity history, custom fields, and pipeline integrity, [ClonePartner](https://clonepartner.com/blog/blog/how-we-run-migrations-at-clonepartner/) has built migration scripts for both folk and Close APIs. We've completed migrations between these specific platforms and know where each platform's export gaps create risk.
> Planning a folk CRM to Close migration? Our engineers can scope it, map the data, and execute with zero downtime — typically in days, not weeks.
>
> [Talk to us](https://cal.com/clonepartner/meet?duration=30)
## Frequently asked questions
### How long does a migration from folk CRM to Close typically take?
A basic contacts-and-deals migration takes 1–3 days for teams under 10K records. A full migration including activity history and notes takes 5–10 days because interaction data must be extracted via folk's API and imported into Close's API record by record.
### Can I migrate from folk CRM to Close without losing data?
Yes, but not via CSV alone. folk's CSV export excludes interaction history and notes. You need folk's API (Premium plan required) to extract all objects, transform them to Close's Lead-centric schema, and import via Close's API.
### Can Close automatically import data from folk CRM?
No. Close's native CRM-to-CRM importer supports 28+ platforms, but folk is not on the list. You need to export from folk, transform the data to match Close's Lead-centric structure, and import via Close's Lead Importer or API.
### Is folk CRM cheaper than Close?
On per-seat price, yes — folk Standard is $24/user/mo vs Close Essentials at $35/user/mo. But folk gates deal management behind Premium ($48/user/mo) and lacks a native dialer. For outbound teams, Close's bundled calling often yields lower total cost of ownership.
### Which CRM has better security compliance — folk or Close?
Close holds SOC 2 Type 2 certification and CCPA compliance. folk holds SOC 2 Type 1 and is pursuing Type 2. Both are GDPR-compliant and host data on AWS in the US.