FluxCascade
FeaturesConnectorsPricingDocsBlog

Getting Started

  • Introduction
  • Quick Start
  • Core Concepts

Integrations

  • Overview
  • HubSpot
  • Jobber
  • Pipedrive
  • Salesforce

Field Mappings

  • Creating Mappings
  • Field Transformations
  • Bidirectional Sync
  • Conflict Resolution

Syncing Data

  • How Syncs Work
  • Scheduling
  • Webhooks
  • Error Handling

API Reference

  • Overview
  • Authentication
  • Connections
  • Mappings
  • Syncs
  • Webhooks

Guides

  • All Guides
  • HubSpot + Jobber
  • Deals to Jobs
  • Address Mapping

Security

  • Data Privacy
  • Encryption
  • Compliance

Support

  • FAQ
  • Troubleshooting
  • Contact Us

Creating Field Mappings

Field mappings are the heart of FluxCascade. They define how data flows between your connected systems, specifying which fields in one platform correspond to fields in another.

What is a Mapping?

A mapping is a configuration that connects two systems and defines:

  • Source: The system and object type where data originates (e.g., HubSpot Contacts)
  • Target: The system and object type where data is sent (e.g., Jobber Clients)
  • Direction: Whether data flows one-way or bidirectionally
  • Field Pairs: Which fields map to each other between systems

Creating Your First Mapping

Step 1: Navigate to Mappings

  1. Log in to FluxCascade
  2. Click Mappings in the sidebar
  3. Click the New Mapping button

Step 2: Select Source and Target

Choose your source and target systems:

SettingDescriptionExample
Source ConnectionThe system to pull data fromHubSpot (My Company)
Source ObjectThe type of record to syncContacts
Target ConnectionThe system to push data toJobber (Field Services)
Target ObjectThe type of record to create/updateClients

Step 3: Choose Sync Direction

Select how data should flow between systems:

DirectionBehaviorUse Case
source_to_targetData only flows from source → targetCRM is your source of truth
target_to_sourceData only flows from target → sourceField service app is source of truth
bidirectionalData syncs both waysBoth teams update records

Step 4: Configure Field Pairs

Map individual fields between the source and target objects. FluxCascade provides intelligent suggestions based on field names and types.

For each field pair, you can configure:

  • Source Field: The field to read from
  • Target Field: The field to write to
  • Transform: An optional transformation to apply (see Field Transformations)
  • Required: Whether this field is mandatory for sync

Step 5: Name and Save

Give your mapping a descriptive name and optional description:

Name: HubSpot → Jobber: Contacts to Clients
Description: Syncs marketing contacts to field service client database

Click Save Mapping to create it.

Mapping Configuration Options

Matching Strategy

FluxCascade needs to know how to match records between systems to avoid duplicates:

StrategyDescription
Email MatchMatch contacts by email address (most common)
Phone MatchMatch by phone number (normalized)
External IDUse a custom field to store the foreign ID
Composite KeyMatch on multiple fields (name + company)

Filtering Records

You can filter which records are synced:

  • All Records: Sync every record in the source object
  • Recently Modified: Only sync records changed since the last sync
  • Custom Filter: Define criteria (e.g., only contacts with email addresses)

Managing Mappings

Editing a Mapping

  1. Go to Mappings
  2. Click on the mapping you want to edit
  3. Click Edit Mapping
  4. Make your changes
  5. Click Save

Changes take effect on the next sync.

Activating/Deactivating

Toggle mappings on or off without deleting them:

  • Active: Mapping will be included in scheduled and webhook-triggered syncs
  • Inactive: Mapping is paused but configuration is preserved

Deleting a Mapping

  1. Go to Mappings
  2. Click the mapping to delete
  3. Click Delete Mapping
  4. Confirm deletion

Note: Deleting a mapping does not delete data in either system – it only removes the sync configuration.

Best Practices

Start Small

Begin with essential fields only:

  • Name fields (first, last)
  • Email and phone
  • One or two custom fields

Add more fields after verifying the initial sync works correctly.

Use Descriptive Names

Name mappings clearly so team members understand them:

✓ HubSpot → Jobber: Contacts to Clients
✓ Pipedrive Deals → Jobber Jobs (One-way)
✗ Mapping 1
✗ Test

Test Before Going Live

  1. Create the mapping
  2. Run a test sync with a small subset of records
  3. Verify data appears correctly in both systems
  4. Enable scheduled syncing

Document Your Mappings

Use the description field to note:

  • Why the mapping exists
  • Any special transformation logic
  • Who requested it and when

Next Steps

  • Field Transformations – Apply transforms to data as it syncs
  • Bidirectional Sync – Keep both systems in sync
  • Conflict Resolution – Handle conflicting updates
FluxCascade

The modern data integration platform. Connect your systems, sync your data, automate your workflows.

Product

  • Features
  • Pricing
  • Connectors
  • Changelog

Resources

  • Documentation
  • API Reference
  • Guides
  • Blog

Company

  • About
  • Contact
  • Privacy Policy
  • Terms of Service

Connect

  • Twitter
  • GitHub
  • Discord
  • LinkedIn

© 2026 FluxCascade. All rights reserved.

PrivacyTermsSecurity