HaloPSA opportunity custom fields and quotes

HaloPSA lets you store extra information on opportunities as custom fields. Those values do not appear on Salesbuildr quotes or quote widgets. Salesbuildr does not show an error or a warning when this happens — the fields are simply ignored.

This article explains what syncs, what the Public API can do, and what to expect in the product.

For the initial HaloPSA connection and field mapping, see HaloPSA Setup. For Autotask opportunity custom fields (User Defined Fields), see Opportunity UDF → Autotask sync.

HaloPSA custom fields are not imported

Salesbuildr does not read HaloPSA custom fields on opportunities, quotations, companies, or other Halo records.

That means:

• Custom field values you enter on a HaloPSA opportunity are not copied onto the linked Salesbuildr opportunity.
• Those values are not used to fill a Salesbuildr quote, a quote widget, or a form field on a quote.
• There is no mapping screen under Settings > Integrations > HaloPSA for Halo custom fields. The Opportunities tab maps opportunity types and statuses only.

Standard opportunity details still sync as usual — name, status, company, contact, and the other fields you configure during HaloPSA Setup. Custom fields are the gap.

Salesbuildr data points (custom fields you define in Salesbuildr under Settings > Custom Fields) are separate. You can still fill those on an opportunity or a quote in Salesbuildr. They do not map to HaloPSA custom fields.

Quote sync is one-way (Salesbuildr → HaloPSA)

Quote sync with HaloPSA is push-only. When you create or update a quote in Salesbuildr, Salesbuildr sends the quote header, line items, and attachments to HaloPSA as a quotation.

Salesbuildr does not import quotations from HaloPSA. Changes you make to a quotation in Halo — including custom fields, line items, and status — do not come back into Salesbuildr.

Opportunity status can still move in both directions when you have mapped statuses on Settings > Integrations > HaloPSA > Opportunities. That updates the opportunity only. It does not pull Halo custom fields, and it does not change the quote.

Approve and send quotes in Salesbuildr, not in HaloPSA. Approving a quotation only in Halo leaves the Salesbuildr quote on its previous status.

Public API

If the Public API is enabled on your account, you can create a Salesbuildr quote and include products. Those products become line items on the new quote.

The Public API cannot:

• Create or fill quote widgets (content, forms, images, summaries, and similar sections)
• Update a quotation that already exists in HaloPSA
• Send HaloPSA custom field values onto a quote or widget

A create call that succeeds still produces a quote with products. Widgets stay empty unless someone adds them later in the quote editor, or you create the quote from a Salesbuildr template that already has those sections. Halo custom field data is not applied in either case.

You can change a draft quote's header in Salesbuildr through the Public API (title, notes, payment term, and similar fields). That does not fill widgets, does not write Halo custom fields, and is not a way to edit an existing Halo quotation.

What you will see

There is no error, toast, or issue under Settings > Tools > Issues when Halo custom fields are skipped. Sync can look healthy while the extra Halo data is missing.

Typical signs:

• The HaloPSA opportunity shows custom field values, but the Salesbuildr opportunity and quote do not.
• A quote widget or form you expected to pre-fill from Halo is blank.
• An integration that creates quotes through the Public API adds products, but widgets and Halo custom fields never appear.

This is expected today. If a value must appear on a Salesbuildr quote, enter it in Salesbuildr — on the opportunity, in a quote widget, or as a line item.

See also

• HaloPSA Setup — connect HaloPSA and map types, statuses, and quote statuses
• Custom Fields — Salesbuildr data points on products, companies, and opportunities
• Quote Editor — widgets, forms, and line items
• Public API — create quotes with products, draft header updates, and rate limits
• Opportunity UDF → Autotask sync — Autotask opportunity custom field mapping (Autotask only)
• PSA Sync Issues — errors that do appear when a sync fails