# Link Hub Well

> How HubSpot connects to other systems.


## Pages

- [Glossary](https://linkhubwell.com/glossary/): The terms on the map pages. Each one is a decision, not a product name.
- [Troubleshooting](https://linkhubwell.com/troubleshooting/): Most failures are a key, a status nobody mapped, or a field both sides were allowed to edit. Start there before you rebuild the connector.
- [Sync patterns](https://linkhubwell.com/sync-patterns/): A sync pattern is the rule for one flow: which object, which way, what identifies a match, and what happens when both sides changed.
- [Native, iPaaS, or custom API](https://linkhubwell.com/approaches/): Pick from the objects you must move, the volume, and the person who will still understand the connection in a year.
- [Warehouse and BI](https://linkhubwell.com/warehouse/): Snowflake, BigQuery, Power BI, and Looker should read HubSpot on a schedule you can explain.
- [Finance and billing](https://linkhubwell.com/finance/): QuickBooks, Xero, Stripe, and the rest know what was billed and what was paid. HubSpot should show that status to the owner.
- [Ecommerce and HubSpot](https://linkhubwell.com/ecommerce/): Shopify, WooCommerce, and Magento already have the customer.
- [ERP and HubSpot](https://linkhubwell.com/erp/): SAP, NetSuite, Dynamics, and Odoo already know the customer, the order, and the invoice.
- [Integrations by system](https://linkhubwell.com/systems/): HubSpot is one side of the map. The other side decides the objects, the direction, and the failures you will actually see.
- [Home](https://linkhubwell.com/): How HubSpot meets ERP, ecommerce, billing, and the warehouse: what syncs, which way, and where the record breaks.


[comment]: # (Generated by Hostinger Tools Plugin)