Skip to main content

Developer Portal Service — Migration Plan

Version: 1.0 Status: Draft Owner: Product + Developer Relations (DevRel) Last Updated: 2026-04-20

1. Intent​

Plan how existing pilot developers, beta tenants, and any prior SDK consumers migrate onto the Developer Portal v1.0. The portal is greenfield; migration centres on importing pre-existing API keys, redirecting old docs URLs, and onboarding pilot tenants gradually.

2. Scope​

  • Pilot developers (≤ 30 individuals) using pre-portal API keys provisioned manually. TBD
  • Pre-portal markdown docs hosted on a Confluence space. TBD
  • Internal SDKs (Node, Python prototypes) shipped to pilot tenants. TBD

3. Phases​

Phase 1 — Shadow launch (week 1–2)​

  • Deploy portal with feature flags hiding production-key UI.
  • Migrate pilot developers' Confluence docs URLs to portal /legacy/... redirects.
  • TBD

Phase 2 — Pilot enrolment (week 3–4)​

  • Invite pilot developers to portal; have them claim sandbox keys.
  • Issue production keys via owner-approval flow.
  • Disable manual key-issuance path. TBD

Phase 3 — Public open (week 5+)​

  • Open portal sign-up to all tenants.
  • Publish all SDKs to public registries (npm, PyPI, etc.).
  • Sunset Confluence docs (redirect 301 to portal). TBD

4. Cut-over Checklist​

  • Pilot developers notified 14 days in advance
  • Old API keys remain valid for 90 days post cut-over
  • Confluence space frozen and 301-redirected
  • DevRel office hours scheduled for first 2 weeks of public open

5. Rollback​

  • TBD

6. Success Metrics​

  • ≥ 90% of pilot developers self-issue keys via portal within 14 days. TBD
  • 100% of new tenants onboard via portal (no manual provisioning). TBD
  • Zero P0 incidents during cut-over. TBD