Útmutató a szerverről a felhőbe való áttelepüléshez

Támaszkodj az áttelepítés folyamatát lépésről lépésre ismertető útmutatónkra – a benne szereplő források és ajánlott eljárások garantálják a sikeres átállást a felhőbe

Choose your migration strategy and method

The method you choose will depend on your team’s unique needs for migration. Review the sections below to understand and choose the best strategy and method for your team.

Recommended

An “all at once” migration where you assess which data to migrate to cloud and which to leave behind on your server instance for future reference in a read-only state.

Take all of your data - product data, users, and apps - and migrate it to cloud in a single migration.

Migrate data in stages, rather than all at once. As you complete each migration, issues can be worked out and users onboarded and trained in small chunks.

If you’re confident you won’t be working with the majority of your existing server project data going forward, or want to work in cloud immediately, then you may choose the start fresh approach to setting up your cloud site.


Pros	Everything is migrated at once Only migrating what you need Shorter overall migration timeline and reduced migration downtime Will make cloud simpler for your teams to navigate May improve cloud performance May decrease costs to migrate (e.g. resourcing, Partner costs) due to protracted timeline
Cons	All users will need to be onboarded simultaneously May increase downtime depending on the size of your data Requires additional planning and work to determine how to optimize
Recommended when	You want to move to cloud in one migration Your migration is lower complexity (fewer than 5,000 users and 10 apps) Your critical apps are available in cloud, and have migration paths You need to migrate Jira Service Desk or Portfolio


Pros	Everything is migrated at once Shorter overall migration timeline May decrease costs to migrate (e.g. resourcing, Partner costs) due to protracted timeline
Cons	All users will need to be onboarded simultaneously May increase downtime depending on the size of your data May be moving unneeded data and users to cloud, which can increase costs
Recommended when	You need to move to cloud quickly Your migration is lower complexity (fewer than 5,000 users and 10 apps) Your critical apps are available in cloud, and have migration paths You do not need or want to clean up prior to migrating You need to migrate Jira Service Desk or Portfolio


Pros	Phased user onboarding Reduced single downtime Allows you to clean up and optimize over time Gives users a chance to adapt to new ways of doing things
Cons	Not well supported if you need to migrate Jira Service Desk or Advanced Roadmaps (formerly known as Portfolio) Longer overall migration timeline may lead to increased costs Can be more complex to manage multiple deployments during the transition Requires careful planning, since dependencies must be mapped out Can be harder to fix links after migration when only some Confluence Spaces or Jira Projects are migrated
Recommended when	You are able to move to cloud over an extended timeframe Your migration is higher complexity (more than 5,000 users and 10 apps) Some teams' critical apps are not yet available in cloud


Pros	No or limited migration downtime If you have a server license, you can keep the data around for archiving purposes
Cons	Users will not have access to old project/space data
Recommended when	You won’t be working with your existing server data You’re a Jira Service Desk customer and dont need quick access to old tickets You’re are spinning up a new team You want to expedite your move to cloud You want to streamline your cloud footprint and reinvent ways of working

Tervezés, követés és támogatás

Jira Software

Jira Align

Jira Core

Jira Service Management

Opsgenie

Állapotoldal

Együttműködés

Confluence

Trello

Kódolás, buildelés és szállítás

Bitbucket

Sourcetree

Bamboo

BIZTONSÁG ÉS SZEMÉLYAZONOSSÁG

Atlassian Access

Crowd

Marketplace

Fejlesztők

Bizalom és biztonság

Work Life blog

Csapatméret szerint

Startupok

Kisvállalkozások

Nagyvállalat

Csapatfunkció szerint

Szoftver

Marketing

HR

Jogi

Műveletek

IT

Pénzügy

Incidenskezelés

Marketplace

Fejlesztők

Bizalom és biztonság

Work Life blog

Források

Dokumentáció

Utazás a felhőbe

Felhőbeli áttelepülési központ

A felhő ütemterve

Vásárlás és licencelés

Támogatási szolgáltatások

Szolgáltatások nagyvállalatok részére

Partnerprogram

Atlassian-támogatás

Tanulás és kapcsolat

Rólunk

Karrier

Atlassian Egyetem

Atlassian Közösség

Marketplace

Fejlesztők

Bizalom és biztonság

Work Life blog

Útmutató a szerverről a felhőbe való áttelepüléshez

Choose your migration strategy and method

Server to cloud migration strategies

Choose your migration method