Migrate your folk data
Lightweight CRM built around Groups and Contacts for relationship-driven sales teams. No permanent free tier, but one of the fastest onboarding curves in the CRM category.
In its favor
Why people choose folk
The signal that keeps folk on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Minimal setup friction — contacts import in two steps via CSV and the interface behaves like a clean workspace rather than a rigid sales system, which appeals to teams switching from spreadsheets or Notion.
LinkedIn-first workflow with a one-click contact save from LinkedIn profiles — users praise the depth of the LinkedIn integration compared to HubSpot's lighter social connection.
Credit-based AI with a single, workspace-wide pool for Magic Fields and enrichment is simpler to reason about than seat-level credit splits found in Attio.
Per-group custom fields let non-technical users build group-specific taxonomies (e.g., separate field sets for Leads vs. Clients) without touching a schema editor.
Teams of 20–50 migrating from Notion, ActiveCampaign, or Brevo cite the pipeline view and email tracking as the features that finally justify a CRM over a spreadsheet.
Internal automation between contact and company fields requires manual field mapping — contacts and companies do not auto-link in folk, causing data duplication for teams with strong account-based motions.
Reporting is limited compared to Pipedrive or HubSpot — deal dashboards and pipeline analytics shipped recently but still lag behind pipeline-first CRMs on forecasting and cohort analysis.
Workspace-wide AI credit limits mean one heavy automator can exhaust Magic Field credits for the entire team, causing unexpected feature lockouts mid-month.
No public bulk API documented for programmatic export — teams with thousands of records rely on multi-step CSV extraction, which breaks for attachments and relationship graphs.
Some users report bugs with document attachments and slower performance when contacts exceed 5,000 records in a single group.
Reasons to switch
Why people leave folk
The recurring reasons buyers give for replacing folk. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where folk fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
folk pricing overview
Folk uses per-seat pricing with an annual discount of roughly 20%. No permanent free tier exists — only a 14-day trial without a credit card. AI features (Magic Fields and enrichment) are credit-pooled at the workspace level, not per-seat, which means costs scale with the team but the AI pool does not grow proportionally with headcount.
Standard
Tier 1 of 3
$20–$30/user/month (billed annually $24–$25)
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on folk's schedule — see our quote-based pricing →
What gets migrated
folk object support
Object-by-object support for folk migrations. Per-pair details surface during scoping.
Contacts
Fully supportedContacts are the primary record in folk, with a person/company subtype. We map the subtype field and all standard properties (name, email, phone, social handles) directly. Custom fields per contact are preserved via per-group field mapping.
Groups
Fully supportedGroups are folk's organizational container concept — analogous to Lists or Segments in other CRMs. We map each Group and preserve group membership for every contact during migration.
Custom Fields
Mapping requiredCustom fields in folk are defined per-group, not globally. We enumerate all group-specific field schemas during discovery and build a field map before importing, since the schema varies between source groups.
Notes
Fully supportedNotes are attached to contacts and contain plain text plus timestamps and author attribution. We migrate notes as linked child records of the contact.
Reminders
Mapping requiredReminders carry a due date, assignee, and text. We migrate reminder text and due date; assignee mapping requires resolving user identity between source and destination systems.
Tags
Fully supportedContacts can be tagged freely in folk. We migrate the full tag set per contact as a string array, and map to the destination system's tag or label model.
Pipeline Views
Mapping requiredPipeline views in folk are per-group. We map pipeline stages to the destination CRM's pipeline structure and flag any custom stage logic that needs manual recreation.
Email Campaigns
Not in this platformEmail campaign history — sent emails, open/click events — is not exported via CSV or a public bulk API. We migrate the contact list for the campaign but not campaign performance data.
Attachments
Mapping requiredAttachments linked to contacts can be exported as URLs or files via CSV. We attempt to download and re-upload where the destination supports it; file size limits vary by plan.
Activities
Mapping requiredActivity history (emails sent, meetings logged) is partially captured in folk's timeline. We extract what is present in the CSV export and map it to the destination's activity object, noting gaps.
Companies
Fully supportedCompanies are a contact subtype in folk. We treat them as separate records with a linked-person parent where applicable, and migrate all company properties and custom fields.
AI Magic Fields
Not in this platformMagic Fields are AI-generated field values computed at query time, not stored as data. They do not exist as migratable records — they are derived from source data and the AI model, so we do not attempt to migrate them.
Enrichment Credits
Not in this platformEnrichment data is external and live-fetched by folk's AI. The enriched values are not persistently stored in a way that is accessible for export, so we do not migrate them.
| Object | Support | Notes |
|---|---|---|
| Contacts | Fully supported | Contacts are the primary record in folk, with a person/company subtype. We map the subtype field and all standard properties (name, email, phone, social handles) directly. Custom fields per contact are preserved via per-group field mapping. |
| Groups | Fully supported | Groups are folk's organizational container concept — analogous to Lists or Segments in other CRMs. We map each Group and preserve group membership for every contact during migration. |
| Custom Fields | Mapping required | Custom fields in folk are defined per-group, not globally. We enumerate all group-specific field schemas during discovery and build a field map before importing, since the schema varies between source groups. |
| Notes | Fully supported | Notes are attached to contacts and contain plain text plus timestamps and author attribution. We migrate notes as linked child records of the contact. |
| Reminders | Mapping required | Reminders carry a due date, assignee, and text. We migrate reminder text and due date; assignee mapping requires resolving user identity between source and destination systems. |
| Tags | Fully supported | Contacts can be tagged freely in folk. We migrate the full tag set per contact as a string array, and map to the destination system's tag or label model. |
| Pipeline Views | Mapping required | Pipeline views in folk are per-group. We map pipeline stages to the destination CRM's pipeline structure and flag any custom stage logic that needs manual recreation. |
| Email Campaigns | Not in this platform | Email campaign history — sent emails, open/click events — is not exported via CSV or a public bulk API. We migrate the contact list for the campaign but not campaign performance data. |
| Attachments | Mapping required | Attachments linked to contacts can be exported as URLs or files via CSV. We attempt to download and re-upload where the destination supports it; file size limits vary by plan. |
| Activities | Mapping required | Activity history (emails sent, meetings logged) is partially captured in folk's timeline. We extract what is present in the CSV export and map it to the destination's activity object, noting gaps. |
| Companies | Fully supported | Companies are a contact subtype in folk. We treat them as separate records with a linked-person parent where applicable, and migrate all company properties and custom fields. |
| AI Magic Fields | Not in this platform | Magic Fields are AI-generated field values computed at query time, not stored as data. They do not exist as migratable records — they are derived from source data and the AI model, so we do not attempt to migrate them. |
| Enrichment Credits | Not in this platform | Enrichment data is external and live-fetched by folk's AI. The enriched values are not persistently stored in a way that is accessible for export, so we do not migrate them. |
Gotchas
What to watch for in folk migrations
Issues we've hit on past folk migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No public bulk API for automated migration
Per-group custom fields create schema fragmentation
Workspace-wide AI credit limits affect all seats
Contact–company linking is not automatic
Email campaign history not exported
| Severity | Issue |
|---|---|
| High | No public bulk API for automated migration |
| Medium | Per-group custom fields create schema fragmentation |
| Medium | Workspace-wide AI credit limits affect all seats |
| Low | Contact–company linking is not automatic |
| Low | Email campaign history not exported |
Leaving folk?
Where folk customers move next
12 destinations folk can migrate to.
How a folk migration works
Four steps, folk-specific
Connect
Not publicly documented into folk. Scopes limited to read-only on the data we move.
Map
We translate folk-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate folk quirks before production.
Migrate
Full migration with folk rate-limit handling. Rollback available throughout.
FAQ
folk migration FAQ
Answers to the questions buyers ask most during folk migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your folk migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate folk.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your folk setup and destination — written quote back within a business day.