CRM migration
Field-level mapping, validation, and rollback between Friday CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Friday CRM
Source
Nutshell
Destination
Compatibility
6 of 8
objects map 1:1 between Friday CRM and Nutshell.
Complexity
BStandard
Timeline
1-3 weeks
Overview
Moving from Friday CRM to Nutshell is a structural migration for small teams that have outgrown a free-tier platform and need reporting, automation, and multi-user collaboration features. Friday CRM exposes a manual CSV export through Settings but does not publish API rate limits or bulk endpoints, making it a file-based migration rather than an API-based one. We audit the CSV export to confirm which objects and fields are present, map Friday CRM's nine custom field types (radio, multi-checkbox, single checkbox, dropdown, text, number, date, URL, multi-line) to Nutshell's equivalents, and resolve Company-Contact-Deal relationships before import. Pipeline stages, tags, and note timestamps migrate with ordering preserved. We do not migrate attachments (not exposed via export), integrations (OAuth tokens not exportable), or workflows (not present in Friday CRM). Nutshell's tiered pricing (Foundation at $16/user/month annual) unlocks reporting, automation, and collaboration features that Friday CRM does not offer at any tier.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Friday CRM object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Friday CRM
Company
Nutshell
Company
1:1Friday CRM Company records map directly to Nutshell Company records. Standard fields (company name, domain, address, phone) migrate 1:1. Custom fields defined on the Friday CRM Company interface (up to nine field types) require type mapping: radio selects convert to Nutshell dropdowns, multi-checkboxes may convert to multi-select or multiple boolean fields depending on destination configuration, and single checkboxes convert to Nutshell checkbox fields. We document the full field type mapping during scoping and confirm acceptable semantic conversions with the customer before migration.
Friday CRM
Contact
Nutshell
Person
1:1Friday CRM Contact records map to Nutshell Person records. Standard fields (first name, last name, email, phone, address) migrate 1:1. Friday CRM supports tagging on Contacts, which maps to Nutshell Person tags with deduplication applied during import. Custom Contact fields follow the same type-mapping rules as Company custom fields: radio selects to dropdowns, multi-checkboxes to multi-select or booleans, single checkboxes to Nutshell checkbox. The Friday CRM Company-Contact relationship is preserved by resolving the company name or domain as a lookup match in Nutshell.
Friday CRM
Deal
Nutshell
Deal
1:1Friday CRM Deals map to Nutshell Deals with pipeline stage names and ordering preserved. Deal value, expected close date, and custom fields migrate 1:1 with the same type-mapping rules applied to custom fields on Deals. Friday CRM's kanban-style pipeline stages map to Nutshell pipeline stages by display order. If Friday CRM uses stage probability values, we capture these as custom fields in Nutshell since standard Nutshell Deals do not have a probability field at the object level.
Friday CRM
Pipeline Stage
Nutshell
Pipeline Stage
lossyFriday CRM pipeline stages (the kanban columns) map to Nutshell pipeline stages by their display order and label. If Friday CRM has N stages and Nutshell has M stages, we align by name where possible and document any stage count differences for the customer to resolve before migration. Stage ordering is preserved based on the Friday CRM stage index.
Friday CRM
Custom Field
Nutshell
Custom Field
lossyFriday CRM's nine custom field types require semantic mapping to Nutshell's supported types. Radio selects map to Nutshell dropdowns. Multi-checkbox fields map to Nutshell multi-select picklists or split into separate boolean fields depending on the checkbox semantics. Single checkbox maps to Nutshell checkbox. Text, number, date, and URL field types map 1:1. We produce a custom field mapping matrix during scoping that documents each Friday CRM field name, its type in Friday CRM, its mapped type in Nutshell, and the customer sign-off on each conversion.
Friday CRM
Activity / Note
Nutshell
Note or Activity
1:1Friday CRM notes and activity history attached to Contacts and Deals migrate as Nutshell Note records linked to the parent Person or Deal. Activity timestamps are preserved in the Nutshell Note creation date. We audit the Friday CRM CSV export before migration to confirm which activity types are included; Friday CRM does not publicly document export coverage for activity logs, so we flag any missing activity types and recommend manual export of critical note history if the CSV does not capture it fully.
Friday CRM
Tag / Label
Nutshell
Tag
1:1Friday CRM tags on Contacts and Deals appear as comma-separated values in the export. We parse these tags, deduplicate them, and import them as Nutshell tags associated with the relevant Person or Deal record. Tag normalization (trimming whitespace, removing duplicates) is applied during the transform phase.
Friday CRM
Owner
Nutshell
User
1:1Friday CRM Owner references on Contacts, Companies, and Deals are resolved by matching the owner email address to an active Nutshell User. We extract all distinct owner emails from the Friday CRM export and match them against the destination Nutshell org's user list. Any Friday CRM owner without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before record import resumes.
| Friday CRM | Nutshell | Compatibility | |
|---|---|---|---|
| Company | Company1:1 | Fully supported | |
| Contact | Person1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline Stage | Pipeline Stagelossy | Fully supported | |
| Custom Field | Custom Fieldlossy | Fully supported | |
| Activity / Note | Note or Activity1:1 | Fully supported | |
| Tag / Label | Tag1:1 | Fully supported | |
| Owner | User1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Friday CRM gotchas
No mobile app means no mobile access during migration cutover
CSV export may not capture full activity history
Custom field types may require reconfiguration in destination CRM
No documented API rate limits or bulk endpoints
Integrations must be re-established manually in destination CRM
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
CSV export audit and scope confirmation
We guide the customer through generating the Friday CRM CSV export from Settings and upload the archive to our migration workspace. We audit the export to identify which objects are present (Companies, Contacts, Deals, Activities, Tags), which fields are included, and which are missing or truncated. We compare the export contents against the customer's stated record counts to confirm data completeness. Any gaps (such as missing activity history or undocumented custom fields) are flagged with recommended workarounds before mapping begins.
Custom field type mapping and customer sign-off
We extract every custom field defined on Companies, Contacts, and Deals in Friday CRM and produce a mapping matrix that pairs each Friday CRM field (with its type: radio, multi-checkbox, single checkbox, dropdown, text, number, date, URL, multi-line) to its Nutshell equivalent. Radio selects map to dropdowns, multi-checkboxes to multi-select or boolean fields, single checkboxes to Nutshell checkboxes. We walk the customer through the matrix, confirm which semantic conversions are acceptable, and capture any fields that require post-migration manual entry because no type-equivalent exists in Nutshell.
Schema pre-creation in Nutshell
Before importing any records, we pre-create the destination schema in Nutshell. This includes custom fields (with correct types per the signed mapping matrix), pipeline stages (aligned by name and order to Friday CRM's kanban columns), and any required tags. Nutshell's import interface is used to validate that the destination fields are correctly configured and that the custom field types accept the incoming data format. Schema issues discovered at this stage are corrected before any record data is loaded.
Owner reconciliation and User provisioning
We extract every distinct Friday CRM Owner email address from the export and match against the destination Nutshell org's user list. Any Friday CRM owner without a matching Nutshell User goes to a reconciliation queue. The customer's admin provisions any missing Nutshell Users before record import resumes. Owner resolution must be complete before importing Deals because Nutshell Deals require an assigned User as the owner.
Record import in dependency order
We run the import in record-dependency order: Companies first (no dependencies), then Persons (with company lookup resolved where applicable), then Deals (with person and company lookups and owner User resolved). Tags and notes import as final phases, linked to the parent Person or Deal records. Each phase emits a row-count reconciliation report showing records attempted, records succeeded, and records rejected. Rejections are investigated and corrected before the next phase begins.
Cutover, validation, and integration rebuild handoff
We freeze Friday CRM writes during cutover, run a final delta migration of any records modified since the initial export, then enable Nutshell as the system of record. We deliver a written integration rebuild checklist covering Gmail, G Suite, Mailchimp, and RingCentral reconfiguration steps so the customer's admin can restore integrations independently. We support a five-business-day post-cutover window where we resolve any reconciliation issues. We do not rebuild automations or workflows because Friday CRM does not offer these features; any automation the customer builds in Nutshell is outside migration scope.
Platform deep dives
Friday CRM
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Friday CRM and Nutshell.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Friday CRM: Not publicly documented.
Data volume sensitivity
Friday CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Friday CRM to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Friday CRM to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Friday CRM
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.