Current behavior:

When forms are embedded in an agreement template with "Merge client data" toggled on, the form data only maps to client custom fields — not to opportunity custom fields or contact custom fields, even when the agreement is linked to an opportunity.

According to Moxie support: "The agreement only works one way, there's nothing in the agreement flows that update opportunity data. So it's only agreement → client and not agreement → opportunity."

The inconsistency:

If I send a form directly to a client and it has fields mapped to client custom fields, contact custom fields, and/or opportunity custom fields, all three types of fields will be mapped when the client submits the form.

But if I embed that exact same form in an agreement and send it to the client, only the client custom fields get mapped — contact custom fields and opportunity custom fields don't. This creates an inconsistent experience depending on how the form is delivered.

The issue:

Forms embedded in agreements often capture information that's project-specific, not client-specific. This information should map to opportunity custom fields, but currently can't.

Example:

I have a form embedded in an agreement that asks clients to confirm the pages they want on their website. The package includes 8 pages, and the form asks them to list the names of those 8 pages. This is project-specific information — it's not relevant to the client record overall, so I want it mapped to an opportunity custom field. At the moment, that's not possible.

Current workaround:

To capture this data in opportunity custom fields, you have to either not embed the form in the agreement and send it separately instead (which creates extra steps and a less seamless client experience), manually copy the information from the embedded form submission to the opportunity custom field, or only use client custom fields as mapping keys in embedded forms (even when the data is project-specific and doesn't belong on the client record). None of these options are ideal.

Requested feature:

Allow embedded forms in agreements to map data to client custom fields, contact custom fields, AND opportunity custom fields when "Merge client data" is enabled and the agreement is linked to an opportunity — matching the behaviour of forms that are not embedded.