CRM

CRM

Click to read the full definition in our AI & Automation Glossary.

Field Mapping Worksheet

Your CRM

holds every client interaction, every opportunity, every billable relationship. But if your fields don't map cleanly to your workflows, you're building on quicksand.

This worksheet eliminates the guesswork. It's a structured spreadsheet that documents exactly what each CRM

field does, where its data comes from, and which downstream processes depend on it. Pre-filled for HubSpot, Salesforce, and Clio with the 40+ fields that matter most in professional services.

Use this when you're onboarding a new associate who needs to understand your data model in 20 minutes instead of 20 days. Use it when you're migrating CRMs

and can't afford to lose pipeline visibility for three weeks. Use it when your intake coordinator keeps putting company names in the "Last Name" field because nobody documented the correct protocol.

The template includes seven columns for every field in your CRM

:

Field Name: The exact label as it appears in your system (case-sensitive for API

integrations).

Object Type: Contact, Company, Deal/Matter, Activity, or Custom. This determines which reports can access the field.

Purpose: One-sentence explanation. "Tracks referral source for attribution reporting" beats "Stores referral information."

Workflow Dependencies: Every automation, document template, or integration that pulls from this field. If you change "Practice Area" from a dropdown to free text, you need to know which 12 automations will break.

Data Source: Manual entry, web form, Zapier sync from your practice management system, API pull from your accounting platform. Knowing the source tells you where to fix data quality issues.

Validation Rules: Required field? Dropdown with specific options? Must match email format? Character limits? Document it here so your team enters clean data the first time.

Owner: The specific person (not "the team") who audits this field monthly and fixes bad data. First name, last name, email address.

Step 1: Export your current field list (15 minutes)

In HubSpot: Settings > Properties > Export all properties to CSV. Filter to only Contact, Company, and Deal properties.

In Salesforce: Setup > Object Manager > Select object > Fields & Relationships > Export field definitions.

In Clio: Settings > Custom Fields > Screenshot each section (Clio doesn't offer bulk export, unfortunately).

Copy your field names into Column A of the worksheet. Delete the pre-filled examples that don't match your system.

Step 2: Categorize by object type (10 minutes)

Mark each field as Contact, Company, Deal, Activity, or Custom in Column B. This takes 30 seconds per field if you know your data model. If you don't, open your CRM

in a second window and check where each field lives.

Step 3: Document purpose and dependencies (45 minutes)

This is where most firms rush and regret it later. For each field, answer:

• What business question does this field answer?
• Which reports or dashboards display this field?
• Which email templates or document generators pull from this field?
• Which Zapier workflows or API

  API

  Click to read the full definition in our AI & Automation Glossary.

  integrations read or write to this field?

Example for "Practice Area" field:

Purpose: Categorizes matters by legal specialty for capacity planning and conflict checks.

Workflow Dependencies:

• Triggers assignment to practice group leader in Clio
• Populates engagement letter template in PandaDoc
• Feeds "Revenue by Practice Area" dashboard in Tableau
• Routes intake form submissions via Zapier based on selected practice area

If you discover a field with zero dependencies, flag it for deletion. Dead fields slow down your system and confuse your team.

Step 4: Identify data sources (10 minutes)

For each field, note whether data comes from:

• Manual entry by specific role (intake coordinator, partner, associate)
• Web form submission (contact form, consultation request, newsletter signup)
• Integration sync (practice management system, accounting software, marketing automation)
• API

  API

  Click to read the full definition in our AI & Automation Glossary.

  import (one-time migration, nightly batch job)

This tells you where to implement data quality controls. Manual entry needs validation rules. Web forms need field mapping checks. Integrations need error monitoring.

Step 5: Define validation rules (10 minutes)

For each field, specify:

• Required or optional?
• Free text, dropdown, checkbox, date picker, number?
• If dropdown: list all valid options
• If text: character limit and format requirements
• If number: min/max values and decimal places

Example: "Client Industry" field should be dropdown with options: Legal, Accounting, Consulting, Financial Services, Healthcare, Technology, Other. Required for all Company records. No free text allowed.

Without documented validation rules, you'll have "Accounting," "accounting," "Acctg," and "CPA Firm" all meaning the same thing, making your reports useless.

The worksheet includes starter field sets for three platforms. Customize these to match your actual configuration.

HubSpot (38 fields):

• Contact: First Name, Last Name, Email, Phone, Mobile, Job Title, LinkedIn URL, Lead Source, Lead Status, Lifecycle Stage
• Company: Company Name, Domain, Industry, Annual Revenue, Number of Employees, Company Owner, Type (Client/Prospect/Referral Partner)
• Deal: Deal Name, Amount, Close Date, Deal Stage, Practice Area, Originating Partner, Responsible Attorney, Estimated Hours, Matter Type

Salesforce (42 fields):

• Lead: First Name, Last Name, Email, Phone, Company, Title, Lead Source, Lead Status, Rating, Industry
• Account: Account Name, Type, Industry, Annual Revenue, Number of Employees, Account Owner, Parent Account
• Opportunity: Opportunity Name, Amount, Close Date, Stage, Probability, Practice Area, Lead Source, Next Step

Clio (35 fields):

• Contact: First Name, Last Name, Email, Phone, Mobile, Company, Type (Client/Lead/Referral Source), Source
• Matter: Matter Number, Description, Practice Area, Responsible Attorney, Originating Attorney, Open Date, Close Date, Status, Billing Method, Matter Type

Each platform section includes the most commonly used fields in professional services firms. Add your custom fields in the blank rows below each section.

Mistake 1: Using free text for categorical data

Wrong: "Practice Area" as a text field where people type "Corporate," "corporate," "Corp," "Business Law," "M&A."

Right: Dropdown with exactly seven options that match your firm's practice group structure.

Mistake 2: Storing the same data in multiple places

If "Client Industry" exists on both Contact and Company objects, which one is the source of truth? Pick one. Map the other to sync from it automatically.

Mistake 3: Creating fields without owners

Every field needs a named human who checks data quality monthly. "The admin team" is not an owner. "Sarah Chen, Operations Manager, sarah.chen@firm.com" is an owner.

Mistake 4: No documentation of downstream dependencies

You change a field name or delete a field, and three automations break silently. You don't notice until a client complains they didn't receive their engagement letter. Document every dependency before you change anything.

Mistake 5: Validation rules that don't match reality

Requiring "Annual Revenue" for all Company records sounds good until your intake team can't create records for individual clients who don't have companies. Make fields required only when you genuinely can't proceed without the data.

Assign one person to review this worksheet quarterly. Set a recurring calendar event. During each review:

1. Add any new fields created in the last 90 days
2. Update workflow dependencies for fields that now feed new reports or automations
3. Remove fields that were deprecated or deleted
4. Check that validation rules still match current business processes
5. Verify that field owners are still in their roles (update if someone left the firm)

When you migrate to a new CRM

or add a major integration, review the entire worksheet. Map old field names to new field names. Update all workflow dependencies. Test every integration before going live.

This worksheet is not a one-time documentation exercise. It's your CRM

's operating manual. Keep it current, reference it during onboarding, and consult it before making any structural changes to your system.

Firms that maintain accurate field mapping have 60% fewer data quality issues and onboard new team members 40% faster. Firms that skip this step spend hours every month troubleshooting broken automations and cleaning duplicate data.

Download the template, block 90 minutes on your calendar this week, and build your field map. Your future self will thank you when you're not frantically trying to remember which fields your engagement letter template depends on at 4:45 PM on a Friday.