No sugar-coating. The stuff that's identical, the stuff that's different, all on one page — so you can plan for the differences before you flip the switch.
Timed-entry admission products
— Your admission + exhibit timed-entry slots map cleanly to TripStub's schedules with soft-capacity throttles.Membership list
— Member records import with email, tier, renewal date, and ACME external ID preserved. Your member's barcode keeps working.Historical ticket sales
— Past transactions import as read-only records for accounting reconciliation; ACME transaction IDs kept on each row.Gate-side scanner workflow
— TripStub's offline-first scanner works on the same phones or tablets your door staff uses today. No new hardware required.No per-ticket fee
— This is the point: $0.25–$0.35/ticket becomes $0/ticket. On 180k tickets/year that's $45k–$63k you keep.Self-serve admin (no account manager)
— ACME assigns you an account manager; TripStub is self-serve with a human answering hello@tripstub.com. Different model — some operators prefer the AM, some prefer the speed.Reciprocal-admission networks
— ACME integrates with ASTC and AZA reciprocal networks natively. TripStub's reciprocal integration is on the roadmap — if this is blocking, tell us before you migrate.Blackbaud Altru sync
— If you rely on Altru as your donor CRM with native ACME sync, TripStub's Altru integration is planned but not shipping. Migration may need a CSV-sync bridge in the interim.If you have a CSV export from ACME Ticketing, a morning coffee, and an hour of uninterrupted afternoon, you'll be taking bookings on TripStub by tomorrow morning.
Request your full data export from ACME support (typically 24–48h turnaround). In parallel, create your free TripStub workspace and start building your products.
Upload the ACME export. TripStub maps admission products, timed-entry schedules, member records (with preserved barcodes), and historical transactions. Spot-check a few member records before committing.
Reconnect your Stripe account to TripStub (5 minutes). Test the gate scanner on your existing phones/tablets. Run a parallel afternoon with both systems taking sales (TripStub → new bookings, ACME → existing member renewals).
Point your own-site checkout at TripStub. ACME stays as read-only for historical records for 30 days. Run a daily reconciliation check for the first week. Kill the ACME contract at the end of your current billing cycle.
My members have ACME-generated barcodes. Do those keep working?
Yes. We import the member's existing barcode as the external ID on the TripStub membership, and the gate scanner accepts it. Members see no change at the door.
We use ACME's integration with Blackbaud Altru. What happens to donor sync?
TripStub doesn't replace Altru — you keep Altru as your donor CRM. We can sync ticket-purchase events to Altru via REST API or nightly CSV; full native Altru sync is planned, not shipping. If Altru integration is make-or-break, email hello@tripstub.com before migrating.
Reciprocal-admission networks (ASTC, AZA) — do they work?
Not yet natively. The integrations are on the roadmap with real deadlines. If your reciprocal program is a core member benefit, the interim workflow is a manual lookup — which is the same workflow many museums used before the digital integrations. Tell us what you need to make the bridge tolerable.
What about annual renewals that are already underway?
TripStub imports the member's renewal date. On renewal day, the member gets an email from TripStub with a one-click renew link. Card-on-file isn't imported (PCI constraints); members re-enter payment at the first renewal through TripStub. After that, it's automatic.
What does the first 90 days look like financially?
Most museums save 4–6 weeks of ACME fees in the first 30 days (because your ACME billing runs out, and TripStub is $0). Beyond that, it's 100% pure savings — you've eliminated the per-ticket fee on every future ticket.