JITSU-131: migration analyzer wizard — import from Segment/RudderStack - #1427
Draft
absorbb wants to merge 1 commit into
Draft
JITSU-131: migration analyzer wizard — import from Segment/RudderStack#1427absorbb wants to merge 1 commit into
absorbb wants to merge 1 commit into
Conversation
New workspace page /import (Jitsu Cloud only, gated on appConfig.ee.available): - components/ImportWizard/ImportWizard.tsx: 4-step wizard — provider pick (Segment / RudderStack Cloud / RudderStack OSS), token entry or workspaceConfig.json upload, live analysis progress (2.5s polling of ee-api migration/report), report view. reportId/provider kept in the query string so a refresh resumes the run; token is held in component state only and cleared the moment the analysis starts - MigrationReportView: savings hero (suppressed per PRD when <= 0), verdict summary (auto-importable / small change / needs a call), destination+warehouse+source tables, gaps alert, book-a-call CTA (placeholder URL pending JITSU-128 Calendly answer) - UsageEditor: invoice upload -> ee-api LLM parse -> user confirms numbers -> report-usage applies them (raw parse never auto-applied) - top-nav 'Import' item + overview teaser card, both ee-gated Backend endpoints live in jitsu-cloud-billing PR #29 (JITSU-128). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
JITSU-131— console UI for the migration analyzer (JITSU-128).Adds a workspace page
/importwith a 4-step wizard to analyze a Segment or RudderStack workspace and show a migration report. Cloud-only: everything is gated onappConfig.ee?.available; the backend endpoints (/api/migration/*) live in jitsucom/jitsu-cloud-billing#29.What's in the box
components/ImportWizard/ImportWizard.tsx— Provider → Connect → Analysis → Report steps (antdSteps):workspaceConfig.jsonupload — no API to read);migration/reportevery 2.5 s and renders per-entity progress;reportId/providerare kept in the query string so refresh/back resumes the run.MigrationReportView— savings hero (suppressed when ≤ 0 per PRD), ✅ / 🟡 / 📞 verdict summary + destination/warehouse/source tables, partial-fetch gaps alert, book-a-call CTA (placeholder URL, TODO pending the Calendly answer onJITSU-128).UsageEditor— invoice upload → ee-api LLM parse → user reviews/edits the extracted numbers →report-usageapplies them. The raw parse is never auto-applied.components/ImportWizard/types.ts— client mirror of the ee-api migration contract (kept in sync manually; ee-api is a separate repo).Not testable end-to-end yet
Blocked on the billing side:
migration_reportstable (pnpm db:update-schema) and deploy of jitsucom/jitsu-cloud-billing#29. The UI degrades cleanly meanwhile (analysis start surfaces the API error).🤖 Generated with Claude Code