Migration Playbook
Migrate a venue from OpenTable, Resy, or manual booking to AGNT — extract, restructure, optimize.
Why this playbook
Venue migration is the most sensitive part of onboarding — you're replacing a working system. Downtime means lost bookings, and data loss means angry customers asking 'where's my reservation?'
This playbook extracts existing data from the current platform, restructures it into AGNT's format (reusing the same intake prompt from standard onboarding), and then configures the booking optimizer for the transition period — including dual-running with the old system during cutover.
Designed for venues switching from OpenTable, Resy, or manual booking systems. The extraction step handles each platform's export format.
Prerequisites
- Claude Code with filesystem access
- Admin access to the venue's current booking platform
- Data export from the current platform (reservation history, menu, contact info)
- AGNT venue admin panel access for the target venue
Input requirements
| Input | Type | Required | Description |
|---|---|---|---|
| Platform export | CSV, JSON, or directory | Yes | Exported data from the current booking platform: reservation history, venue details, menu, customer contacts. Format depends on the source platform. |
| Source platform | string | Yes | 'opentable', 'resy', 'sevenrooms', 'manual', or 'custom'. Determines which extraction rules apply. |
| Cutover strategy | string | No | 'immediate' (switch in one step) or 'dual-run' (run both systems for 1-2 weeks). Default: dual-run, which is safer but requires more configuration. |
Step-by-step workflow
Extract and normalize data from current platform
Open promptThis prompt reads the platform export and normalizes the data into a common format: reservation history, venue metadata, customer contacts, and booking policies. It handles platform-specific quirks (OpenTable's CSV encoding, Resy's nested JSON, SevenRooms' XML exports).
The output is a clean intermediate dataset that the next step can process. The prompt flags data quality issues: missing fields, encoding problems, duplicate reservations, and orphaned customer records.
Restructure into AGNT's venue knowledge format
Open promptThis is the same intake prompt used in standard venue onboarding, but fed with normalized data from step 1 instead of a raw website scrape. It produces the pack.json, validates all fields, and flags anything that needs human review.
The advantage of going through the standard intake process: the venue's data structure is identical to a fresh onboarding, which means all downstream tools (agent config, booking optimizer) work without modification.
Configure booking for migration transition
Open promptThe final step configures the booking optimizer with migration-specific settings: dual-run mode (if chosen), reservation history import for the agent's context window, and customer notification templates for the platform switch.
If using dual-run mode, the optimizer configures automatic sync between both systems during the transition period and sets up alerts for booking conflicts (same slot booked on both platforms).
Expected outputs
Normalized platform export
Clean, standardized dataset from the source platform: reservations, venue metadata, contacts, policies.
Produced by step 1AGNT venue knowledge pack
Standard AGNT venue format ready for agent configuration — identical to a fresh onboarding.
Produced by step 2Migration booking config
Booking optimizer config with dual-run settings, history import, conflict alerts, and customer notification templates.
Produced by step 3Tool requirements
- Claude Code with filesystem access
- Export from current booking platform (CSV, JSON, or API access)
- AGNT venue admin access
Troubleshooting
OpenTable CSV has garbled characters in venue names
Reservation history is too large (50k+ records)
Dual-run mode shows booking conflicts
Customers receive duplicate confirmation messages
Share as social post
Migration Playbook 3 steps, 60-90 minutes. Migrate a venue from OpenTable, Resy, or manual booking to AGNT — extract, restructure, optimize. https://agntdot.com/playbooks/migration-playbook
191 / 280 chars