Importing data from BaseCamp
Migrating from other issue trackers
- Importing data from CSV
- Importing data from Excel
- Importing data from Bitbucket
- Importing data from Github
- Importing Data from Asana
- Importing data from TFS or Visual Studio
- Importing data from Rally
- Importing data from VersionOne
- Importing data from YouTrack
- Importing data from Axosoft
- Importing data from Pivotal Tracker
- Importing data from Bugzilla
- Importing data from FogBugz On Demand
- Importing data from FogBugz for your Server
- Importing data from Trac
- Importing data from Redmine
- Importing data from BaseCamp
- Importing data from JSON
- Importing data from Mantis
On this page
Related content
- How to define a default merge strategy per Project
- Merge a pull request
- Remote merge is not happening in Bitbucket Server
- Bitbucket Server/Data Center shows diff between branches even after they are merged (using squash commit)
- Commits missing from Pull Request merge on target branch
- Automatic branch merging
- Understanding Diff view in Bitbucket Server
- Pull Request is automatically marked merged in Bitbucket Data Center and some of the code changes are lost on target branch after performing conflict resolution in a different branch
- Merging a pull request with 'rebase and fast-forward' strategy fails with merge conflict in Bitbucket Server
- Using forks in Bitbucket Server
Unfortunately, it's not possible to export the data from Basecamp into a file format which can be directly imported back to Jira.
There are third party solutions available which might help you. Please check out the TaskAdapter solution from Atlassian Marketplace. You can also contact your local Atlassian Expert for help or develop a solution based on Basecamp and Jira public APIs.
Last modified on Jul 11, 2019
Related content
- How to define a default merge strategy per Project
- Merge a pull request
- Remote merge is not happening in Bitbucket Server
- Bitbucket Server/Data Center shows diff between branches even after they are merged (using squash commit)
- Commits missing from Pull Request merge on target branch
- Automatic branch merging
- Understanding Diff view in Bitbucket Server
- Pull Request is automatically marked merged in Bitbucket Data Center and some of the code changes are lost on target branch after performing conflict resolution in a different branch
- Merging a pull request with 'rebase and fast-forward' strategy fails with merge conflict in Bitbucket Server
- Using forks in Bitbucket Server
Powered by Confluence and Scroll Viewport.