CRM Field Sync: Keep OnRamp and Your CRM in Step (Beta)

Last updated: September 29, 2026

CRM Field Sync: Keep OnRamp and Your CRM in Step

Category: Integrations

CRM Field Sync keeps an OnRamp field and a Salesforce or HubSpot field holding the same value, for as long as the record is active, not just when a project is created. You map a CRM field to an OnRamp field once, choose which way values travel, and OnRamp handles the rest. You don't need to build a workflow or automation for it.

A workflow copies CRM values into a project one time, when it creates the project. Field sync keeps going after that, but only for the fields you map, and only in the direction you choose. Nothing syncs until you create a mapping. For example:

  • If you map a Salesforce Projected Go-Live Date field to the project's End Date with a direction of To OnRamp or Two-way, then when someone changes the Projected Go-Live Date in Salesforce, the project's end date changes too.

  • If you map an OnRamp Go-Live Status data field to a CRM field with a direction of To CRM or Two-way, then when your team updates it in OnRamp, the CRM gets the new value.

What Can Be Synced

On the CRM side, you can use any field on a CRM object your integration exposes: Opportunity, Account, Deal, Company, Contact, custom objects, and so on.

On the OnRamp side, you can use:

  • Data fields on Projects, Tasks, Accounts, Customer Members and Internal Users.

  • Standard project fields: Project Name, Start Date, End Date and Project Value.

  • Standard account fields: Account Name and Website.

  • Subtask fields. These are questions inside a task that are bound to a CRM field in the task builder.

The Four Sync Directions

Each mapping has its own direction:

  • To OnRamp: CRM changes update OnRamp. Edits made in OnRamp stay in OnRamp and are never sent to the CRM.

  • To CRM: OnRamp edits are written to the CRM. CRM changes never overwrite OnRamp. This suits values your onboarding team owns, like go-live confirmed, percent complete or portal status.

  • Two-way: Changes travel both ways. If both sides change, the more recent change wins.

  • Once, at record creation: OnRamp reads the CRM value one time, when the record is first linked, and then stops for that record. This works like a workflow's "populate at creation."

What a Record Needs in Order to Sync

Field sync follows the link between an OnRamp record and its CRM record. A record syncs only if it has one of these links:

  • Projects are linked when a workflow creates them, from Project › Settings › Integrations, or through the OnRamp API.

  • Tasks sync through their project's CRM record.

  • Accounts and users are linked through the CRM record link on their profile.

Syncing stops when a record is finished. Completed, archived or deleted projects and tasks, archived accounts, and disabled users are frozen. Nothing moves in either direction for them, so a closed-out project's values can't change after the fact.

Who Can Use It

Only Super Admins can set up mappings. Field sync is turned on for each organization, so if you don't see CRM field sync in Settings, contact your OnRamp team to have it enabled.

Related Articles

  • Setting Up CRM Field Mappings

  • How CRM Field Sync Moves Values

  • Troubleshooting CRM Field Sync