Export what you have.
Bookings, items and customers from your current tool, as a CSV or spreadsheet.
Your old toolGoGo Engine gives you one calendar across every location, deposit holds released on a clean return, a public API with signed webhooks, and a customer portal under your business name.
| Feature | GoGo Engine | Booqable |
|---|---|---|
| Inventory across locations | Yes | Paid add-on per location |
| Deposit hold + release on return | Yes | Card hold, released by staff |
| Customer portal | Under your business name | Customer accounts |
| Public REST API + webhooks | Every webhook signed | API in beta; v4 webhooks signed, v1 not |
| Pricing rules | Length tiers, seasonal rates, promo codes | Seasonal, weekend, non-billable days |
| Built-in customer SMS | Yes | Through Zapier |
| Accounting sync | Not available | Xero; QuickBooks through Zapier |
There is no self-serve import tool today, so setup happens in the dashboard. The playbook covers what to export and what to check.
Bookings, items and customers from your current tool, as a CSV or spreadsheet.
Your old toolLocations, items, rates and rules are created in the dashboard, with templates and duplicates. There is no self-serve import today.
The dashboardCompare totals, tax and deposits on real bookings against your old tool before you go live.
Before go-livePoint your site’s booking links at GoGo Engine and turn on your customer portal.
LiveThe playbook: what to export from your current tool, how setup works today, and what to check before you go live.