Integration Overview · HubSpot and MYOB AccountRight

Sansai Australia

A first view of the integration between HubSpot and MYOB AccountRight: what Sansai has asked for, how data would flow between the two systems, and what we settle together at discovery.

Prepared for

Sansai Australia

Systems

HubSpot ↔ MYOB AccountRight

Status

Draft for discovery

Date

11 August 2026

01The ask

Sansai Australia is an Australian owned supplier of electrical and consumer electronics products, operating from Melbourne and Sydney with expansion into other states planned. The sales operation runs on MYOB AccountRight today, and the manual handling around it is the core problem.

• Orders are not entered the moment they are taken, so they queue for manual entry.
• Data is double handled between the field and the office.
• Reps lack customer context in the field: purchasing history, order values and open opportunities.
• Administration eats into selling time.

Sansai is evaluating HubSpot, with Sales Hub Professional and Revenue Hub Professional central to the current package discussion and around eight users at launch. A strong HubSpot to MYOB integration is the central requirement: it needs to cut manual administration and give sales and leadership a complete view of customer activity, from purchasing history and order values through to opportunities and performance reporting.

At this stage Sansai has asked Kongo for three things: a view on whether the integration requirements can be supported, an implementation price range for internal discussions, and clarity on recurring integration, hosting and maintenance costs. This document is the starting point for the first, a map of what would sync and in which direction, ready to test and refine at discovery.

02How the data would flow

A first pass at the sync directions, drawn from the briefing. Anything marked to confirm is settled at discovery before it shapes scope or price.

03Object by object

Object	Direction	Purpose	Status
Contacts & companies	HubSpot ↔ MYOB	Keep customer records aligned across both systems so reps and finance work from the same data.	As briefed
Deals, quotes & orders	HubSpot → MYOB	Reps capture opportunities, and potentially place orders, in HubSpot; these pass into MYOB for processing.	As briefed. Whether reps place orders or only capture them is open
Invoices, payments & revenue	MYOB → HubSpot	Order values, invoices, payments and revenue flow back into HubSpot for visibility and reporting.	As briefed
Product catalogue, pricing & tier logic	To confirm	Sansai's catalogue, customer specific pricing and tier logic need a home. On the HubSpot side this points to Revenue Hub Professional, which provides CPQ with price books, tiered pricing and pricing rules (price books were still in beta as at July 2026). The open questions are how MYOB's items and price levels reach HubSpot, and which system owns pricing.	Requirement raised; direction and approach settled at discovery
Purchasing history	MYOB → HubSpot	Give field reps and management visibility of buying habits, order values and sales performance.	As briefed; sourced from MYOB sales history

04What we settle at discovery

Six questions decide the shape and price of the integration. None of them blocks the project; each one just needs an answer before the build is scoped.

• Where quoting happens. If reps quote in HubSpot, the catalogue, customer pricing and tier logic must work natively there through Revenue Hub Professional's CPQ and price books, which changes scope and adds per seat cost. If quotes stay in MYOB, the integration is considerably simpler.
• Order placement or order capture. Whether reps place orders in HubSpot or only capture them drives both the build effort and the level of write access the integration needs into MYOB.
• System of record rules. With data flowing both ways, we agree what MYOB owns and what HubSpot owns (customers, pricing, orders) before any build.
• Pricing and tier logic. How customer specific pricing works in MYOB today, and whether MYOB price levels sync into HubSpot price books automatically or are maintained manually.
• Recurring costs. Integration hosting follows the pay-as-you-go tiers in the next section. Maintenance and support are scoped alongside the implementation range, so the full picture is on the table for the director conversation.
• MYOB AccountRight setup. We map the current company file structure, customisations and data quality, all of which affect feasibility and price.

05Integration hosting

Hosting the integration runs on a pay-as-you-go model across four tiers, so Sansai only pays for the volume the business actually generates.

Each tier includes a monthly event allowance, with a per-event rate for anything above it. As data volume grows, you move to a higher tier with a lower effective cost per event; if volume drops, you scale back down. Usage, costs and sync activity are visible in real time through your client portal. Most clients start on the Starter tier.

Tier	Events per month	Monthly (ex GST)
Lite	5,000	$99
Starter	10,000	$149
Growth	50,000	$349
Scale	200,000	$599

06What happens next

• We work through this document together at the discovery session and correct anything that reads wrong. It is a draft, built to be challenged.
• We settle the six questions above, starting with where quoting happens and who owns pricing.
• Kongo then comes back with the implementation price range and the recurring cost picture, ready for Sansai's internal discussions.