Troubleshooting CRM Field Sync (Beta)

Last updated: September 29, 2026

Troubleshooting CRM Field Sync

Category: Integrations

Start with the Health column on Settings › CRM field sync. It shows how each mapping's most recent write went. Hover over a status for the detail, or click it to open the sync log.

Health Statuses

  • Healthy: the last write went through, or nothing is waiting.

  • Queued: a change is waiting to be sent. This usually clears within seconds.

  • Filling in: records linked before the mapping was added are still being brought into step. Click Sync now to speed it up.

  • Retrying: the CRM refused a write, and OnRamp will try again. The tooltip shows the CRM's response.

  • Failing: the CRM kept refusing the write. The tooltip gives the reason, such as a validation rule, a permission, or a field that was deleted in the CRM.

  • Not delivered: the change was deliberately not sent, for example because the project was completed before it went out. This isn't an error.

  • Picklist mismatch: the OnRamp field offers options the CRM picklist doesn't have. See below.

Common Questions

I changed a value in the CRM, but OnRamp still shows the old one.
First, check that the field is mapped with a direction of To OnRamp or Two-way. Only those carry CRM changes into OnRamp. If it is, keep in mind that CRM changes can take up to 15 minutes to arrive. Open the record or click Sync with CRM to read it right away. The summary tells you why a value didn't change. Common reasons:

  • The OnRamp edit is more recent: on a Two-way mapping, the newer OnRamp edit won.

  • This record is finished, so nothing syncs: the project or task is completed, archived or deleted.

  • Left alone, the mapping does not carry values that way: the mapping is set to To CRM.

  • An OnRamp write to the CRM is still in flight: OnRamp waits for its own send to finish first.

  • This record is not linked to a CRM record: link it from Project › Settings › Integrations, or from the account or user profile.

My formula (or rollup) field in the CRM isn't updating in OnRamp.
CRMs don't flag formula fields as changed, so a formula field mapped To OnRamp or Two-way is re-read once a night. Open the record or click Sync to pick up the latest value sooner.

A dropdown value shows "Not in Salesforce" (or HubSpot).
The value chosen in OnRamp isn't an option in the CRM's picklist, so it stays in OnRamp. Every other field on the record still syncs. Add the option in the CRM, or choose one the CRM has. To bring the CRM's options into OnRamp, use Add N CRM options on the mapping.

A direction is greyed out when I create a mapping.
Hover over it to see why. Common reasons:

  • The CRM calculates the field, so it can't be written.

  • The CRM marks the field read-only.

  • The two field types can't hold the same value.

  • Writing back would change the value the CRM holds, for example rounding or truncating it.

You can still use To OnRamp for these fields.

My edit in OnRamp was overwritten.
Check the field's tag. A From CRM field is replaced by the next CRM change. A Two-way field takes whichever change is newer. Also check the mapping row for an Also written by badge. A workflow, automation or second mapping writing the same field can overwrite it, because the last write wins.

I changed a subtask field's direction, but existing projects didn't change.
That's expected. Subtask bindings are copied into each project when it's created, so changes reach new projects only.

I don't see CRM field sync in Settings.
You need the Super Admin role, and field sync must be enabled for your organization. Contact your OnRamp team.

Does deleting a mapping remove any data?
No. Values already written stay in both OnRamp and the CRM. Syncing simply stops.