INNORIX in Practice / Server & Cloud-to-Cloud Transfer

We need to replace the servers
and clouds we have used for years.

From replacing an aging server to moving clouds and shutting down an in-house data center. This is the story of one company’s infrastructure transition over two years.

The server that holds the company’s core business data is now 10 years old.

The cloud service signed years ago is due for review, and the way the in-house data center is run needs to change too.

The company decides to replace its main infrastructure step by step over the next two years.

But the old server is still creating new data today, and other teams are waiting for it. Years of stored data also have to move to the new environment.

How do you replace infrastructure used for years while the business keeps running?

November 2026Infrastructure transition plan

  • Business data serverWindows ServerCurrent environment
  • Cloud storageAmazon S3Current environment
  • Company infrastructureIn-house data centerCurrent environment
Work the company runs every day
  • 06:00Daily business data deliveryScheduled
  • 08:00Analytics data preparationScheduled
  • 18:00Business results storageScheduled
  • Every SundayWeekly data archivingScheduled

2026.112027.032027.112028.11

An infrastructure transition story set in a fictional company.

INNORIX in Practice

November 202611.16

COMPANY BACKGROUND, November 16, 2026

The company reviews its entire infrastructure.

The company’s core business systems were built up over many years.

Servers were added whenever a new system was needed, and cloud storage came in as data grew. Many business systems still run in the company’s own data center.

But aging servers, changing cloud contract terms and the cost of keeping the data center running led the company to plan a move to new infrastructure.

THE COMPANY

The company’s current infrastructure

Current environmentIn useReason for change
Windows Server10 yearsAging server
Amazon S35 yearsCloud contract and policy changes
In-house data center12 yearsNew way of running infrastructure

The work that runs on this infrastructure every day

Run timeJobTeam
06:00Daily business data deliveryOperations team
08:00Analytics data preparationData analytics team
18:00Business results storageData management team
Every SundayWeekly data archivingInfrastructure team
Infrastructure changes and business work run on different schedules.While the new environment is being prepared, the work in the current one has to carry on.

Live contextNow

11.16 Infrastructure planNovember 2026

Current infrastructure

  • Windows ServerRunning
  • Amazon S3Running
  • In-house data centerRunning

Current migration

Prepare server replacement

Business work

Daily business data delivery

Next task

New server ready

MARCH 2027, March 2

The new server is ready.

The company decided to replace the Windows Server it had used for 10 years with a new Linux Server.

The new server is installed and configured. But the old server still holds years of business files and the data each team uses.

New data is still being created on the old server.

SERVER REPLACEMENT

Current business server

Windows Server

24 TB

Data to migrate, stored now

  • /business-data/12.8 TB
  • /historical-data/8.4 TB
  • /reports/1.6 TB
  • /operations/1.2 TB
In service

New business server

Linux Server

0 TB

Business data migrated so far

Waiting for data migration
Installed and connected

Server switch date

March 21

First scheduled job on new server

March 22, 06:00

Live contextNow

03.02 New server readyMarch 2027

Current infrastructure

  • Windows ServerRunning
  • Linux ServerPreparing
  • Amazon S3Running

Current migration

Move 24 TB of data

Business work

Scheduled jobs on old server

Next task

Move existing data

March 16

The data moves while the old server keeps working.

Instead of stopping all business work to move the data, the operations team decided to migrate while the old server stays in service.

In INNORIX, they connect the existing Windows Server and the new Linux Server, then choose the data to move and its destination.

Data goes directly from server to server, and the old server keeps running the company’s work.

INNORIX STUDIO

New transfer

2027 business server data migration

Source

Windows Server

D:\BusinessData\

Files selected
284,600
Total size
24 TB

Target

Linux Server

/data/business/

Transfer method
Direct transfer
Run condition
Run now
Source data keptRun transfer

While the migration runs, the existing daily business data delivery and analytics data preparation jobs keep running too.

INNORIX STUDIO / RUNS

Server migration period

March 18

Windows Server — Linux Server

14.6 TB/ 24 TB60.8%

Scheduled transfers running in the same period

  • 06:00Daily business data deliveryCompleted
  • 08:00Analytics data preparationCompleted
  • 18:00Business results storageCompleted

March 16March 18March 20

Live contextNow

03.16 Move existing dataMarch 2027

Current infrastructure

  • Windows ServerRunning
  • Linux ServerReceiving data
  • Amazon S3Running

Current migration

Move 24 TB of data

Business work

Scheduled jobs on old server

Next task

Confirm final scope

March 20

All existing data has moved, but the migration isn’t finished.

The 24 TB of data first selected for migration has arrived on the new server.

But work continued on the old Windows Server over the past few days, creating new files and changing existing ones.

To start work on the new server, this data has to be included in the migration too.

MARCH 20, MIGRATION REVIEW

Windows Server

24.6 TB

24 TBData first selected
600 GBData created during migration

Linux Server

24 TB

24 TBData migrated
600 GBStill to migrate

Company data keeps changing even while it is being copied.

Final migration

New files
600 GB
Changed existing files
Resent after ops review
Unchanged data already moved
Kept as migrated

The operations team checks the list of files created or changed during the migration. They set those files up as a separate transfer and move them at the final cutover.

Live contextNow

03.20 Confirm final scopeMarch 2027

Current infrastructure

  • Windows ServerRunning
  • Linux ServerReceiving data
  • Amazon S3Running

Current migration

Move 24 TB of data

Business work

Scheduled jobs on old server

Next task

Switch business server

March 21

From tomorrow, work runs on the new server.

On Sunday evening, the operations team carries out the planned final cutover.

They briefly block file writes on the old business systems and move the last changed data. They also finish checking the files and business systems in the new environment.

Now the file transfer jobs that used the old Windows Server need to run in the new environment.

INNORIX STUDIO / FLOWS

Daily business data delivery

Source

Linux Server

/data/business/daily/

Target

Amazon S3

/business-data/daily/

Schedule
Daily 06:00
File filters
Same conditions, paths checked
Save rules
Same conditions
Recovery policy
Same policy

BeforeAfter

Next run: March 22, 2027, 06:00

The 6 a.m. daily job keeps the same purpose and schedule. Only its transfer source changes, from the old Windows Server to the new Linux Server.

The other server transfer jobs also move to the new environment once their paths and permissions are checked.

Live contextNow

03.21 Switch business serverMarch 2027

Current infrastructure

  • Windows ServerRunning
  • Linux ServerVerifying
  • Amazon S3Running

Current migration

Move 24 TB of data

Business work

Scheduled jobs on old server

Next task

First scheduled job on new server

March 22

The first Monday on the new server

MONDAY MORNING

06:00

The first scheduled transfer starts on the new server.

INNORIX STUDIO / RUNS

Daily business data delivery

SourceLinux Server

TargetAmazon S3

Finished06:14

Completed

At 8 a.m., the data analytics team starts work as usual.

The analytics team doesn’t need to know the new server’s operating system or storage paths. The data they need is ready in the agreed storage.

After checking the scheduled transfer results on the new server, the operations team keeps the old server for a while as a fallback.

When the verification period ends, the Windows Server used for 10 years is retired.

Live contextNow

03.22 First job on new serverMarch 2027

Current infrastructure

  • Windows ServerKept as fallback
  • Linux ServerRunning
  • Amazon S3Running

Current migration

Verify new server

Business work

Scheduled jobs on new server

Next task

Change cloud storage

EIGHT MONTHS LATER, NOVEMBER 2027

This time, the cloud storageused for years has to change.

Current cloud

Amazon S3

180 TB

Data stored over the past five years

New cloud

Azure Blob Storage

0 TB

New storage ready

The new cloud contract is signed, but the company’s data is still in the old environment.

INNORIX in Practice

November 202611.16

NOVEMBER 2027, November 1

A new cloud contract is signed.

With its future work environment and operating policies in mind, the company decided to move its cloud storage to Azure Blob Storage.

Amazon S3 holds five years of business data, analysis results and archives.

Several teams still use this storage.

EXISTING CLOUD DATA

Amazon S3

180 TB

  • Past business data92 TB
  • Analytics data and results36 TB
  • Business results and reports24 TB
  • Archive data28 TB

Transfer jobs that use this storage today

JobSourceTarget
Daily business data deliveryLinux ServerAmazon S3
Analytics data preparationAmazon S3Analytics server
Business results storageBusiness serverAmazon S3
Weekly archivingAmazon S3Archive server

Moving to a new cloud is more than copying 180 TB of data.

The jobs that send data to the old storage, and the jobs that take data from it, have to change too.

Live contextNow

11.01 New cloud contractNovember 2027

Current infrastructure

  • Linux ServerRunning
  • Amazon S3Running
  • Azure BlobPreparing

Current migration

Prepare cloud migration

Business work

Work in the old cloud

Next task

Cloud data migration

November 12

Data starts moving between the two clouds.

The operations team connects the new Azure Blob Storage to INNORIX.

They select the data to move in Amazon S3 and set the storage path in Azure Blob Storage.

Data goes directly from the old cloud to the new one.

INNORIX STUDIO / RUNS

Transferring

Cloud storage migration

November 15

Source

Amazon S3

180 TB

Data first selected

Target

Azure Blob Storage

86.2 TB

Data migrated

  • Past business data92 TBTransferring
  • Analytics data and results36 TBPending
  • Business results and reports24 TBPending
  • Archive data28 TBPending

November 12November 15November 19

The data is not staged on a separate server or downloaded to anyone’s PC for the move.

The original data in Amazon S3 stays in place, and work in the old environment carries on.

Live contextNow

11.12 Cloud data migrationNovember 2027

Current infrastructure

  • Linux ServerRunning
  • Amazon S3Running, sending
  • Azure BlobReceiving data

Current migration

Move 180 TB of data

Business work

Work in the old cloud

Next task

Final migration and cutover

November 19

The initial migration is complete.

180 TB of data has arrived in the new cloud storage.

But during that week, 4.8 TB of new data was added to the old storage, and some existing files changed.

The operations team separates the data moved first from the data added or changed since, and runs the final migration.

CLOUD MIGRATION REVIEW

Data in the current and new clouds

First selected4.8 TB created sinceStill to migrate

November 20–21: final migration and cutover

Check initial migration
180 TB
Move newly created data
4.8 TB
Changed existing files
Resent after review
File list and integrity check
Ops team review
Cloud cutover
After verification

The final cutover runs in a planned window. The team stops new file writes, confirms the last migration scope, then checks the data and access permissions in the new storage.

Live contextNow

11.19 Initial migration completeNovember 2027

Current infrastructure

  • Linux ServerRunning
  • Amazon S3Running, sending
  • Azure BlobReceiving data

Current migration

Move 180 TB of data

Business work

Work in the old cloud

Next task

Final migration and cutover

November 21

Changing the jobs that used the old cloud.

The operations team reviews the transfer jobs that use Amazon S3.

In some jobs Amazon S3 receives data. In others it provides data.

They check each transfer setup connected to the old storage and switch it to the new environment.

INNORIX STUDIO / FLOWS

BeforeAfter

The company’s scheduled transfer jobs

JobSourceTargetSchedule
Daily business dataLinux ServerAzure Blob Storage06:00
Analytics data prepAzure Blob StorageAnalytics server08:00
Business results storageBusiness serverAzure Blob Storage18:00
Weekly archivingAzure Blob StorageArchive serverSundays

Checked at cutover

Storage connection, file paths, access permissions, save rules and run conditions

Each job keeps its purpose and schedule, while its references to the old cloud now point to the new storage.

They then check that each transfer setup runs correctly in the new cloud.

Live contextNow

11.21 Cloud cutoverNovember 2027

Current infrastructure

  • Linux ServerRunning
  • Amazon S3Running
  • Azure BlobVerifying

Current migration

Move 180 TB of data

Business work

Work in the old cloud

Next task

First scheduled job in new cloud

November 22

Monday morning, work starts in the new cloud.

MONDAY, NOVEMBER 22

Today’s business work

  • 06:00Daily business data deliveryDone 06:14

    SourceLinux Server

    TargetAzure Blob Storage

  • 08:00Analytics data preparationDone 08:18

    SourceAzure Blob Storage

    TargetAnalytics server

  • 18:00Business results storageDone 18:12

    SourceBusiness server

    TargetAzure Blob Storage

The company’s first scheduled transfer jobs in the new cloud.

The operations team checks the results of the scheduled transfers run in the new storage.

The analytics team starts its morning analysis, and each team stores the day’s work results in the new cloud.

Amazon S3 is kept for a while as a fallback. After final approval from the operations team, its contract is ended.

Live contextNow

11.22 First job in new cloudNovember 22, 2027

Current infrastructure

  • Linux ServerRunning
  • Amazon S3Kept as fallback
  • Azure BlobRunning

Current migration

Verify new storage

Business work

Scheduled jobs in new cloud

Next task

Data center migration plan

SEVEN MONTHS LATER, JUNE 2028

The company decides to shut downits own data center.

A bright data center aisle lined with glass-door server racksAn existing data center with black server racks and yellow cable trays

Current environment

In-house data center

The company’s main business systems, run for 12 years

New environment

Private Cloud

Where the company’s business systems will run next

This time, not one serverbut many business systems have to move.

INNORIX in Practice

November 202611.16

JUNE — NOVEMBER 2028, June 1

Not every business system can move at once.

Many of the company’s business systems run in its own data center.

Each system works differently and each team has its own schedule, so the company decided to move the systems one by one over about six months.

DATA CENTER MIGRATION PLAN

Migration schedule by business system

November 30: the old data center shuts down

Data migration, environment checks and cutover period for each system

The operations team checks where each business system stores its data and which file transfer jobs are connected to it.

When a system finishes moving, its file transfer jobs will switch to the new environment at the same time.

Live contextNow

06.01 Data center migration planJune 2028

Current infrastructure

  • In-house data centerRunning
  • Private CloudPreparing
  • Azure BlobRunning

Current migration

Plan migration by system

Business work

Work in the existing data center

Next task

Move report and business data systems

July

Systems that can move first are switched first.

The report management system and the business data management system are being moved.

Business files go from the existing data center to Linux servers in the new Private Cloud.

Once each system is moved and verified, the source and target of its transfer jobs are changed.

But the analytics system and the core business system still run in the old data center.

SWITCH STATUS BY SYSTEM

July

In-house data center

Systems running in the old environment

  • Report systemSwitched
  • Business data systemSwitched
  • Analytics systemRunning
  • Core business systemRunning
  • Archive systemRunning

Private Cloud

Systems running in the new environment

  • Report systemRunning
  • Business data systemRunning
  • Analytics systemScheduled
  • Core business systemScheduled
  • Archive systemScheduled

JuneJulySeptemberNovember

Each business system moves from the old environment to the new one on its own schedule.

Live contextNow

Jul Migration by systemJuly 2028

Current infrastructure

  • In-house data centerPartly running
  • Private CloudPartly running
  • Azure BlobRunning

Current migration

Switch report and business data systems

Business work

Work in both environments

Next task

Move analytics system

September

The company is running two infrastructure environments.

Some business systems already run in the Private Cloud, while others still run in the company’s own data center.

The company’s data transfer jobs also use different environments.

In INNORIX, the operations team sees which jobs have moved to the new environment and which still use the old one.

INNORIX STUDIO / FLOWS

The company’s data transfer environment in September

JobSourceTargetRuns in
Report storagePrivate CloudAzure Blob StorageNew
Daily business dataPrivate CloudAzure Blob StorageNew
Analytics data prepAzure Blob StoragePrivate CloudNew
Core business resultsOn-premisesAzure Blob StorageOld
Weekly archivingAzure Blob StorageOn-premisesOld

Next to switch

Core business system

Data migration and checks planned for October

Each time a business system moves, its transfer setup changes too.

Jobs that have not moved yet keep running in the old environment.

You don’t have to switch all of your infrastructure at once to run file transfers in a new environment.

Live contextNow

Sep Migration by systemSeptember 2028

Current infrastructure

  • In-house data centerPartly running
  • Private CloudPartly running
  • Azure BlobRunning

Current migration

Prepare core system move

Business work

Work in both environments

Next task

Move core business system

November 25

Checking the last jobs that use the old environment.

The move of the company’s main business systems is almost complete.

The operations team checks whether any transfer jobs still point to servers or paths in the old data center.

Once the archive system, the last to move, passes verification, its transfer jobs will switch to the new environment.

INFRASTRUCTURE MIGRATION REVIEW

Checking transfer references to the old data center

Environment to check

On-premises

Servers and paths in the old data center

Transfer jobs using the old environmentNovember 25

0

  • Weekly archivingPrivate Cloud Archive ServerSwitched

Before final switchAfter final switch

Beyond the last transfer job, the team also checks other applications and data access paths that depend on the old systems.

Based on the file transfer history, migration results and system verification results, they approve shutting down the old data center.

Live contextNow

11.25 Final migration reviewNovember 2028

Current infrastructure

  • In-house data centerPartly running
  • Private CloudPartly running
  • Azure BlobRunning

Current migration

Check old environment references

Business work

Work in both environments

Next task

Data center shutdown

November 30

Shutting down a data center after 12 years.

NOVEMBER 30, 2028

18:00

The last business system has moved.

Old in-house data center

0 / 5

Migrating systems running here

Shut down

New Private Cloud

5 / 5

Migrating systems running here

Running

December 1, 2028: next scheduled job

06:00Daily business data delivery

SourcePrivate Cloud

TargetAzure Blob Storage

The company shuts down the data center it has run for 12 years.

The infrastructure project that began two years ago comes to an end.

At 6 a.m. the next day, the company’s routine data delivery starts on the new infrastructure.

Live contextNow

11.30 Data center shutdownNovember 2028

Current infrastructure

  • Linux ServerRunning
  • Azure BlobRunning
  • Private CloudRunning

Current migration

Project complete

Business work

Work in the new environment

Next task

12.01 06:00 Daily business data delivery

TWO YEARS LATER

Two years on, what environment does the company work in?

All the main infrastructure the company used two years ago has been replaced.

Windows Server became Linux Server, and the company’s cloud storage moved from Amazon S3 to Azure Blob Storage.

The main business systems also moved from the company’s own data center to a Private Cloud.

TWO YEARS OF INFRASTRUCTURE TRANSFORMATION

November 2026

Two years ago

Business data server

Windows Server

Cloud storage

Amazon S3

Company infrastructure

In-house data center

November 2028

Now

Business data server

Linux Server

Cloud storage

Azure Blob Storage

Company infrastructure

Private Cloud

The company’s scheduled work

JobTwo years agoNow
Daily business data delivery06:0006:00
Analytics data preparation08:0008:00
Business results storage18:0018:00
Weekly data archivingEvery SundayEvery Sunday

Over two years, the company’s infrastructure and operations changed a great deal.

The company chose new technologies, services and operating policies, and with each change it moved the data and transfer jobs it needed to the new environment.

Live contextNow

2 years later Infrastructure transition completeNovember 2028

Current infrastructure

  • Linux ServerRunning
  • Azure BlobRunning
  • Private CloudRunning

Current migration

Project complete

Business work

Work in the new environment

The company’s infrastructure may change again.

The operations team manages its current servers and clouds, and the transfer jobs between them, in INNORIX.

INNORIX STUDIO

Devices

DeviceEnvironmentConnection
Business Data ServerLinux ServerConnected
Enterprise Cloud StorageAzure Blob StorageConnected
Business SystemsPrivate Cloud / LinuxConnected
Analytics ServerPrivate Cloud / LinuxConnected
Archive ServerPrivate Cloud / LinuxConnected
The infrastructure the company uses today and the data transfer jobs connected to it.

It may add new servers or move to another cloud in the future.

The company can choose the infrastructure that fits its work, and change its data and transfer setup when it needs to.

Live contextNow

Now Working in the new environmentNovember 2028

Current infrastructure

  • Linux ServerRunning
  • Azure BlobRunning
  • Private CloudRunning

Current migration

Project complete

Business work

Work in the new environment

INFRASTRUCTURE CHANGES. BUSINESS CONTINUES.

Over two years, the companychose new infrastructure.

  • Business data serverWindows ServerLinux ServerNew environment
  • Cloud storageAmazon S3Azure Blob StorageNew environment
  • Company infrastructureIn-house data centerPrivate CloudNew environment

Next business day06:00

Daily business data deliveryNext run scheduled

Servers are replaced when they get old.

Clouds are chosen to fit the company’s needs.

The way infrastructure is run changes over time, too.

The company chooses the infrastructure it needs.INNORIX delivers the data in that environment.

THE TECHNOLOGY BEHIND THIS STORY

Server & Cloud-to-Cloud Transfer

Move data directly between different servers and clouds, and keep file transfer jobs running as the company’s infrastructure changes.

Explore the product