Standardize Field Names Across Pipedrive/HubSpot/Salesforce

You are a CRM migration consultant who's moved 50+ agencies between Pipedrive, HubSpot, and Salesforce and has seen every naming convention disaster.
Agency: [AGENCY_NAME] | Source CRM: [SOURCE_CRM] | Target CRM (or 2nd CRM): [TARGET_CRM] | Migration or sync scenario: [SCENARIO] | Critical fields: [CRITICAL_FIELDS] | Existing field names (mess): [EXISTING_NAMES]
Create a canonical field naming convention with cross-CRM mapping. For each canonical field, give the recommended label, API name, data type, and what it maps to in Pipedrive, HubSpot, and Salesforce — including platform-specific gotchas.

- Canonical API name in snake_case, no platform-specific prefixes
- Mapping table must call out platform-specific differences (data type mismatches, picklist vs free text, etc.)
- For each field, flag whether sync is bidirectional safe, source-of-truth only, or risky
- Include a glossary for ambiguous terms (e.g., "Deal Amount" vs "MRR" vs "TCV")
- Recommend the canonical source-of-truth system for each field group

Section 1: naming convention rules. Section 2: canonical field dictionary (Canonical Label | API Name | Type | Pipedrive | HubSpot | Salesforce | Sync Safety | Source of Truth). Section 3: glossary of ambiguous terms. Section 4: top 5 migration gotchas.

• [AGENCY_NAME] — Your agency's name
• [SOURCE_CRM] — Where data lives today
• [TARGET_CRM] — Where it's going (or other side of sync)
• [SCENARIO] — Migration, dual-sync, multi-brand setup
• [CRITICAL_FIELDS] — Fields that must survive perfectly
• [EXISTING_NAMES] — Examples of current naming mess (e.g., 'mrr_amt', 'Monthly Rev', 'mrr')

Agency: Tradewind Marketing | Source: Pipedrive | Target: HubSpot Pro | Scenario: full migration in Q3 | Critical: MRR, contract length, source, AM, service line | Existing names: 'mrr_amt' (Pipedrive custom), 'Monthly Rev', 'rev_mo' — all referring to the same thing

**Naming rules**
- snake_case canonical API names, no CRM-specific prefixes
- Currency fields suffixed `_amount` or `_mrr`
- Date fields suffixed `_date`
- Boolean fields prefixed `is_`
- Picklist fields use singular noun

**Canonical Dictionary** (abridged)
| Canonical | API | Type | Pipedrive | HubSpot | Salesforce | Sync | SoT |
|---|---|---|---|---|---|---|---|
| Monthly Recurring Revenue | mrr_amount | Currency | Custom field 'mrr_amt' | Custom 'mrr_amount' | hs_mrr__c | Bidirectional safe | New CRM |
| Contract Months | contract_months | Number | 'contract_len' | 'contract_months' | 'Contract_Months__c' | Bidirectional safe | New CRM |
| Service Line | service_line | Multi-select | Multi-options | Multi-checkbox property | Multi-select picklist | Risky — Pipedrive multi-options ≠ HubSpot multi-checkbox 1:1 | Pick one |
| AM Owner | am_owner | User | Custom user field | HubSpot Owner property | Custom Lookup | Bidirectional safe if user IDs map | New CRM |
| Deal Source | deal_source | Picklist | Custom picklist | 'hs_analytics_source' or custom | LeadSource | Risky — HubSpot has built-in source that fights custom | Use custom in both |

**Glossary**
- Deal Amount = TCV (total contract value) in HubSpot default; force MRR in custom field
- 'Amount' in Salesforce = one-time; create MRR custom

**Top gotchas:** (1) HubSpot deal amount auto-calcs from line items — disable if migrating raw amounts. (2) Pipedrive multi-options export as comma-strings; HubSpot needs semicolons. (3) Salesforce LeadSource is hardcoded on Lead/Opportunity — your custom source must live elsewhere. (4) User IDs don't transfer — map manually. (5) Date formats: Pipedrive ISO, Salesforce often MDY in exports.

• Pick one source of truth per field before you migrate. Bidirectional sync without a SoT is how data gets mangled.
• Test your mapping on 50 records first. If anything looks weird at 50, it'll be a catastrophe at 5,000.
• Keep the canonical dictionary in a shared doc forever — it becomes onboarding gold when you hire your next ops person.