Mapping CRM Data into OnRamp Using Data Fields

Last updated: February 18, 2026

Once you’ve created Data Fields, the next step is connecting them to your CRM.

This is how you eliminate manual entry and keep onboarding data aligned across systems.

When Does CRM Mapping Happen?

CRM → OnRamp mapping happens inside Workflows.

Specifically:

  • During project creation

  • Inside the Project Data Fields card

This ensures values are populated the moment a project is created.

How to Map CRM Fields to Data Fields

Step 1 — Open Your Workflow

Go to:

Workflows → Select Workflow

Open the version you want to edit (or create a new version).

Step 2 — Locate the “Project Data Fields” Card

This card appears only if:

  • The selected Playbook includes Data Fields

If your Playbook has none, the card won’t appear.

Step 3 — Map CRM Fields

For each Data Field:

  • Select the CRM field from your triggering object

  • Or assign a fixed value

Examples:

  • CRM Industry → Industry Data Field

  • CRM Implementation Type → Implementation Type Data Field

Step 4 — Save & Publish

Once mapped:

  • Save the Workflow version

  • Publish it

From now on, any new project created through that Workflow will have those fields pre-filled automatically.

What Happens During Execution?

When your CRM record meets trigger criteria:

  1. CRM sends the payload to OnRamp

  2. OnRamp processes the Workflow

  3. Data Fields are populated based on your mappings

  4. Project is created with structured data already in place

No copying. No manual edits.

Common Mapping Issues

If a Data Field isn’t populating:

  • Confirm the CRM field exists on the triggering object

  • Confirm the integration user has read access

  • Confirm data types match

  • Confirm you’re using the correct Workflow version

If the Workflow runs but the value is blank — it’s usually a mapping or permission issue.

Why This Matters

When CRM data maps directly into OnRamp:

  • Reporting becomes powerful

  • Automations become smarter

  • CRM write-back becomes easier

  • Manual errors disappear

It turns onboarding into a structured system — not a collection of tasks.