Salesforce + Jobber Integration Guide

This guide walks you through setting up a complete integration between Salesforce and Jobber. By the end, your Salesforce contacts and Jobber clients will stay in sync for coordinated sales and field service operations.

Overview

Goal: Keep Salesforce Contacts and Jobber Clients in sync, so your sales team and field service crew work from the same customer data.

What You'll Set Up:

• Salesforce Contacts synced with Jobber Clients
• Salesforce Accounts mapped to Jobber Properties (service locations)
• PascalCase ↔ snake_case field name handling
• Bidirectional updates with conflict resolution

Time Required: 20–25 minutes

Prerequisites

Before starting, ensure you have:

• [ ] A FluxCascade account (sign up free)
• [ ] System Administrator access to your Salesforce org
• [ ] Admin access to your Jobber account
• [ ] Both platforms connected to FluxCascade

If you haven't connected your platforms yet, see the Salesforce integration docs and Jobber integration docs first.

Step 1: Connect Salesforce (Sandbox vs. Production)

When connecting Salesforce, you'll choose between:

Production: Your live Salesforce org. Use this for real data sync.

Sandbox: A copy of your production org for testing. Recommended for initial setup. When you're satisfied with the mapping, disconnect the sandbox and connect production.

To connect:

1. Go to Connections → Add Connection → Salesforce
2. Select Production or Sandbox
3. Authorize FluxCascade in the Salesforce login screen
4. Verify the connection shows a green status

Step 2: Plan Your Field Mapping

Contact → Client Field Pairs

Salesforce uses PascalCase field names (FirstName, MailingCity) while Jobber uses snake_case (first_name, billing_address.city). FluxCascade handles the mapping — you just select the fields.

Step 3: Create the Contact → Client Mapping

1. Go to Mappings in FluxCascade
2. Click New Mapping
3. Configure the basics:

Source:

• Connection: Your Salesforce connection
• Object: Contacts

Target:

• Connection: Your Jobber connection
• Object: Clients

Direction: Bidirectional (recommended)

4. Click Continue

Step 4: Configure Field Pairs

Add these field pairs:

1. First Name

   • Source: FirstName
   • Target: first_name
   • Transform: None

2. Last Name

   • Source: LastName
   • Target: last_name
   • Transform: None

3. Email (Matching Field)

   • Source: Email
   • Target: email
   • Transform: lowercase
   • Mark as Matching Field

4. Phone

   • Source: Phone
   • Target: phone
   • Transform: phone_e164
   • Default country: US (or your country)

5. Company Name

   • Source: Account.Name
   • Target: company_name
   • Transform: None

Address Fields

6. Street

   • Source: MailingStreet
   • Target: billing_address.street1

7. City

   • Source: MailingCity
   • Target: billing_address.city

8. State/Province

   • Source: MailingState
   • Target: billing_address.province

9. Postal Code

   • Source: MailingPostalCode
   • Target: billing_address.postal_code

Step 5: Account → Property Mapping (Optional)

Salesforce Accounts can map to Jobber Properties (service locations). This is useful when a single company has multiple job sites.

1. Create a second mapping: Salesforce Accounts → Jobber Properties
2. Map the following:

• BillingStreet → street
• BillingCity → city
• BillingState → province
• BillingPostalCode → postal_code
• Name → (use as label/reference)

This mapping is typically one-way (Salesforce → Jobber), since field service teams add properties directly in Jobber for new job sites.

Step 6: Configure Conflict Resolution

For bidirectional sync, set rules for conflicting updates:

Recommended Settings:

• Overall Strategy: Last Write Wins
• Email field: Salesforce wins – CRM is the record owner for email
• Phone field: Jobber wins – field service teams often get updated numbers on-site
• Address fields: Jobber wins – field crews confirm physical addresses

Step 7: Set Matching Strategy

1. In mapping settings, find Matching Strategy
2. Select Email as the primary matching field
3. Enable Case Insensitive Matching

Step 8: Test the Mapping

Before going live:

1. Click Test Sync

2. Review the preview showing what would sync

3. Check for:

   • Correct field mapping across naming conventions
   • Phone numbers formatted correctly
   • Address components in the right Jobber fields
   • Expected record counts

4. Adjust configuration and test again if needed

Step 9: Run Initial Sync

Once testing looks good:

1. Click Sync Now
2. Choose Full Sync for initial population
3. Monitor progress in real-time
4. Review completion statistics

Expected Results:

• Salesforce Contacts created as Jobber Clients
• Jobber Clients created as Salesforce Contacts (bidirectional)
• Address data split into correct Jobber billing address fields

Step 10: Enable Scheduled Sync

Set up automatic syncing:

1. Go to mapping Settings
2. Enable Scheduled Sync
3. Choose frequency: Every 15 minutes (recommended)
4. Save

Verification

Check Salesforce

1. Open a Contact that should have synced
2. Verify Jobber-created contacts appear
3. Check field values match

Check Jobber

1. Open a Client that should have synced
2. Verify Salesforce-created clients appear
3. Check billing address is populated correctly

Review Sync Logs

1. Go to Syncs
2. Click on recent sync jobs
3. Verify success rates and any errors

Common Issues & Solutions

PascalCase Fields Not Mapping

Cause: Confusion between Salesforce field API names and display labels.

Solution: Always use Salesforce API names in the field selector (e.g., FirstName, not "First Name"). FluxCascade's field picker shows API names and labels side by side.

Address Not Populating in Jobber

Cause: Salesforce MailingStreet mapped to billing_address instead of billing_address.street1.

Solution: Map each address component individually:

• MailingStreet → billing_address.street1
• MailingCity → billing_address.city
• MailingState → billing_address.province
• MailingPostalCode → billing_address.postal_code

Salesforce Sandbox Data Not Syncing

Cause: Connected to production but testing with sandbox data, or vice versa.

Solution: Verify which Salesforce environment you connected. Check the connection details page — it shows the instance URL (login.salesforce.com for production, test.salesforce.com for sandbox).

Duplicate Clients Created

Cause: Matching field not finding existing records.

Solution:

1. Ensure email is the matching field
2. Enable case-insensitive matching
3. Verify emails are populated in source records
4. Run a dedup in Jobber if duplicates were created during initial sync

Phone Numbers Not Syncing

Cause: Salesforce stores phone numbers with formatting (e.g., (415) 555-0100), Jobber expects clean numbers.

Solution: Add the phone_e164 transform. Set the default country to your region.

Best Practices

1. Test in a Salesforce Sandbox first – Validate your mapping before touching production data

2. Map address components individually – Don't concatenate into a single field; Jobber needs structured addresses

3. Let Jobber own address data – Field crews verify addresses on-site; set Jobber as the conflict winner for address fields

4. Use email for matching – Most reliable identifier shared between Salesforce and Jobber

5. Start with Contacts, add Accounts later – Get person-level sync working before adding the Account → Property mapping

6. Monitor the first week – Check sync logs daily to catch issues early

Next Steps

• HubSpot + Jobber guide – Compare with the HubSpot integration approach
• Address Mapping guide – Advanced address handling
• Field Transformations – Data transformation options
• Error Handling – Handle sync failures