Skip to content

feat(admin): Add legacy Seer migration action to customer admin#114126

Merged
swartzrock merged 6 commits intomasterfrom
swartzrock/admin-migrate-legacy-seer
Apr 28, 2026
Merged

feat(admin): Add legacy Seer migration action to customer admin#114126
swartzrock merged 6 commits intomasterfrom
swartzrock/admin-migrate-legacy-seer

Conversation

@swartzrock
Copy link
Copy Markdown
Member

@swartzrock swartzrock commented Apr 28, 2026

Adds a "Migrate From Legacy Seer" admin action to the customer details page that posts to the CustomerMigrateLegacySeerAdminEndpoint. The action allows admins to move an organization off legacy Seer reserved budgets and onto the seat-based Seer plan.

The action is gated to AM1/AM2/AM3 plan tiers and exposes two timing options (apply immediately or at next billing period) plus an optional 14-day Seer seat trial. After migration, users opt in to Seer from their organization settings.

Screenshots

Customer Action Menu

image

Customer Action Menu for non-Legacy Seer customer

image

Customer Action Dialog

image

Adds a "Migrate From Legacy Seer" admin action to the customer details page that posts to the CustomerMigrateLegacySeerAdminEndpoint. The action allows admins to move an organization off legacy Seer reserved budgets and onto the seat-based Seer plan.

The action is gated to AM1/AM2/AM3 plan tiers and exposes two timing options (apply immediately or at next billing period) plus an optional 14-day Seer seat trial. After migration, users opt in to Seer from their organization settings.
@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Apr 28, 2026
@swartzrock swartzrock marked this pull request as ready for review April 28, 2026 15:50
Comment thread static/gsAdmin/views/customerDetails.tsx
Comment thread static/gsAdmin/components/migrateLegacySeerAction.tsx
Copy link
Copy Markdown
Contributor

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 2 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 3cc072f. Configure here.

Comment thread static/gsAdmin/components/migrateLegacySeerAction.tsx
Comment thread static/gsAdmin/components/migrateLegacySeerAction.tsx
@swartzrock swartzrock enabled auto-merge (squash) April 28, 2026 21:08
@swartzrock swartzrock merged commit f5eeff6 into master Apr 28, 2026
65 checks passed
@swartzrock swartzrock deleted the swartzrock/admin-migrate-legacy-seer branch April 28, 2026 21:47
cleptric pushed a commit that referenced this pull request May 5, 2026
)

Adds a "Migrate From Legacy Seer" admin action to the customer details
page that posts to the CustomerMigrateLegacySeerAdminEndpoint. The
action allows admins to move an organization off legacy Seer reserved
budgets and onto the seat-based Seer plan.

The action is gated to AM1/AM2/AM3 plan tiers and exposes two timing
options (apply immediately or at next billing period) plus an optional
14-day Seer seat trial. After migration, users opt in to Seer from their
organization settings.

## Screenshots

### Customer Action Menu
<img width="325" height="154" alt="image"
src="https://github.com/user-attachments/assets/74f0cefd-bf7b-4f8d-9321-4060d274cae6"
/>

### Customer Action Menu for non-Legacy Seer customer
<img width="347" height="229" alt="image"
src="https://github.com/user-attachments/assets/29a28db1-8feb-45f9-8c74-47baa2db9254"
/>


### Customer Action Dialog
<img width="623" height="680" alt="image"
src="https://github.com/user-attachments/assets/e7644119-4ce4-4ac2-ba33-f45107499bb0"
/>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants