Highline Adventures Migration Plan — Summit Guardian
Document 2 of 3 · Plan

Migration Plan

Moving highlineadventures.com onto the Summit Guardian platform — same Highline brand and voice, new engine underneath. Companion to the Site Audit (Document 1).

01  Goals & principles

02  Target architecture

Summit Guardian (Python) serves both halves: the public site and the operations backend.

Summit Guardian module Replaces What it must do
Content & pagesJoomla + YOOthemeStructured product + page content (not builder layouts); templates for the five page types; per-page meta (fixes AUD-11)
Products & pricingPeek product catalog10 products seeded from Audit §04; price shown on site is read live from here
Availability & schedulingPeek calendarTour slots, capacity (settle AUD-04 first), seasonal Thu–Sun vs 7-day schedules, weather holds
Checkout & paymentsbook.peek.comOn-site checkout; promo codes; group quotes (>8) routed to reservations; punch passes and e-gift cards as tender
WaiversPeek email linkE-sign at booking or from reminder; minor co-sign by guardian; status visible at Basecamp check-in
NotificationsPeek emailConfirmation, waiver reminder, arrive-15-min-early reminder, weather cancellation → refund/rain-check per policy
Guest records— (new)Owned booking history, punch-pass balances, photo delivery (replaces USB sales), review prompts

03  Target IA & redirect map

The IA keeps the current mental model — Adventures / Events / Gift Cards / Plan Your Visit — and collapses every duplicate route into one canonical URL.

Canonical (new) 301s from (old)
/
/adventures/zipline/zipline
/adventures/adventure-park/adventure-park
/adventures/skynet-playground/skynet-playground
/adventures/protea-walking-tours/protea-walking-tours
/events/group-adventure/zipline-group-tours · /group-tours-and-adventures
/events/team-adventure/team-building
/events/school-adventure/school-field-trip-adventures
/events/corporate/corporate-events
/events/wedding-celebrations/wedding-celebrations
/events/birthday-celebrations/skynet-birthday-party-package
/book (native checkout, per-product params)all book.peek.com deep-links (8 slugs, Audit §06)
/plan-your-visit (FAQ + eligibility + policies hub)/faq · /eligibility-requirements-recommendations · /reservation-policy (content merged, anchors preserved)
unchanged: /e-gifts · /sales · /news · /directions · /cancellation-policy · /privacy-policy · /accessibility · /donations · /mobile-terms-of-servicesame paths, new platform
removed from public nav/site-map?view=xml (kept for crawlers at /sitemap.xml) · /login (admin-only URL)

04  Phased rollout

Phase Work Exit criteria
0 · Settle the record ~2 wks Sign off the audit. Operations decides the contested facts: zipline capacity (AUD-04), ground-school length (AUD-05), phone/photo policy (AUD-06), canonical prices (AUD-07). Export Peek data: products, future bookings, gift-card and punch-pass balances, customer list. One-page "facts sheet" approved; Peek export verified.
1 · Build on Summit Guardian ~4 wks Seed product catalog from Audit §04. Enter content into structured templates, fixing AUD-03/08/09/10/13 as it's entered. Build the five page templates from the redesigned prototype (Document 3). Stage redirects. Site reads prices/availability from Summit Guardian, but BOOK NOW still deep-links to Peek. New site live on new platform; zero booking change; redirects verified; Lighthouse + SEO parity checks pass.
2 · Booking cutover ~3 wks · off-peak, midweek Summit Guardian checkout passes parity tests (each product, promo codes, group quote path, waiver e-sign, notification emails). Flip BOOK NOW to /book. Peek stops new sales but stays read-only for existing reservations until the last Peek-booked tour date passes. Honor gift cards and punch passes from imported balances. First full week of native bookings with no support escalations; refund + reschedule flows exercised for real.
3 · Own the guest ongoing Digital photo delivery replaces USB sales. Post-tour review prompts. Weather-hold notifications. Decommission Joomla and close the Peek account once its last booking is served. Joomla + Peek off; all guest data in Summit Guardian.

05  Cutover checklist

06  Risks & mitigations

Risk What could go wrong Mitigation
R1SEO dip after replatform1:1 301 map, unchanged canonical paths where possible, per-page meta upgrade, sitemap resubmission, rank monitoring for 90 days
R2Double-booking across two systems during cutoverHard switch: Peek sales stop the moment /book opens; imported Peek reservations block Summit Guardian slots
R3Gift-card / punch-pass liability lost in transferBalance export reconciled against Peek statements before Peek closes; codes honored verbatim
R4Waiver enforceability on the new e-sign flowCounsel reviews text + signature capture before Phase 2; paper fallback stays at Basecamp
R5Cutover collides with peak season (7-day summer schedule)Schedule Phase 2 for the Thu–Sun off-peak calendar; freeze changes around holiday weekends
R6Prices drift again across site / OTAs / printSite renders prices from Summit Guardian only; third-party channels reviewed quarterly against the catalog

07  Decisions needed from Highline

Prepared July 4, 2026 Internal — Summit Guardian migration