Skip to main content

​
Overview

Field mapping connects data from your integrated systems (Salesforce, HubSpot, Stripe, etc.) to Quivly objects. Map external fields to core Quivly fields or create custom fields during the process.

​
Prerequisites

  • Integration is connected and has synced data
  • You have Admin access
For an initial Monaco or Octolane account import, ask your Quivly onboarding team to review and save the account import scope first, including an explicit choice when all accounts should be imported. Connecting the CRM alone does not complete this setup. See CRM import scope.

​
Configuring Field Mappings

1

Navigate to Object Settings

Go to Data → Objects → Select the object you want to configure (e.g., Customers)
2

Select Integration

In the Configuration tab, select which integration to map from the dropdown.
Once you save a mapping, the integration is locked and can only be changed by support.
3

View Available Fields

The left panel shows all fields available from the external system. Use the search box to filter fields. Hover over fields to see sample values.
4

Map Fields

For each external field you want to sync:
  1. Click the field
  2. Select a Quivly field from the dropdown, or click Create New Field to add a custom field
  3. The mapping is staged — an “Unsaved changes” badge appears until you save
5

Create Custom Fields (Optional)

When creating a new field:
  • Enter a field label
  • Select the field type (string, number, boolean, date, email, url, json, or reference)
  • For reference fields, select which object it links to
6

Save Configuration

Choose Save changes, or Save & start import where offered for an initial CRM mapping. Saved mappings are used as incoming records are processed. This saves field mappings; it does not edit your account import filter.

​
Field Types

​
Auto-Computed Fields

Some fields are automatically computed by Quivly and cannot be manually mapped. These appear in a separate “Auto-computed Fields” section with a lock icon.

​
Notes

  • Each external field can only be mapped to one Quivly field
  • Core field mappings are locked after first save
  • Use the Raw Data Preview section to see sample data from the external system
  • Monaco and Octolane provide defaults for all their supported objects. Core conversions remain locked; add custom mappings for the additional fields you need.
  • A connected source can have received data that has not yet become a customer record. Check that the required mappings and import scope are saved, then inspect processing in the integration’s Logs.