![\"Data](\"https:\/\/gitprotect.io\/blog\/wp-content\/uploads\/2024\/07\/Data-Migration-Use-Case-1024x576.jpg\")
<\/a><\/figure><\/div>\n\n\nBackup and restore needs <\/h3>\n\n\n\n
To meet the Shared Responsibility Model<\/a> and compliance requirements, you need to have backup. Import and export of Bitbucket data can partly cover this needs. As, it allows you to have a copy of your Bitbucket repository on your local disk, for example. So, when there is a need you can import your repository back to your Bitbucket.<\/p>\n\n\n\n For your organizational or compliance needs you may need to keep your data for long periods of time. Exporting repositories from Bitbucket to your local instance can meet this pain. Moreover, export of completed or inactive projects for long-term storage can help you free up space in the active Bitbucket environment.<\/p>\n\n\n\n If you need to work and cooperate with teams that work with other version control systems, like GitHub or GitLab, you may need to import and export your data from time to time. In this case, if somebody works in GitHub and you need to push some code to the same project. you can import the GitHub repository to your Bitbucket project, and do your job.<\/p>\n\n\n\n To meet strict compliance requirements, like SOC 2<\/a>, ISO 27001<\/a> or NIS 2<\/a> (a new regulation that comes into force in October 2024), you need to guarantee that your data is secure, available and accessible. Exporting data from your Bitbucket, you get a copy of your repository that is necessary for audits and historical record-keeping.<\/p>\n\n\n\n By importing Bitbucket data, you can use it to test environments to simulate real-world scenarios, debug issues, or develop new features without impacting production data.<\/p>\n\n\n\n Also, you may need export and import capability for data analysis and reporting, Continuous Integration and Delivery, data consolidation, integration with other tools, preserving project history, and these reasons we can enlist more and more. Though, the most important here is how to export and import securely, fast, and without any data loss?<\/p>\n\n\n\n Before you start to export and import your data, it\u2019s worth assessing all the risks. You\u2019d better take some precautionary measures to be sure that nothing threatens your workflow, and during the exporting or importing process no data is lost. <\/p>\n\n\n\n So, let\u2019s take a look at the so-called \u201crequirements\u201d before starting your export and import in Bitbucket:<\/p>\n\n\n\n Before we jump at describing how to import your data into Bitbucket, we need to mention some capabilities of the Bitbucket import feature<\/u><\/a>. You can use Bitbucket importer only if you store your code in GitHub, CodePlex, Google Code, Subversion, SourceForge, or another Git-based hosting platform. If you have another alternative to host your source code or you don\u2019t know the URL of the repository you want to export into Bitbucket, you will need to convert your code to Git. You can read more about it in the Atlassian Documentation<\/u><\/a>. <\/p>\n\n\n\n 4. Don\u2019t forget about \u201cAdvanced settings\u201d which you can access by expanding the button Advanced settings<\/em> on your screen. Here you will be asked to provide description for the data you want to import (1), you can manage forking permissions (2), and you can choose a programming language for the repository you are importing (3). Though it\u2019s not obligatory to add that information, it\u2019s better to specify them.<\/p>\n\n\n\n 5. Finally, when you click \u201cImport repository\u201d, you initiate the import of data. And when the process of importing is over, you will be notified if the migration process was successful or not. In our case, the importing of data from GitHub to GitLab was successful. <\/p>\n\n\n If you need to import a few repositories, you need to perform the above-mentioned steps a few times for each of your private repositories in your existing project on GitLab or GitHub. After that, you can check for the imported repositories in your existing project on Bitbucket.<\/p>\n\n\n\n If you need to have a ZIP file of your Bitbucket repository on your local machine, you can manually download it. After you have your Bitbucket file on your local instance, you can keep it as a backup or upload it to another git hosting platform, for example, migrate that existing Bitbucket repo to GitHub or Gitlab<\/u><\/a>. <\/p>\n\n\n\n Well, to export your Bitbucket data, you need to simply go to the git repository you want to export. Then, in the right corner expand \u201cMore\u201d and select \u201cDownload repository\u201d.<\/p>\n\n\n After that, you just need to figure out where you want to keep the downloaded file on your local machine. <\/p>\n\n\n That\u2019s it! Now, the most important is to remember where you keep your exported repository from Bitbucket Cloud.<\/p>\n\n\n\n In case you use Bitbucket Data Center, you can opt for the REST API architecture that Atlassian provides. Thus, you will be able to export your data to other platforms or to Bitbucket Cloud. Moreover, it can help you create your automated system. <\/p>\n\n\n\n Before you start an export job, you should remember that you can have only 2 concurrent exports per cluster node. Otherwise, the export will be rejected with an error. Moreover, you should confirm the URL of the repo or project you are about to export to be able to execute Bitbucket exports from your local instance. Usually this URL looks the following way:<\/p>\n\n\n\n https:\/\/bitbucket.com\/projects\/[name-of-the-project]\/repos\/[the-repository]<\/a><\/p>\n\n\n\n Here [name-of-the-project] means your project key, and [the-repository] represents your repository slug. Check Atlassian API documentation<\/u><\/a> for the detailed explanation of the process and examples of the requests in different languages, including curl, Node.js, Java, Python, and PHP. <\/p>\n\n\n\n As for the Bitbucket Data Center importing, you should copy the import file you need to your target instance by copying into:<\/p>\n\n\n\n $BITBUCKET_HOME\/shared\/data\/migration\/import<\/p>\n\n\n\n Then, you should state the path relative to the import directory in the REST call. That’s important as if you file won\u2019t be copied to this directory, your import job won\u2019t work. For reference, we leave here a link to Atlassian\u2019s documentation for importing Bitbucket data<\/u><\/a>, as all the process is well documented there.<\/p>\n\n\n\n Of course, if you search for other ways to migrate data into Bitbucket or from Bitbucket, you can find other options, for example Git Clone and Mirror commands. Though, they are useful for migrating data from one repo to another, e.g. from Bitbucket Cloud to Bitbucket Cloud, you still need to be very attentive not to miss some critical data during the cloning or mirroring process. <\/p>\n\n\n\n For example, you can use the git clone<\/em> command to create a clone of your repository<\/u><\/a>:<\/p>\n\n\n\n git clone <repo_address> <directory> \u2013no-tags \u2013filter = blob: none<\/p>\n\n\n\n This approach will allow you to copy a project from a given address to the needed remote or local directory.<\/p>\n\n\n\n In this case, you will need to do a git pull of your current master branch in local. For that, you can use:<\/p>\n\n\n\n git push – mirror destination-repository-url<\/p>\n\n\n\n This command will help you transfer all your branches, commit history, and tags to the new git repository. <\/p>\n\n\n\n Whether you need to do Bitbucket imports and exports for migration or backup needs, you can try a professional backup tool – GitProtect.io backup and Disaster Recovery software for Bitbucke<\/a>t. With GitProtect.io you will not only have a reliable copy of your Bitbucket data (in a few storage destinations!), but also meet the Shared Responsibility and compliance needs. Once you set up your GitProtect.io account and link your Bitbucket, GitHub, or\/and GitLab environment to it you will be able to schedule an automated backup of your DevOps ecosystem, following the backup best practices for Bitbucket data protection<\/u><\/a>.\u00a0<\/p>\n\n\n\n Then, you can restore your data to the same or new Bitbucket account or use the cross-over recovery option with minimal effort – you can restore your data to another git hosting service, e.g GitLab or GitHub.<\/p>\n\n\n\n \u270d\ufe0f Subscribe to our DevOps X-Ray Newsletter<\/u><\/a> to always stay up to date with the latest news in DevOps and DevSecOps. As one of the leading platforms for distributed version control, Bitbucket is a hub that helps DevOps teams collaborate on code. This critical data, including source code, digital data, and we shouldn\u2019t forget metadata that helps them to see the full picture of their work, is vital for their operations and business continuity. So, should they have the possibility to seamlessly import this data from Bitbucket and export to Bitbucket? The answer is yes. <\/p>\n","protected":false},"author":8,"featured_media":5404,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-5393","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-bitbucket","post--single"],"yoast_head":"\nArchiving purposes<\/h3>\n\n\n\n
Collaboration across teams<\/h3>\n\n\n\n
Compliance and auditing<\/h3>\n\n\n\n
Testing and development<\/h3>\n\n\n\n
Bitbucket export and import tips & tricks – Bitbucket migration checklist<\/h2>\n\n\n\n
\n
How to import data into Bitbucket – Step-by-step guide<\/h2>\n\n\n\n
Steps to import your data into Bitbucket<\/h3>\n\n\n\n
\n
![\"Bitbucket](\"https:\/\/gitprotect.io\/blog\/wp-content\/uploads\/2024\/07\/Bitbucket-imports-and-exports-1-1024x299.png\")
<\/figure><\/div>\n\n\n\n
![\"Bitbucket](\"https:\/\/gitprotect.io\/blog\/wp-content\/uploads\/2024\/07\/Bitbucket-imports-and-exports-2-1.png\")
<\/figure><\/div>\n\n\n\n
![\"Bitbucket](\"https:\/\/gitprotect.io\/blog\/wp-content\/uploads\/2024\/07\/Bitbucket-imports-and-exports-3.png\")
<\/figure><\/div>\n\n\n\n
![\"Bitbucket](\"https:\/\/gitprotect.io\/blog\/wp-content\/uploads\/2024\/07\/Bitbucket-imports-and-exports-4.png\")
<\/figure><\/div>\n\n\n![\"Bitbucket](\"https:\/\/gitprotect.io\/blog\/wp-content\/uploads\/2024\/07\/Bitbucket-imports-and-exports-5.png\")
<\/figure><\/div>\n\n\n\n
How to export to Bitbucket – Step-by-step explanation<\/h2>\n\n\n\n
![\"Bitbucket](\"https:\/\/gitprotect.io\/blog\/wp-content\/uploads\/2024\/07\/Bitbucket-imports-and-exports-6-1024x307.png\")
<\/figure><\/div>\n\n\n![\"\"](\"https:\/\/gitprotect.io\/blog\/wp-content\/uploads\/2024\/07\/Bitbucket-imports-and-exports-7-3.png\")
<\/figure><\/div>\n\n\nA few words about Bitbucket export and import using REST API architecture<\/h3>\n\n\n\n
How-to export data using API<\/h4>\n\n\n\n
How-to import data using API<\/h4>\n\n\n\n
Are there any other ways to migrate data to Bitbucket?<\/h2>\n\n\n\n
Git commands approach<\/h3>\n\n\n\n
\n
\n
GitProtect.io as a secure way to backup and migrate your Bitbucket Cloud data<\/h3>\n\n\n\n
Before you go:<\/h2>\n\n\n\n
\ud83d\udd0e Find out what security incidents Atlassian faced in 2023<\/u><\/a> and what were the causes of those threats.
\ud83d\udcda<\/u><\/a> Learn how to build your Disaster Recovery strategy<\/u><\/a> to meet any disaster scenario and build an uninterrupted workflow for your DevOps team.
\ud83d\udccc Try <\/u><\/a>GitProtect.io<\/u><\/a> backup and Disaster Recovery software for Bitbucket<\/u><\/a> to have peace of mind that your data is safe during the migration process and any other event of failure.
\ud83d\udcc5 Schedule a live demo to talk about Bitbucket backup<\/u><\/a> and best practices to protect your DevOps ecosystem.<\/p>\n","protected":false},"excerpt":{"rendered":"