Professional Documents
Culture Documents
IT departments at many companies today are maintaining systems that were developed over the
past 40 years. Initially, these systems were based on monolithic architectures using languages such as
Assembler, COBOL, and C, and a central server was responsible for all data processing activities.
Users and clients accessed these servers via unintelligent terminals (a.k.a. dumb terminals). Many of
these systems exploited the latest technologies available at the time, but were not able to evolve as
technology evolved. Some of these applications are still around today and are accessed via terminal
emulators. With the advent of desktop computers, client/server computing took off in a big way in
the late 1980s and early 1990s. Client/server computing helped to offload some data processing
activities from central servers to client desktops. The downside of client/server computing was that
IT departments had to manage hundreds, and sometimes thousands, of desktop computers to
periodically update
the applications that clients developed in languages such as Cþþ, PowerBuilder, Visual Basic, and
Delphi. These client/server applications were attractive to users because of the rich
graphical user interfaces (GUIs) they provided instead of traditional “green screens.” In the late
1990s, the next revolution in computing occurred, and it enabled users to access data and
information using Internet browsers on personal computers, smartphones, and other digital devices.
No other software was required on these devices to access applications over the Internet. Internet
computing also heralded an era of openness and the proliferation of standards allowing seamless
access to data and information over the Internet (e.g., SOAP/XML), resulting in development of
service-oriented architecture (SOA) standards. Eventually, SOA became overhyped to the point that
every software vendor started to claim support for SOA standards in some shape or form, even if
their products had nothing to do with SOA.
aplikacije tih klijenata razvijenih u jezicima kao što su Cþþ, PowerBuilder, Visual Basic, i
Delphi. Ove klijent/server aplikacije bile su privlačne korisnicima zbog bogatog grafičkog
korisničkog sučelja (GUI) koje su umjesto tradicionalnih "zelenih ekrana." U kasnim 1990-
im, dogodila se sljedeća revolucija u računarstvu, a to je omogućilo korisnicima da pristupe
podacimai informacijama pomoću Internet preglednika na personalnim računarima, pametnim
telefonima i drugim digitalnim uređajima. Nijedan drugi softver nije bio potreban na tim
uređajima za pristup aplikacijama putem Interneta. Internet computing također nagovijestio je
eru otvorenosti i proliferaciju standarda omogućujući jednostavan pristup podacima i
informacijama preko Interneta (npr. SOAP/XML), što je rezultiralo u razvoju standarda
servis-orijentisane arhitekture (SOA). Na kraju, SOA je postao raširen do te mjere da je svaki
proizvođač softvera počeo da traži podršku za SOA standarde u nekom obliku ili formi, čak i
ako njihovi proizvodi nemaju nikakve veze sa SOA.
Povećano usvajanje klijent/server i internet computing arhitekture je rezultiralo u širenju velikog broj
servera u data centrima. Upotreba pakovanog Migriranja na Cloud. DOI: 10.1016/B978-1-59749-647-
6.00001-6 1 poslovne aplikacije kao što su upravljanje odnosa sa kupcima (CRM) i Enterprise
Resource Planning (ERP) također je doprinijelo povećanju korištenja sistema smještenih unutar data
centara za obradu podataka, sa svakim aplikacijskim okruženjem zavisno o jedinstvenoj konfiguraciji
servera, skladištenja i softvera. Vremenom, IT odjeli i organizacije počeli su stvarati ogromne
troškove u smislu kapitalnih i operativnih troškova za održavanje ovih IT sistema i infrastrukture. Oni
su morali predvidjeti budući rast potražnje za IT resursima, i oni su morali planirati i kako da steknu
potreban hardver i softver i konfigurišu ih odgovarajuće. Slično tome, svakih nekoliko godina morali
su da planiraju za hardver i softver nadogradnje kako bi inkorporirali nove tehnologije u njihove
infrastrukture.
Even in difficult economic climates in which companies were forced to cut costs, IT departments
received increasing pressure to trim their budgets and increase their utilization of these expensive
resources. To address these concerns and challenges, in the early 2000s the concept of grid
computing began to take shape. With grid computing, groups of inexpensive networked servers
functioned as one large server. This meant IT departments no longer had to acquire large and
Čak i u teškim ekonomskim uslovima firme su bili prisiljene da smanje troškove, IT odjeli su dobili
veći pritisak da smanji svoje budžete i povećaju njihovu korištenje ovih skupih resursa. Za rješavanje
tih problema i izazova, u ranim 2000-im koncept grid computing počeo je da se oblikuje. Uz grid
computing, grupe jeftino umreženih servera funkcionisale su kao jedan veliki server. Ovo je značilo da
IT odjeli više nisu morali da stiču velike i
expensive servers to meet existing or anticipated workload requirements. Moreover, capacity could
be added to existing infrastructure by simply adding new servers and systems. Grid computing also
enabled data-center consolidation via server clusterin
skupe servere da ispuni postojeće ili očekivane zahtjeve posla. Osim toga, kapacitet se može dodati
na postojeće infrastrukture jednostavnim dodavanjem novih servera i sistema. Grid računarstvo
također omogućilo je konsolidacijeu data-centara preko clusteringa servera.
NIST cloud computing model sastoji se od pet jedinstvenih karakteristika, tri servis modela, te četiri
razvojna modela. Pet karakteristika povezanih sa ovim modelom uglavnom omogućavaju lakšu
dostupnosti izmjerenog, skalabilan, elastičnost računarskih resursa koji se mogu preuzeti preko auto-
servisa i može im se pristupiti bilo sa tankih ili debelih klijenata preko mreže.
• Software as a Service – Software as a Service (SaaS) Applications delivered as a service to end users
over the Internet. This model is the earliest model of cloud computing in which software companies
started to sell their solutions to businesses based on the number of users with a given set of service-
level requirements. The major players in this field are Oracle (with its CRM on Demand solution),
Salesforce.com, and
Google (with its Google Apps).
• Software as a Service (SaaS) Aplikacije isporučene kao servis krajnjim korisnicima preko Interneta.
Ovaj model je najraniji model cloud computinga u kojem su softverske kompanije počele da prodaju
svoja rješenja za poslovanja bazirana na osnovu broja korisnika sa datog skupa servis – nivo zahtjeva.
Glavni igrači u ovoj oblasti su Oracle (sa svojim CRM on Demand rješenjem), Salesforce.com, a
Google (sa svojim Google Apps).
• Platforma kao Servis - Platform as a Service (PaaS) Aplikacijski razvoj i razvojne platforme (koja se
sastoji od aplikacijskih servera, baza podataka, itd) isporučuje se kao servis. Amazon Elastic Compute
Cloud (EC2) i Savvis su istaknuti nosioci ovog modela cloud servisa.
• Infrastructure as a Service (IaaS) Server, storage, and network hardware and associated software
delivered as a service. Amazon EC2 is the prominent provider of this model of cloud service. Key
technologies that have enabled cloud computing in general are virtualization and clustering.
• Infrastruktura kao usluga - Infrastructure as a Service (IaaS) Server, skladištenje i mrežni hardver i
pripadajući softver isporučuju se kao servis. Amazon EC2 je istaknuti provajder ovog modela cloud
servisa. Ključne tehnologije koje su omogućile cloud computing općenito su virtualizaciju i klastering
– clustering.
Virtualization
Virtualization allows users to overcome the restrictions associated with sharing physical computing
resources such as servers, storage, and networks. For example, virtualization of servers allows users
to run multiple operating system images on a single server. Virtualization of network infrastructure
allows users to share network bandwidth by creating virtual local area networks (VLANs).
Virtualization in cloud computing typically involves deploying many operating system images (virtual
machines or VMs) on a single server sharing available CPU resources and memory. Being able to
deploy many VMs also allows users to pay only for the resources they use instead of paying for all the
installed capacity on the servers. This also facilitates monitoring of resource consumption by
individual VMs for use by charge-back systems later. Most of the virtualization software that is
available today is based on hypervisor technology. IBM introduced hypervisor technology in the
1960s with a mainframebased product called CP/CMS, which evolved into a product known as z/VM.
Using hypervisor technology for server virtualization is more popular than using hardware
partitioning or OS partitioning (host OS based), for the following reasons:
Virtualizacija
Virtualizacija omogućava korisnicima da prevaziđu ograničenja povezana sa fizičkim dijeljenjem
računarskih resursa, kao što su serveri, skladištenje, i mreža. Na primjer, virtualizacija servera
omogućuje korisnicima pokretanje slika-image-a više operativnih sistema na jednom serveru.
Virtualizacija mrežne infrastrukture omogućava korisnicima da dijele mrežnu propusnost stvaranjem
virtualne lokalne mreže (VLAN-a). Virtualizacija u cloud computingu obično uključuje postavljanje
slika većeg broja operativnih sistema (virtualne mašine ili VM) na jednom serveru dijeljenjem
dostupnih CPU resursa i memorije. Biti u mogućnosti za postavljanje mnogih VM-a također
omogućava korisnicima da plaćaju samo resurse koje koriste umjesto plaćanja za sve instalirane
kapacitete na serverima. Ovo također olakšava praćenje potrošnje resursa po pojedinoj VM za
korištenje od strane charge-back sistema kasnije. Većina virtualizacijskog softvera koji je dostupan
danas se temelji na Hipervizor tehnologiji. IBM je predstavio Hipervizor tehnologiju 1960-te godine sa
mainframe baziranim proizvodom pod nazivom CP/CMS, koji evoluirao u proizvod poznat kao z/VM.
Korištenje Hipervizor tehnologije za virtualizaciju servera je popularnije nego korištenje hardverskog
particioniranja ili OS particije (host baziran OS), iz sljedećih razloga:
• Ease of deployment VMs can be quickly deployed or undeployed with a click of a button.
• Jednostavnost implementacije VM-a mogu se brzo rasporediti ili vratiti u prijašnje stanje sa klikom
na tipku.
• Isolation Since each VM provides a complete image of the operating environment, including the
choice of operating system and applications, it provides excellent isolation capabilities for users
sharing the same servers.
• Hypervisor used Some vendors, such as VMware, developed their own hypervisors (VMware’s is
called ESX), whereas others, such as Oracle with its Oracle VM, leverage the open source Xen
hypervisor as the foundation for their solution.
• Hipervizor korišten od Nekih proizvođača, kao što su VMware, razvili su svoje vlastite hipervizore
(VMware je nazvan ESX), dok su drugi, kao što su Oracle sa svojim Oracle VM, protuteža open source
Xen Hipervizoru kao temelj za njihovo rješenje.
• Full virtualization Products such as those from VMware support full virtualization; that is, they run a
binary image of the OS and emulate real I/O device drivers. Other offerings that support full
virtualization are KVM and Xen-HVM.
Potpuna virtualizacija Proizvoda kao što su oni iz VMware podrške pune virtualizacije, to je,
oni vode binarnu sliku OS i oponašaju prave I/O upravljačke programe - drivere uređaja.
Ostatak nudi one podržavaju punu virtualizaciju su KVM i Xen-HVM.
• Paravirtualization Products that support paravirtualization, such as Oracle VM, run OSes that are
ported to specific hardware architecture and are hypervisor-aware. As such, they use generic device
drivers to perform regular system functions. Virtualization is essential for cloud providers to be able
to provide end users with computing resources at a lower cost. Virtualization also helps cloud
providers to maximize utilization of resources and reduce capital expenditures by avoiding
implementation of siloed IT infrastructure.
• Paravirtualizacijski Proizvodi koji podržavaju paravirtualizaciju, kao što su Oracle VM, pokrećei OS
koji se prenose na specifične hardverske arhitekture i Hipervizor-aware su. Kao takvi, oni koriste
generičke upravljačke programe-drivere za obavljanje redovnih sistemskih funkcija. Virtualizacija je
od suštinskog značaja za cloud ponuđače da bi bili u mogućnosti pružiti krajnjim korisnicima
računarske resurse po nižoj cijeni. Virtualizacija također pomaže cloud ponuđačima da maksimiziraju
korištenje resursa i smanje kapitalne izdataka zaobilaženjem implementacija in-house IT
infrastrukture.
Clustering
Clustering allows multiple systems to function as one large system by using software and networking
technologies such as shared file systems, high-speed interconnects (for servers), and similar
technology. This, in turn, helps users to scale out their applications easily by adding more systems to
an existing cluster to overcome the limits of physical resources (CPU and memory) in a single server.
It also makes the Migrating to the Cloud applications highly available by allowing them to run on
multiple servers in an active-active fashion to avoid single points of failure. Grid computing, as
discussed earlier, was all about clustering commercially available, off-the-shelf hardware
technologies to create powerful, scalable computing infrastructure. In some ways, grid computing
was an early form of cloud computing in that it ensured availability of applications and masked the
servers which executed specific requests in the grid.
Clustering
Clustering omogućava više sistema da djeluje kao jedan veliki sistem pomoću softvera i mrežnih
tehnologija, kao što su zajedničke sistemske datoteka, high-speed među-konekcijama (za servere), i
slične tehnologija. Ovo, pokreće, i pomaže korisnicima da uvećaju svoje aplikacije dodavanjem više
sistema na postojeći klaster da prevaziđu granice fizičkih resursa (CPU i memorije) na jednom
serveru. Također čini Migriranje na Cloud aplikacije visoko dostupnim dopuštajući im da rade na više
servera u active-active modu da se izbjegnu jednomjesni kvarovi. Grid računarstvo, kao što je ranije
rečeno, bio je sve o grupisanju komercijalno dostupnih, u standardizranim hardver tehnologijama za
stvaranje moćne, skalabilne computing infrastrukture. Na neki način, mrežni computing je bio rani
oblik cloud computinga po tome što je osiguravao dostupnost aplikacija i maskirao servere koji
izvršavaju specifične zahtjeve u mreži.
• Public cloud As the name suggests, this type of cloud deploymentmodel supports all users who
want to make use of a computing resource, such as hardware (OS, CPU, memory, storage) or
software (application server, database) on a subscription basis. Most common uses of public clouds
are for application development and testing, non-mission-critical tasks such as file-sharing, and e-
mail service.
• Public Cloud, kao što mu i samo ime govori, ova vrsta razvojnog modela cloud-a podržava sve
korisnike koji žele kristiti computing resurse, kao što su hardver (OS, procesor, memorija,
skladištenje) ili softver (aplikacijski server, baza podataka) baziran na pretplati . Najčešća upotreba
javnih oblaka su za razvoj aplikacija i testiranje, ne-kritične zadatke kao što su file-sharing, i e-mail
servis.
• Private cloud True to its name, a private cloud is typically infrastructure used by a single
organization. Such infrastructure may be managed by the organization itself to support various user
groups, or it could be managed by a service provider that takes care of it either on-site or off-site.
Private clouds are more expensive than public clouds due to the capital expenditure involved in
acquiring and maintaining them. However, private clouds are better able to address the security
and privacy concerns of organizations today.
• Privatni oblak odgovara svom imenu, privatni oblak je tipično infrastruktura korištenae od strane
jedne organizacije. Takvom infrastrukturom može upravljati sama organizacija za podršku različitim
grupama korisnika, ili može upravljati provajder koji se brine za to na licu mjesta ili izvan lokacije.
Privatni oblaci su skuplji od javnih oblaka zbog kapitalnih rashoda uključenih u sticanje i njihovo
održavanje. Međutim, privatni oblaci mogu bolje da omoguće sigurnost i privatnost za koje su danas
organizacije veoma zainteresovane.
• Hybrid cloud In a hybrid cloud, an organization makes use of interconnected private and public
cloud infrastructure. Many organizations make use of this model when they need to scale up their IT
infrastructure rapidly, such as when leveraging public clouds to supplement the capacity available
within a private cloud. For example, if an online retailer needs more computing resources to run its
Web applications during the holiday season it may attain those resources via public clouds.
Hibridni cloud, kod hibridnog oblaka, organizacija koristi među-povezane privatne i javne
cloud infrastrukture. Mnoge organizacije koriste ovaj model, kada im je potrebno da uvećaju
svoju IT infrastrukture brzo, kao kada se oslanjaju na javne oblaka za dopunu raspoloživih
kapaciteta unutar privatnog oblaka. Na primjer, ako online trgovac treba više računarskih
resursa za pokretanje svojih Web aplikacija za vrijeme praznika može postići te resurse putem
javnog oblaka.
• Community cloud This deployment model supports multiple organizations sharing computing
resources that are part of a community; examples include universities cooperating in certain areas of
research, or police departments within a county or state sharing computing resources. Access to a
community cloud environment is typically restricted to the members of the community. With public
clouds, the cost is typically low for the end user and there is no capital expenditure involved. Use of
private clouds involves capital expenditure, but the expenditure is still lower than the cost of owning
and operating the infrastructure due to private clouds’ greater level of consolidation and resource
pooling. Private clouds also offer more security and compliance support than public clouds. As such,
some organizations may choose to use private clouds for their more mission-critical, secure
applications and public clouds for basic tasks such as application development and testing
environments, and e-mail services.
•Oblak Zajednice. Ovaj model podržava raspoređivanje više organizacija dijeljenjem računarskih
resursa koji su dio zajednice, primjeri uključuju univerzitetsku saradnju u određenim područjima
istraživanja, odnosno policijskih uprava unutar regije ili države dijeljenjem računarskih resursa.
Pristup okruženju cloud zajednice obično je ograničena na pripadnike zajednice. S javnim oblacima,
cijena je obično niska za krajnjeg korisnika i nema kapitalnih izdataka uključenih u ovaj poduhvat.
Korištenje privatnog oblaka uključuje kapitalne troškove, ali potrošnja je i dalje niži od troškova
posjedovanja i rada infrastrukture zbog privatnih oblaka 'veći stepen konsolidacije i udruživanja
resursa. Privatni oblaci također nude više sigurnosti i usklađenosti podrške od javnih oblaka. Kao
takve, neke organizacije mogu odabrati da koriste privatne oblake za svoje kritičnije procese, sigurne
aplikacije i javne oblake za osnovne zadatke kao što su razvoj aplikacija i testiranje okruženja, i e-mail
servise.
WHY MIGRATE?
Many organizations adopt a “don’t fix it if it’s not broken” approach when it comes to adopting the
latest technologies and architectures. The main reasons behind this approach are cost, uncertainty,
and fear of failure. Some organizations also think that new systems and architectures cannot match
or outperform their current systems. In adopting this approach, these organizations miss out on
many important advances in software and hardware technology, as well as the advantages offered by
the latest standards and architectures. Not adopting new technologies, platforms, and standards can
result in the following:
ZAŠTO MIGRIRATI?
Mnoge organizacije su usvojile "ne popravljaj ako nije pokvareno" pristup kada je u pitanju usvajanje
najnovijih tehnologija i arhitekture. Glavni razlozi iza ovog pristupa su trošak, nesigurnost i strah od
neuspjeha. Neke organizacije također misle da se novi sistemi i arhitekture ne podudaraju ili
nadmašuju njihove trenutne sisteme. Prilikom usvajanja ovog pristupa, ove organizacije propuštaju
mnoge važne prenodsti u softverskoj i hardver tehnologiji, kao i prednosti koje nude najnoviji
standardi i arhitekture. Neusvajanje novih tehnologija, platformi, i standarda može rezultirati u
sljedećem:
• Longer time to market It takes longer to roll out new services and features to support business
expansion and acquisitions.
• Cost of maintenance Over the years, it becomes expensive to maintain staff for ongoing system
maintenance and routine updates. Legacy software vendors also incur increased costs in supporting
the very large number of customers using their products.
• Difficult to integrate Integrating legacy applications with newer and modern standards-based
applications, special tools, and services is necessary, but difficult.
• Duže vrijeme na tržištu - potrebno je više vremena da se uvedu novi servisi i mogućnosti da podrže
širenje poslovanja i akvizicija.
• Troškovi održavanja Tokom godina, postaje skupo za održavanje personal za tekuće održavanje
sistema i rutinsko ažuriranja. Nasljeđe softvera također snositi povećane troškove u podršci velikog
broja kupaca koriste njihove proizvode.
• Faster, more efficient hardware Technology is improving at a faster rate, resulting in systems on the
market today that are exponentially faster than their predecessors. Therefore, organizations can
benefit from periodically updating their systems by having similar or smaller hardware configurations
delivering the same level of performance.
• Brži, efikasniji hardverske tehnologija je poboljšanje na bržu kurs, što je rezultiralo u sistemima na
tržištu danas da su eksponencijalno brži od svojih prethodnika. Stoga, organizacije mogu imati koristi
od periodičnog ažuriranja svojih sistema koje imaju slične ili manje hardverske konfiguracije
isporukom istog nivoa performansi
• Leveraging of the latest standards It becomes much easier to integrate and exploit the latest trends
in software and hardware technologies, such as SOA and cloud computing. This can result in
standardization of application architecture and leveraging of business rule engines, business process
management methodologies, and Web services.
• Reduced total cost of ownership Migrating to newer software and hardware platforms can result in
consolidation, therefore reducing the number of disparate environments that must be maintained in
the future. It may also result in higher utilization of IT resources such as CPUs and storage.
Consolidating existing applications into one or two platforms using standard software can cut down
on management costs and enable organizations to get better prices from software vendors as their
usage grows. Organizations can also take advantage of open source software such as operating
systems and development tools to reduce their total cost of ownership. Newer systems based on off-
the-shelf components, such as x86-based systems with open source operating systems (e.g., Linux),
can reduce the cost of ownership significantly.
• Increased agility It becomes easier to modify a business rule, alter a business process, or change a
business service on the fly as doing so does not require unnecessary system downtime. Having a
clear separation of application user interface, business logic, business process orchestration, and
business rules makes it easier to enhance the system when required.
• Povećana agilnost, postaje lakše modificirati poslovne pravilo, mijenjati poslovne procese, ili
promijeniti poslovni servisu hodu jer to ne zahtijeva nepotrebni zastoj sistema. Gdje imamo jasno
razdvajanje korisničkog sučelja aplikacije, poslovne logike, orkestracije poslovnih procesa, i poslovnih
pravila olakšava poboljšanje sistema kada je to potrebno.
• Governance/compliance In older technologies, it is very difficult to implement new requirements
concerning governance and compliance. Newer software products have out-of-the-box features to
support these requirements, such as extensive auditing, logging, monitoring, and security features.
• Longer shelf life Newer technologies have a longer shelf life, so organizations don’t need to pay
exorbitant fees for maintenance. The cost of a migration project is a major source of concern for
most organizations. They need to have a solid business case to justify the up-front investment in
a migration project and be able to show a significant return on investment later. A typical cost
breakdown for a migration project can be as follows:
• Initial discovery/assessment Typically, organizations need to take at least a few weeks to assess
their current portfolio of applications and analyze the impact of migration. This might require
engaging a system integrator or in-house IT staff. Most system integrators provide this type of service
for a fee.
• Migration tools, hardware, and software Depending on the current portfolio of applications and the
target platform, it may be necessary to acquire special migration tools and technologies that can
assist with migration.
• Duži rok trajanja , Novije tehnologije imaju duži rok trajanja, tako da organizacije ne moraju plaćati
astronomske naknade za održavanje. Trošak je migracije projekta je glavni izvor zabrinutosti za
većinu organizacija. Oni moraju imati solidan poslovni slučaj da se opravda up-front ulaganje u
migraciju projekt i biti u stanju pokazati značajan povrat na investiciju kasnije. Tipični trošak kvara za
migraciju projekt može biti kako slijedi:
• Migracijski alati, hardver i softver, ovisno o portfoliju aplikacija i ciljnoj platformi, može biti
potrebno da se stekne posebni migracijski alati i tehnologije koji mogu pomoći u migraciji.
• Migration services Most organizations do not have the skill set to perform migrations, as this is not
their core competency and it is a one-time effort for them. As a result, they may need to hire a
system integrator to perform the migration task. The cost of such a service depends on factors such
as complexity, scope, and the number and size of applications and databases involved.
• Migracijske usluge, Većina organizacija nemaju vještinu postavljanja i obavljanja migracije, jer to
nisu njihove core kompetencije i to je jednokratni napor za njih. Kao rezultat toga, oni će trebati
zaposliti sistem integratora za obavljanje migracijsko zadatka. Cijena takve usluge zavisi o faktorima
kao što su kompleksnost, opseg, kao i broj i veličinu aplikacija i baza podataka uključenih.
• Hardware, software, and storage For the target platform, new hardware, software, and storage
may need to be acquired. The cost of hardware, software, network technology, and storage can also
vary based on size, performance, and vendor, among other factors.
• Hardver, softver i skladištenje, Za ciljnu platformu, novi hardver, softver i skladištenje može biti
potrebno da se pribave. Troškovi hardvera, softvera, mrežne tehnologije, kao i za skladištenje mogu
varirati u odnosu na veličinu, performanse i dobavljača, među ostalim faktorima.
• Testing and production rollout Usually, testing and production rollout are required for any
migration. These tasks are performed by system integrators in most cases. Of these costs, the cost of
acquiring hardware and software for the target platform can be avoided if organizations have spare
hardware and possess licenses for software. Investing in automated migration tools can help to
reduce overall migration costs and increase the quality of conversions in some cases. Investing in
creating appropriate documentation for the new system should also be considered. In most cases,
system integrators or migration service providers perform the task of documenting the new system
as part of the migration effort.