CRM field sync

Updated

CRM field sync keeps an OnRamp field and a Salesforce or HubSpot field holding the same value after a project is created. You map a CRM field to an OnRamp field once and choose which way values travel. You don't need to build a workflow or automation for it.

CRM field sync is available when it's turned on for your organization. If you don't see it, contact your OnRamp team.

When to use 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 date field to the project's End date with a direction of To OnRamp or Two-way, a change to that date in Salesforce moves the project's end date.

  • If you map an OnRamp data field to a CRM field with a direction of To CRM or Two-way, your team's edits in OnRamp are sent to the CRM.

How it works

Field sync needs a CRM connected under Integrations+. Until one is connected, the CRM field sync page asks you to connect your CRM under Integrations+ in Settings. You add mappings on that page with Add mapping, or map many fields at once with Auto-match fields. If you remove a mapping, values already written stay where they are.

What you can map

On the CRM side, some fields are locked. Calculated or read-only CRM fields can't receive values from OnRamp. A field whose type doesn't match, or that would lose data when written, can't be mapped in that direction.

On the OnRamp side, you can use:

  • Data fields on projects, tasks, accounts, customer users and internal users.

  • Standard project fields. Project name, Start date, End date and Project value can sync in any direction. OnRamp calculates the rest, so it only sends them to your CRM: Customer name, Owner name, Status, Completed date, Completion percentage, Next task name, On-time performance, Engagement score, Project org site URL, Number of days active and Project UUID.

  • Standard account fields: Account name, Website, Email, Location, Renewal date and Licences.

  • Subtask fields. These live on the playbook or library task, and you choose the CRM field in the task builder. They're copied into each project when it's created. They also appear on the CRM field sync page under Subtask fields. If you can edit mappings, you'll see an Add subtask field button there. A direction you change there reaches new projects only.

Sync directions

Each mapping has its own direction:

  • To OnRamp: CRM changes update OnRamp. Edits in OnRamp stay in OnRamp.

  • 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 once, when the record is first linked, then stops for that record. This works like a workflow filling a field when it creates a project.

What a record needs to sync

Field sync follows the link between an OnRamp record and its CRM record:

  • Projects list their linked CRM records in the project's settings, under Project Integrations+ Settings. The records show there when Integrations+ is turned on for your organization and your access role lets you view integration connections. If your access role also lets you change CRM links, you can select Add entity to link a record, or remove a linked one.

  • Tasks sync through a CRM link of their own and through their project's CRM record. Because a task data field syncs through the project's record, editing it on one task sends the new value to the CRM when the mapping's direction is To CRM or Two-way. When the direction is Two-way, that value then comes back from the CRM to every other open task in the project that holds the field.

  • Accounts and users sync through the CRM record link stored for them.

A live project with no link of its own to a Salesforce Account or HubSpot company can still sync through its primary account. Its project data fields and synced subtask answers use the account's CRM link. Its standard project fields don't sync this way.

Who can use it

Super Admins and Integrators whose access role lets them edit field sync mappings can set them up. Others with view access see the mappings but can't change them. CRM field sync appears in Settings only when the feature is on and your access role lets you view field sync.

Limits

Syncing stops when a record is finished. These records are frozen:

  • Completed, archived or deleted projects.

  • Completed, archived or deleted tasks, plus every task in a frozen project.

  • Archived or deleted accounts.

  • Inactive, disabled or deleted internal users and customer users.

For one day after a project is completed, OnRamp can still send its calculated fields to your CRM. After that, or right away if the project is archived or deleted, nothing moves in either direction.

More in Integrations