Switching shouldn't mean starting over.
Repolaris imports your repositories, issues, and workflows—preserving your history and your momentum. We make migration as painless as possible.
Migration paths
From GitHub
Repositories
- • Full Git history with all branches and tags
- • LFS objects
- • Releases and assets
- • Commit signatures preserved
Issues & PRs
- • Complete issue history
- • All comments and reactions
- • Pull request discussions
- • Labels and milestones
Actions
- • GitHub Actions workflow compatibility
- • Minimal syntax changes required
- • Common actions supported
Teams & Permissions
- • Organization structure
- • Team mappings
- • Permission levels
From GitLab
Repositories
- • Full Git history
- • All branches and tags
- • LFS objects
- • Project variables → Secrets
Merge Requests
- • MR history with discussions
- • Approval states
- • Draft MRs
Issues
- • Complete issue history
- • Weight → Estimates
- • Labels and milestones
- • Issue relations
CI & Groups
- • .gitlab-ci.yml → workflow translation
- • Variable mapping
- • Group → Organization mapping
- • Subgroups → Teams
From Bitbucket
Repositories
- • Git repositories with full history
- • Mercurial → Git conversion available
- • Branches and tags
- • LFS objects
Pull Requests
- • PR history and comments
- • Approval states
- • Merge commits
Issues
- • Issue migration
- • Comment history
- • Assignees and watchers
From Jira
Issues
- • Full issue history
- • All comments and attachments
- • Custom fields
- • Subtasks → Sub-issues
Workflows
- • Status mapping to Repolaris workflows
- • Transition rules where applicable
Boards
- • Kanban board configuration
- • Column mapping
- • Filters → Views
Sprints
- • Sprint → Cycle mapping
- • Active sprint migration
- • Historical sprint data
From Azure DevOps
Repositories
- • Git repositories with full history
- • Branch policies reference
- • TFVC conversion available
Work Items
- • Work item → Issue migration
- • All fields and history
- • Area paths → Teams
- • Iteration paths → Cycles
Boards
- • Board configuration
- • Column rules
Migration process
Assessment
- • Review repository count and sizes
- • Assess issue and PR volumes
- • Map team structure
- • Identify integration dependencies
Preparation
- • Create your Repolaris organization and teams
- • Invite team members and set up SSO
- • Configure any external integrations
Import
- • Import repositories using migration tools
- • Import issues and project data
- • Verify data came through correctly
Parallel Period
- • Operate both platforms during transition
- • Point CI/CD to Repolaris gradually
- • Train users on the new platform
Cutover
- • Import any changes since initial migration
- • Redirect links and documentation
- • Archive or delete old platform data
Migration tools
Web Import
Simple projects
- Import directly from web UI
- Connect to source platform
- Select what to import
- Watch progress
CLI Import
Large migrations
- Script and automate imports
- Bulk operations
- Progress tracking
- Retry on failure
repolaris import github \
--org my-org \
--repos all \
--issues \
--prs \
--actionsAPI
Custom migrations
- Full API access for custom tooling
- Bulk operations
- Programmatic verification
Enterprise Migration Services
For Enterprise customers, we offer assisted migration.
Planning consultation
Architecture review, migration strategy, risk assessment
Implementation support
Dedicated migration engineer, custom scripting, data verification
Parallel operation
Sync tooling, dual-write strategies, gradual cutover
Training
Admin training, user onboarding, workflow adaptation
What gets migrated
| Source | Repos | Issues | PRs/MRs | CI | Teams |
|---|---|---|---|---|---|
| GitHub | Partial* | ||||
| GitLab | Partial* | ||||
| Bitbucket | — | ||||
| Jira | — | — | — | — | |
| Azure DevOps | — |
*CI configuration requires workflow file updates
What doesn't migrate
Technical Limitations
- • Webhooks (must be reconfigured)
- • API tokens (new tokens required)
- • OAuth apps (re-registration needed)
Not Applicable
- • GitHub Apps (different app model)
- • Marketplace apps (may not have equivalents)
Manual Steps
- • Branch protection (reconfigure rules)
- • CODEOWNERS (review and update paths)
- • Repository settings (review and configure)
FAQ
How long does migration take?
Depends on size: Small project (<1000 issues) in minutes, Medium org (50 repos, 10K issues) in hours, Large enterprise (500+ repos) in days with parallel running.
Is there downtime?
No downtime for existing platform. Repolaris imports are additive.
Can I migrate incrementally?
Yes. Import repositories first, then issues, then configure CI.
What if something goes wrong?
Imports can be re-run. Your source platform is unchanged.
Can I keep both platforms running?
Yes, for as long as you need during transition.