Create Sanka orders and subscriptions from HubSpot deals while preserving customer, line item, and billing lineage.
Last updated: June 2, 2026
This guide explains how to use a HubSpot deal as the sales source, create or reuse a Sanka order, and then create a Sanka subscription from that order. Use this flow when sales work happens in HubSpot but subscriptions, billing, and accounting are managed in Sanka.
Expected behavior
Sanka should create the downstream records in this order:
HubSpot deal is reviewed as the sales source.
Sanka order is created or reused from the deal.
Sanka subscription is created from the order.
Later invoices, payments, and accounting records can trace back to the order and deal.
Before conversion, the deal needs one resolved customer. Keep exactly one company or one contact as the billing customer. If the HubSpot deal has multiple customer candidates, resolve the customer in Sanka first, then retry from the action history.HubSpot deal stages can differ from the stages already configured in Sanka. If a HubSpot-sourced stage is new, review it before using it in reports, workflows, or forecast dashboards.
Troubleshooting
The subscription was not created
Check that the deal has one customer, line items or an amount, currency, and the fields your subscription workflow requires. Then confirm whether an order was already created or reused before the subscription step.
The customer is ambiguous
If both a company and contact, or multiple customer records, are attached as candidates, Sanka blocks downstream conversion rather than guessing. Keep one billing customer and retry.
The HubSpot stage looks new
Review the imported stage name and decide whether it should be part of your Sanka pipeline. Do this before relying on it for reports or automation.
Safe AI prompt
Sample prompt
/sanka Review this HubSpot deal before creating a Sanka subscription. Confirm the single billing customer, line items, amount, currency, HubSpot stage, existing Sanka order, and whether a subscription already exists. Do not create duplicate downstream records.
