Migration guide
Add FlowSprite to your Gearset workflow in 10 minutes
Most Gearset teams keep their existing Git repo and just point FlowSprite at it. Closer to "add a tool" than "replace a stack."
You don't have to migrate. Add FlowSprite to the same repo Gearset is already watching, and let your team pick which tool fits which work.
The 10-minute setup
01
Connect FlowSprite to your existing repo
GitHub, GitLab, or Bitbucket — same OAuth flow Gearset uses. No new repo, no rebaseline.
02
Connect a sandbox
Same sandbox set already wired into Gearset. FlowSprite reads metadata via standard sfdx; no conflict.
03
Try one change
Ask FlowSprite to add a test field. Review the PR. Deploy to sandbox. Compare to your Gearset workflow.
04
Decide your split
AI-drafted admin changes through FlowSprite. Engineer-driven release management stays in Gearset. Or full cutover. Your call.