BidScript connects with HubSpot so your team can import deals as projects, keep deal information aligned, and bring related HubSpot files into your workspace.

Before importing deals, HubSpot must be connected in BidScript.

If BidScript cannot access HubSpot, you’ll see a HubSpot connection required message with a shortcut back to Integrations.

To create BidScript projects from HubSpot deals:

The import table shows each deal’s name, client, stage, close date, and amount. Deals already imported into BidScript are marked as Already imported and cannot be selected again.

Before importing, BidScript asks you to confirm how HubSpot deal stages should map to BidScript project statuses.

For example:

BidScript will suggest mappings where possible. Any stage that cannot be mapped automatically is highlighted for review. Once confirmed, mappings are saved and reused for future imports and ongoing syncs.

You can update HubSpot mappings at any time.

These mappings are used when importing HubSpot deals and when syncing HubSpot projects.

After import, the HubSpot deal becomes a BidScript project. BidScript stores the HubSpot deal link and key deal information, including:

From the project overview, you can sync the latest HubSpot data into BidScript using Sync from HubSpot.

HubSpot-linked projects can sync in both directions for supported fields.

When you update supported project fields in BidScript, BidScript attempts to update the linked HubSpot deal. Supported fields include:

Some fields remain managed by HubSpot. For example, the primary company is read-only in BidScript and should be edited in HubSpot.

BidScript also runs background syncs to keep HubSpot-linked projects up to date. You can manually refresh a project by clicking Sync from HubSpot.

During import and manual sync, BidScript attempts to import files associated with the HubSpot deal. If some files cannot be imported, the project can still be created or synced, and BidScript will show a file import issue message.