Migrate venue bookings from OpenTable to AGNT
Step-by-step migration playbook for venues moving from OpenTable to AGNT.
Venues switching from OpenTable to AGNT need a clean migration path: export existing reservations, map guest data to AGNT's format, configure the new booking flow, and run parallel operations until the cutover date. This prompt handles the full migration playbook.
The prompt is designed for an operator running Claude Code with filesystem access. It produces a migration plan, a data mapping spreadsheet, a parallel-run checklist, and a cutover day script. The key constraint: no guest data is lost, no double-bookings during the transition period, and the venue's Google Business Profile booking link is updated on cutover day.
The prompt
<<< You are migrating a venue from OpenTable to AGNT booking. Follow this playbook: PHASE 1 — EXPORT (Day 1): 1. Export all future reservations from OpenTable as CSV. 2. Export guest list with names, emails, phone numbers, visit count. 3. Map fields: OT guest_id → AGNT guest record, OT reservation → AGNT booking. PHASE 2 — PARALLEL RUN (Days 2-7): 1. Set up AGNT venue agent (Sam) with full knowledge pack. 2. Keep OpenTable active for existing reservations. 3. New bookings go through AGNT only — update website/Google booking link. 4. Daily reconciliation: compare OT and AGNT booking counts. PHASE 3 — CUTOVER (Day 8): 1. Cancel OpenTable subscription (ensure no future bookings remain). 2. Import remaining OT guest data into AGNT. 3. Update Google Business Profile booking URL to AGNT. 4. Send WhatsApp broadcast to past guests with new booking link. 5. Monitor for 48 hours — check for missed bookings or confused guests. OUTPUT: migration-plan.md, data-mapping.csv, cutover-checklist.md >>>
When to use
Use this when a venue is switching from OpenTable (or any legacy booking platform) to AGNT. The parallel-run phase prevents the most common migration failure: lost bookings during cutover.
Works with
Related guides
Onboard your venue with AGNT in 30 minutes
From sign-up to a live venue agent answering guests on WhatsApp — the full operator walkthrough.
Debug booking failures — common issues and fixes
Diagnose why a booking did not go through and fix it in minutes using the AGNT venue admin tools.
How to use Claude Code with AGNT
Install Claude Code, register AGNT as an MCP server, and start calling real venue tools from inside your terminal.
Share as social post
Migrate venue bookings from OpenTable to AGNT (claude-code) — Step-by-step migration playbook for venues moving from OpenTable to AGNT. https://agntdot.com/prompts/migrate-from-opentable
187 / 280 chars
Related prompts
Venue intake prompt pack for Claude Code
Parse a venue's website + menu into AGNT's knowledge pack format.
Codex fleet-swap operator prompt
Walk an operator through swapping an AGNT agent from claude_local to codex_local.
Agent hiring brief — reusable template
The CEO/CTO prompt for spawning a new sub-agent via Paperclip with clear acceptance criteria.