Migrating Custom Fields Between CRMs: Keep the Logic, Not Just the Values
Your unique sales process lives in custom fields: industry picklists, scoring formulas, and dependent cascades. A naive CSV export flattens field types, freezes formulas as static numbers, and drops the picklist rules reps rely on every day.
We migrate field types, picklist values, and dependent logic intact.
Sound Familiar?
These are the exact issues sales ops faces when CRM fields migrate as flat text:
- Industry picklists arrive as free text; reps invent spellings and reporting collapses
- Lead-scoring formulas export as static numbers that never update again
- Dependent cascades (region → country → province) flatten; invalid combinations flood the new CRM
- Sales ops spends weeks recreating field types that a CSV never carried
- Plan ceilings force a rushed export that silently drops multi-selects and formula logic
Platform field limits force rushed exits. Pipedrive Growth caps you at 100 custom fields; Salesforce Professional stops at 100 per object. Hit the ceiling and a DIY CSV cutover is the default path, which is exactly when picklist migration fails and formula fields die.
What Custom Field Migration Actually Does
Inventory → map types → rebuild logic → validate. Values alone are not enough.
Schema Audit
Every custom field typed: picklists, multi-selects, formulas, lookups, cascades
Picklist & Type Map
Source options reconciled to target fields; dead values retired before load
Logic Rebuilt
Dependent cascades and scoring formulas recreated so they keep updating
Validated Cutover
Spot-checks pass on live deals; sales keeps the process they already know
Everything You Need for a Reliable Picklist Migration
Field-Type Inventory
We catalogue every custom field by type: text, picklist, multi-select, formula, lookup, and dependent cascades, before a single record moves.
Picklist Value Mapping
Source options map 1:1, many:1, or to a legacy value. Dead values get retired; live ones land with the labels your team already trusts.
Dependent Logic Preserved
Controlling and dependent picklists rebuild as cascades in the target CRM. Region → country → province still constrains what reps can choose.
Formula Fields Rebuilt
Scoring and weighted formulas do not survive CSV. We recreate calculation properties or workflows so lead scores keep updating after cutover.
Triaged Schema, Not Blind Copy
Dormant fields (often 30–60% of a mature CRM) get retired. You migrate the process that sales still runs, not every abandoned campaign column.
Parallel Validation
Spot-check picklists, formulas, and cascades against live deals before cutover. Blank formula fields and invalid cascades get caught in test, not on day one.
Platforms We've Handled for Field Migration
From 3 Weeks of Blank Formulas to Validation-Only
How a sales ops lead moved 180 custom fields between CRMs without losing picklists, scoring, or dependent cascades.
The Naive CSV Attempt
- Sales ops exported Opportunities and Contacts as CSV after hitting Salesforce Professional's 100-field ceiling on a key object
- Industry picklist values arrived as free text; three spellings of "Financial Services" broke segment reports
- Lead Score formula landed as a frozen number; new engagement never recalculated
- Region → country → province cascade vanished; reps selected invalid combinations
- Three weeks spent recreating field types by hand before the board trusted the pipeline again
The Typed Migration
- Full schema audit: 180 fields triaged; ~40% dormant fields retired before mapping
- Picklist values pre-created in the target; multi-selects transformed, not dumped as text
- Scoring formulas rebuilt as live calculations so lead scores keep updating
- Dependent cascades recreated; invalid region combinations blocked again
- Parallel validation against open deals; cutover with sales using the same field language
Before vs After Field-Type Migration
How It Works
From field inventory to live CRM in 6 to 12 weeks for most mid-market orgs.
Audit Custom Fields
Every field type, picklist value, dependency, and formula across deals, contacts, and companies.
Map and Triage
30-minute call to decide keep, edit, or retire. Consolidate picklists and design formula equivalents.
Migrate and Rebuild Logic
Load typed fields via API where CSV fails. Rebuild dependent cascades and scoring formulas in the target.
Validate and Cut Over
Parallel-run until picklists, formulas, and cascades match. Then switch sales to the new CRM.
Frequently Asked Questions
Why do custom fields break during a CRM migration?
Naive CSV exports store values, not field types or logic. Formula fields become static snapshots. Dependent picklists lose their controlling relationships. Multi-selects often arrive as semicolon-delimited text the target cannot filter. Salesforce's Data Import Wizard explicitly ignores field dependencies, so invalid combinations import cleanly and break the process later.
What are the hard custom field limits that force migrations?
Pipedrive caps custom fields at 30 on Lite, 100 on Growth, and 300 on Premium. Salesforce Professional allows 100 custom fields per object; Enterprise allows 500; Unlimited allows 800. Zoho Standard starts at 10 fields per module and scales to 500 on Ultimate. When you hit the ceiling, a rushed plan upgrade or platform switch often dumps custom objects and formula logic unless the migration is scoped for field types.
Can formula fields and dependent picklists be migrated?
Not as-is through CSV. Formula fields export as the computed value at export time, so a lead score stops updating. Dependent picklist metadata lives outside the flat file and must be rebuilt in the target. We inventory every formula and cascade, then recreate calculation properties, workflows, or equivalent dependent fields so the business logic keeps running.
How long does a custom-field-aware CRM migration take?
Most field-heavy migrations we run take 6 to 12 weeks from audit to cutover. Accounts with under 50 live custom fields and simple picklists sit toward the shorter end. Orgs with hundreds of fields, multi-level cascades, and scoring formulas take closer to 3 to 4 months, phased so sales can work in the new system while edge cases finish.
How much does custom field migration cost?
Focused field-mapping and picklist migrations typically land between R80,000 and R200,000. Full CRM moves with custom objects, formula rebuilds, and dependent logic usually sit in the R200,000 to R1.3 million range (about $12,000 to $80,000 at R16.54 to the dollar, August 2026), matching specialised migration services for custom-field-heavy orgs. Against three weeks of sales-ops rebuild labour after a failed CSV, most clients see payback inside the first quarter.
Should we migrate every custom field we have?
No. Field triage on mature CRMs routinely marks 30–60% of custom fields for deletion: abandoned campaign columns, one-off experiments, and formulas whose inputs are already retiring. We keep the fields that encode your live process (industry picklists, scoring, dependent cascades) and leave the rest behind so the new CRM stays usable.
Stop Losing Custom Fields to Naive Exports
If your sales process lives in picklists, scoring formulas, and dependent cascades, a flat CSV migration will break it. That problem is already solved.
Tell us which CRM you are leaving, how many custom fields you run, and which formulas or cascades matter most. We will show you exactly how a typed migration would work for your business.