Salesforce 
HubSpot 
NetSuite 
Zendesk 
Microsoft Dynamics 365 Sales 
Dynamics 365 F&O 
Attio 
Pipedrive 
Zoho CRM 
Campfire 
Rillet 
Front 
Shopify 
Amazon Seller Central 
SendGrid Keep supported HubSpot and Rillet records aligned with two-way sync. Give each team access to current data while controlling which system can update each field.
Example workflow
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Starting eventA change involving HubSpot Company or Rillet Customer needs a defined result in the other system.
Start with HubSpot Company and Rillet Customer. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
What to verifyTest an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Review records and field ownershipMapping essentials
Match records by stable IDs and assign an owner for each field. The record notes identify the coverage to check.
Download the mapping worksheetCSV · No email required
| HubSpot record | Rillet record | Record matching | Field ownership |
|---|---|---|---|
| CompanyDocumented record: SupportedCustomer identity assessment | CustomerDocumented record: Incremental: ; historical: ; delete detection: | Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. | Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company. |
| ContactDocumented record: SupportedCustomer identity assessment | CustomerDocumented record: Incremental: ; historical: ; delete detection: | Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. | Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company. |
| InvoicesDocumented record: SupportedRecord matching | InvoiceDocumented record: Incremental: ; historical: ; delete detection: | Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap. | The financial system owns posting and accounting treatment. A posted invoice may need a credit or adjustment process instead of an overwrite. |
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Why teams connect HubSpot and Rillet
Start with the work your team needs to complete: keep records up to date, make operational data available for reporting, or move data to a new system. Choose one HubSpot and Rillet workflow to test, define what success looks like, and decide who handles failed updates.
Push product signup and usage events into HubSpot contact properties to drive lifecycle marketing segmentation.
Write warehouse-computed lead and account scores back to HubSpot properties on a schedule or in near real time.
Keep customers and invoices aligned between Rillet and a CRM so finance and sales work from the same account records.
Mirror journal entries and contract revenue data into a warehouse for board and ARR reporting.
Start with the records your workflow needs. Check each system’s read and write requirements before mapping fields.
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| ✅ Supported. Confirm field permissions and sync direction. |
| 🕘 Coming soon. Confirm field permissions and sync direction. |
| ❌ Not supported. Confirm field permissions and sync direction. |
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| Incremental: ✅; historical: ✅; delete detection: ✅. Confirm field permissions and sync direction. |
| Incremental: ✅; historical: ✅; delete detection: ✅ Every 1h. Confirm field permissions and sync direction. |
| Incremental: ❌; historical: ✅; delete detection: ✅ Every 1h. Confirm field permissions and sync direction. |
| Incremental: ❌; historical: ✅; delete detection: ✅ Every 4h. Confirm field permissions and sync direction. |
Review how each system connects, detects changes, and permits access to your records.
View setup requirements and limits| Connection requirement | HubSpot | Rillet |
|---|---|---|
| Integration interface | REST API (CRM v3) | REST API (OpenAPI-specified, with production and sandbox environments) |
| Authentication | OAuth | API key generated in Rillet |
| Change detection | Record updates and association changes need separate validation. | Historical and incremental syncs are documented by object. |
| Read access | Available for supported records | Available for supported records |
| Write access | Available for supported records | Available for supported records |
Enterprise controls
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Inspect sync errors and use retry and revert controls to resolve failed updates.
Read the recovery guideImplementation
Review setup, record relationships, testing, and recovery for your implementation.
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.
Setup guides: Authorize HubSpot
Setup guides: Authorize Rillet Connection
Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.
Use the HubSpot and Rillet planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
Keep each record tied to its source ID. Use the references below to choose field owners and preserve relationships between records.
Download the mapping worksheet · CSV, no email required
Customer identity
Before linking HubSpot Company to Rillet Customer, check whether the customer is an individual or a company. Match the correct record type in each system.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Fields to include
References: HubSpot: Company documentationRillet: Customer documentation
Customer identity
Before linking HubSpot Contact to Rillet Customer, check whether the customer is an individual or a company. Match the correct record type in each system.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Fields to include
References: HubSpot: Contact documentationRillet: Customer documentation
Record matching
Compare whether HubSpot Invoices and Rillet Invoice describe the same customer invoice in your business.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Fields to include
References: HubSpot: Invoices documentationRillet: Invoice documentation
Record matching
Compare whether HubSpot Commerce Payments and Rillet Invoice Payment describe the same payment or settlement in your business.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Fields to include
References: HubSpot: Commerce Payments documentationRillet: Invoice Payment documentation
Use HubSpot Company and Rillet Customer for the first pilot. Verify its identity and permitted direction, then add dependent records only when the acceptance checks pass.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Starting event: A change to the selected Company or Customer record needs a defined result in the other system.
Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Starting event: A change to the selected Contact or Customer record needs a defined result in the other system.
Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Starting event: A change to the selected Invoices or Invoice record needs a defined result in the other system.
Expected result: Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.
If it fails: Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.
Validate the selected objects and operations even where connector-level direction is documented.
Starting event: A finance-owned record in Rillet needs operational visibility through Contact or Company.
Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.
If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
The expected customer relationship is preserved with no duplicate action or unintended write.
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
The expected customer relationship is preserved with no duplicate action or unintended write.
Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.
The expected customer invoice relationship is preserved with no duplicate action or unintended write.
Test partial payment, one-to-many allocation, refund, and repeated delivery of the same transaction.
The expected payment or settlement relationship is preserved with no duplicate action or unintended write.
Check that each connected account can read and write the chosen objects. Exercise both directions with a test record before enabling production changes.
Only an approved, supported direction and permitted fields are written.
Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.
The process meets its agreed freshness target and reconciliation has no unexplained differences.
Start with the failed record and the destination error, then inspect the source value, field requirements, and access.
Inspect HubSpot Company and Rillet Customer, their IDs, and the destination error.
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Inspect HubSpot Contact and Rillet Customer, their IDs, and the destination error.
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Inspect HubSpot Invoices and Rillet Invoice, their IDs, and the destination error.
Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.
Check the HubSpot and Rillet connector guides, account permissions, and any operations marked On Request.
Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.
Compare current source values, destination validation, identity mappings, and any side effects already completed.
Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.
Read the Stacksync issues dashboard guide for retry and revert behavior.
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
Detect changesRecord updates and association changes need separate validation. Association detection uses full scans unless Associations CDC Boost is configured for an eligible account.
Apply updatesSelected writable fields update in Rillet. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Detect changesHistorical and incremental syncs are documented by object. Some objects have only historical sync; delete detection intervals vary.
Apply updatesSelected writable fields update in HubSpot. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Stacksync connects HubSpot and Rillet with two-way sync for supported records. Authorize the accounts, select the record types, and map compatible fields. Both connectors support reading and writing; object permissions determine the available fields. Use the Issues dashboard to inspect and resolve rejected updates.
Stacksync supports two-way sync between writable records in both systems. The chosen objects and fields must permit updates in both directions. Read-only fields can supply values but cannot receive updates. Stacksync can read database views; it does not write back to the view.
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Have a HubSpot Super Admin authorize Stacksync through the account connection flow. Generate an API key in Rillet Organization Setting > API Access. Use the pair worksheet to record ownership and acceptance criteria.
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
Start by reviewing Company in HubSpot and Customer in Rillet. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.
Use HubSpot Company and Rillet Customer for the first pilot. Verify its identity and permitted direction, then add dependent records only when the acceptance checks pass.
Integration directory
Review documented support, sync direction, and setup requirements on each pair page. Search all 457 integrations listed for HubSpot and Rillet.
Popular · 7 of 457
HubSpot and Hyperline 
HubSpot and Pigment 
HubSpot and QuickBooks 
HubSpot and Stripe Rillet and Salesforce Rillet and Microsoft Dynamics 365 Sales Rillet and Attio Next step
Walk through your HubSpot and Rillet records, field mappings, and requirements with an integration engineer.
