Pivotal Tracker stopped accepting new signups in early 2024 and entered read-only mode in October 2024. Existing customers retain export-only access through 2025; after that, the data is gone.
SprintFlint is the closest sprint-native replacement we know — same stories+points+velocity model, with native retros, burndown, and capacity that Pivotal never had. The migration takes well under an hour for most projects and runs entirely off your Pivotal CSV/JSON export. No engineering effort required.
If you’d rather have someone walk through it with you, email [email protected] and we’ll set up a free 20-minute call.
Steps
-
1 Export your Pivotal project
From your Pivotal Tracker project dashboard, go to Project Settings → Export Stories. You’ll get a CSV containing every story with its title, description, point estimate, story type (feature/bug/chore/release), state, labels, and owners.
For multi-project orgs, export each project separately. SprintFlint can import multiple Pivotal projects into one workspace under different SprintFlint projects, so naming convention matters here.
-
2 Sign up for SprintFlint
Create a free account at sprintflint.com/magic-link/new. No credit card required. The first 300 tickets are free, so most Pivotal projects can run on the free tier indefinitely. We’ve onboarded several Pivotal-refugee teams and the trial gives you everything you need to validate the move.
-
3 Create the SprintFlint project
From the dashboard, New Project → name it the same as your Pivotal project. Pick a sprint length close to your Pivotal “iteration length” (Pivotal defaulted to 1 or 2 weeks). The project prefix becomes your ticket reference (e.g.
PROJ-123). -
4 Import the CSV via AI
On the empty sprint page, click Import → From text or CSV and paste your Pivotal CSV. SprintFlint’s importer reads Pivotal’s column structure natively:
- Story titles and descriptions → SprintFlint title and description
- Estimate → story points (Pivotal’s 0/1/2/3 scale maps to Fibonacci 0/1/2/3 directly; you can rescale later)
- State → SprintFlint status (see step 5)
- Story Type (feature/bug/chore) → SprintFlint labels
- Owners → assignee (matched by email)
- Labels → SprintFlint labels
-
5 Map statuses (one-time)
Pivotal states map cleanly to SprintFlint’s:
- Unstarted / Unscheduled → backlog
- Started → in_progress
- Finished / Delivered → in_review
- Accepted → done
- Rejected → in_progress (re-opened)
Releases (Pivotal’s release-marker stories) become SprintFlint sprint goals. Spikes stay as labelled stories.
-
6 Set up the team
From Settings → Team, invite by email. Pivotal user accounts don’t migrate, but most teams use the same emails so re-inviting takes minutes. Each teammate gets a magic-link sign-in (no password to set).
-
7 Activate the first SprintFlint sprint
Drag the stories you’d planned for your next Pivotal iteration into the SprintFlint sprint. Hit Activate — velocity starts tracking immediately. Burndown and capacity widgets show up by default.
Pivotal’s “auto-iteration” model (where iteration boundaries shift based on velocity) doesn’t have a SprintFlint equivalent — you commit explicitly to each sprint. Most ex-Pivotal teams report this as a feature, not a regression: predictability beats auto-magic.
-
8 Optional: keep Pivotal exports as archive
Pivotal’s read-only access ends late 2025. Before then, export your project as JSON as well as CSV (Project Settings → Export Project → JSON). Stash it somewhere durable (S3, GitHub repo, Drive). SprintFlint can import additional historical sprints later from the JSON if you ever want to backfill velocity history.