CRM migration
Field-level mapping, validation, and rollback between YetiForce CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
YetiForce CRM
Source
Nutshell
Destination
Compatibility
8 of 10
objects map 1:1 between YetiForce CRM and Nutshell.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Moving from YetiForce CRM to Nutshell is a transition from a self-hosted open-source ERP-CRM hybrid to a managed SaaS CRM with built-in sales and marketing automation. YetiForce's Organizations map directly to Nutshell Companies, Contacts map 1:1, and Potentials map to Nutshell's Opportunities with stage names transformed via a configuration table. The key technical difference is that YetiForce's free Webservice Standard API exposes only record-level CRUD with no bulk endpoints, so we extract via CSV export and supplement with API-based validation passes. We do not migrate YetiForce workflows, the removed Reports module, or any custom PHP modifications; we deliver a written inventory of these for the customer's admin to rebuild in Nutshell's automation tools. Nutshell's native import tool does not support YetiForce directly, which is why a scripted migration through FlitStack AI is the practical path for teams with thousands of records.
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 YetiForce 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.
YetiForce CRM
Organizations
Nutshell
Company
1:1YetiForce Organization records map directly to Nutshell Company records. Organization fields (company name, industry, website, address, phone, type) map to Nutshell Company fields by field name matching after a dynamic schema map is built during the audit phase. Organizations are migrated first because Contacts and Potentials reference them via foreign key. The Nutshell API requires Company creation before Contact creation if the Contact has an associated Company.
YetiForce CRM
Contacts
Nutshell
Person
1:1YetiForce Contact records map to Nutshell Person records. Name, email, phone, job title, address, and assigned owner fields migrate 1:1. The Contact's Organization reference resolves to a Nutshell Company via the Organizations mapping performed in the previous phase. We flag any Contact without an email address for the customer's review before import because Nutshell requires an email for Person record creation at most plan tiers.
YetiForce CRM
Leads
Nutshell
Lead
1:1YetiForce Lead records (pre-conversion prospect data including source, status, and company name) map to Nutshell Lead records. Lead_Source and Lead_Status from YetiForce migrate to Nutshell Lead source and status picklist values. We apply a transformation table to map YetiForce status values to Nutshell's native Lead status options (New, Working, Nurture, Unqualified, Converted). Any custom status values that do not match Nutshell options default to the nearest native value and are flagged for the admin to review post-migration.
YetiForce CRM
Potentials
Nutshell
Opportunity
1:1YetiForce Potentials (the deal pipeline object tied to an Organization and an assigned user) map to Nutshell Opportunities. The Potential stage name maps to Nutshell pipeline stage values via a customer-supplied configuration table during scoping. We flag the possibility that YetiForce stage names (often customized per-instance) do not map directly to Nutshell's default stage set and require explicit mapping. The related Organization reference resolves to the Nutshell Company lookup at migration time.
YetiForce CRM
Projects
Nutshell
Account + Custom Fields
lossyYetiForce Projects (name, status, start/end dates, assigned owner) have no direct Nutshell equivalent because Nutshell is CRM-focused without native project management. We migrate Projects as Nutshell Companies with a custom Project__c boolean flag and custom date fields for start and end dates. The customer must decide whether Project status picklist values map to Nutshell Industry or a custom picklist. Project Tasks link to the parent Project and are mapped separately as Nutshell Tasks with a custom project_reference__c field linking back to the parent Company record.
YetiForce CRM
Project Tasks
Nutshell
Task
1:1YetiForce Project Tasks link to a parent Project (resolved to the Company-as-Project record via the Organization mapping). We map task subject, status, priority, and assigned user to Nutshell Task fields. YetiForce status and priority picklist values transform to Nutshell Task status and priority via a configuration table. The parent record reference resolves via the project_reference__c custom field on the Task. Large Project Tasks volumes may require CSV export path rather than API due to Nutshell API rate limits.
YetiForce CRM
Tickets
Nutshell
Lead or Task
lossyYetiForce Tickets (title, status, priority, category, related Contact and Organization) have no direct Nutshell equivalent. We scope the customer's use of Tickets during discovery: if Tickets are used for pre-sale prospect issues, they map to Nutshell Lead with a custom ticket_status__c field. If used for customer support, they map to Nutshell Task records with a custom ticket_id__c field and a dedicated view for the support team. The customer chooses the strategy during scoping because Nutshell's native support object (Cases) requires the Service Cloud add-on.
YetiForce CRM
Products
Nutshell
Product
1:1YetiForce Products (name, unit price, vendor link, description, stock levels) map to Nutshell Product records. Product name, price, and description migrate 1:1. The vendor reference resolves to the Nutshell Vendor record (created in the Vendors phase). Stock levels are informational in Nutshell unless the customer has a separate inventory system; we migrate the value but flag it as read-only in Nutshell's product management UI.
YetiForce CRM
Services
Nutshell
Product
1:1YetiForce Services (recurring offerings with price per unit and description) share the same data shape as Products in YetiForce. We migrate Services to Nutshell Product records using the same mapping logic as Products, flagging them with a custom product_type__c field set to 'Service' so the customer's team can filter by type in Nutshell's product list view.
YetiForce CRM
Vendors
Nutshell
Company
1:1YetiForce Vendor records (company name, website, address, assigned owner) map to Nutshell Company records with a custom vendor__c boolean flag. This differentiates Vendors from customer Organizations in Nutshell's Company list. Vendor name becomes the Company name, and vendor website migrates to the Company website field.
| YetiForce CRM | Nutshell | Compatibility | |
|---|---|---|---|
| Organizations | Company1:1 | Fully supported | |
| Contacts | Person1:1 | Fully supported | |
| Leads | Lead1:1 | Fully supported | |
| Potentials | Opportunity1:1 | Mapping required | |
| Projects | Account + Custom Fieldslossy | Mapping required | |
| Project Tasks | Task1:1 | Mapping required | |
| Tickets | Lead or Tasklossy | Mapping required | |
| Products | Product1:1 | Fully supported | |
| Services | Product1:1 | Fully supported | |
| Vendors | Company1: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.
YetiForce CRM gotchas
YetiForce GitHub archived as read-only since August 2025
Reports module removed in version 4.4 and never restored
Webservice Standard API lacks bulk endpoints
Webservice Premium required for portal and OpenAPI access
Heavy per-instance customization complicates field mapping
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
Discovery and export path determination
We audit the source YetiForce instance for record counts per module (Organizations, Contacts, Leads, Potentials, Projects, Project Tasks, Products, Services, Vendors), custom field definitions, and active integrations. We determine whether the customer has Webservice Premium (REST API access) or must use CSV Export for extraction. We identify any PHP version constraints on the source server and confirm whether the YetiForce instance is on a supported version. The discovery output is a written scope, a data quality report identifying duplicates and incomplete records, and a recommendation on whether to clean data before migration.
Schema mapping and custom field reconciliation
We build a dynamic field schema map by querying YetiForce's field metadata endpoint (if Webservice Premium is available) or by analyzing the CSV export headers. This map resolves YetiForce's instance-specific custom field IDs (cf_123) to their human-readable names. We then map each YetiForce field to a typed Nutshell field (text, number, date, picklist, boolean). Any YetiForce fields without a Nutshell equivalent are flagged as candidate custom fields, and we confirm with the customer which ones fit within their Nutshell plan's custom field limit.
Data extraction via CSV export or API
We extract data from YetiForce using the path determined in discovery: CSV Export for each module (Organizations, Contacts, Leads, Potentials, Products, Services, Vendors) if Webservice Premium is unavailable, or REST API record-level extraction if it is. For Projects and Project Tasks, we use a separate export pass because of the parent-child relationship. We validate record counts against the discovery data quality report and flag any modules where the extracted count diverges significantly from the expected count.
Transformation, deduplication, and parent resolution
We transform extracted records to match Nutshell's import schema. This includes applying the stage-name configuration table for Potentials-to-Opportunities mapping, resolving Organization references to Nutshell Company lookups, applying the Lead status transformation table, and flagging any records with missing required fields (email for Persons, company name for Companies). We run a deduplication pass on email addresses for Contacts and Person records to prevent duplicate Nutshell entries. Organizations are loaded first, then Contacts, then Leads, then Potentials, then Products and Services.
Sandbox import and reconciliation
We run a full import into Nutshell using a test workspace or a sandbox-like data load to validate mapping accuracy. The customer's admin reviews 25-50 randomly sampled records against the YetiForce source data, confirms that custom fields landed in the correct Nutshell fields, and verifies that Opportunity stage values are readable in the Nutshell pipeline view. Any mapping corrections are applied to the transformation logic before the production import begins.
Production import, cutover, and handoff
We run the production import in dependency order (Companies, Persons, Leads, Opportunities, Products, Services, Tasks). Each phase emits a row-count reconciliation report. We freeze writes to the YetiForce instance during cutover, run a final delta migration for records modified during the migration window, then mark Nutshell as the system of record. We deliver a written inventory of any YetiForce workflows, custom PHP modifications, and the removed Reports module definitions for the customer's admin to rebuild in Nutshell. We do not rebuild automations as part of the standard migration scope.
Platform deep dives
YetiForce CRM
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 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 YetiForce CRM and Nutshell.
Object compatibility
1 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
YetiForce CRM: Not publicly documented by YetiForce; rate limits may be enforced per-IP or per-session on self-hosted instances.
Data volume sensitivity
YetiForce 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 YetiForce CRM to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your YetiForce 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 YetiForce 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.
