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
- Log in to FluxCascade
- Click Mappings in the sidebar
- Click the New Mapping button
Step 2: Select Source and Target
Choose your source and target systems:
| Setting | Description | Example |
|---|---|---|
| Source Connection | The system to pull data from | HubSpot (My Company) |
| Source Object | The type of record to sync | Contacts |
| Target Connection | The system to push data to | Jobber (Field Services) |
| Target Object | The type of record to create/update | Clients |
Step 3: Choose Sync Direction
Select how data should flow between systems:
| Direction | Behavior | Use Case |
|---|---|---|
source_to_target | Data only flows from source → target | CRM is your source of truth |
target_to_source | Data only flows from target → source | Field service app is source of truth |
bidirectional | Data syncs both ways | Both 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:
| Strategy | Description |
|---|---|
| Email Match | Match contacts by email address (most common) |
| Phone Match | Match by phone number (normalized) |
| External ID | Use a custom field to store the foreign ID |
| Composite Key | Match 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
- Go to Mappings
- Click on the mapping you want to edit
- Click Edit Mapping
- Make your changes
- 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
- Go to Mappings
- Click the mapping to delete
- Click Delete Mapping
- 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
- Create the mapping
- Run a test sync with a small subset of records
- Verify data appears correctly in both systems
- 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