Ticketing → HubSpot · custom objects
An opera house, its ticketing system
- The software
- The venue's ticketing system, reached through the API its vendor exposes.
- In HubSpot
- Shows, sessions, seats, orders and contacts as custom objects, linked to each other, with a card on the record showing what each contact bought.
- Volume
- 921,325 records backfilled from 2000 onward, then every change since.
- On their side
- The vendor exposed the API. The venue's team changed nothing in how it sells tickets.
What it changes: A ticketing history going back 26 years, usable in HubSpot from the first sync.
FileMaker ERP → HubSpot · custom objects
A language school, its in-house ERP
- The software
- The school's own ERP built on FileMaker: 257 tables across 16 files, of which a dozen carry the commercial core.
- In HubSpot
- Companies, learners, enrolments and invoices as native and custom objects, linked to each other.
- Volume
- About 100,000 learners and 110,000 invoices to backfill.
- On their side
- An API specification handed to the software's maintainer: incremental reads only. Nothing else.
What it changes: No connector existed for this software anywhere. One will, without the school writing a line of it.