When an organization starts thinking about a move to the cloud, one of the first questions is usually how long the business will have to be down. Some managers already imagine an entire weekend when employees cannot log in to the systems and the IT people work until morning to move everything. In practice, if the move is planned in an orderly way, that part can be much shorter than people think.
Most of the time is invested in preparation. You need to understand which systems exist in the organization, which systems are connected to each other, what information needs to be transferred and what is important to check before setting a date. You also need to think about the people who use the systems every day. When can they manage without a certain system for a few hours? Who needs to be available to test it after the move? And what do you do if a problem is discovered?
The period after the holidays can be convenient for planning such a move, especially in organizations where the pace of work eases a little. If you are considering a move to the cloud, it is worth getting to know the stages in advance. That makes it much easier to understand why the time is devoted and what is expected to happen at each stage.
What Do You Check Before You Start Moving Systems to the Cloud?
Before setting a date for the move, you first need to understand what exists in the organization today. You start with an orderly list of the systems you use: servers, software, databases, accounting systems, ERP, customer management software, internal systems and external services. Sometimes at this stage you discover old systems that are still active, even though only a few people remember what they are used for. It is also possible that a certain process runs automatically every night and almost nobody deals with it day to day. All of these need to be in the picture before anything is moved. The goal is simple: to know what exists, who uses it and how much the business activity depends on it.
After finishing the list, you check how the systems relate to each other. For example, the sales system may automatically pass information to accounting, or one system may send data to another every few hours. If you move one of them without understanding that connection, the process may stop working. So at this stage you also decide what is right to move together and what can be moved at another stage. In organizations with many systems it is customary to carry out the move in several groups. You start with a relatively simple part, check how it works in the new environment, learn from the experience and only then continue. For you this means the move progresses in an orderly way, and at each stage you know exactly what has already moved and what remains.
How Do You Choose a Date for the Move Without Disrupting Day-to-Day Work?
There is no single date that suits every organization. For a company that works mainly Sunday to Thursday, a weekend can be a convenient time. A business that serves customers abroad may be active on Friday or Saturday because of time differences. A factory that works in shifts may run certain systems almost around the clock. So the question is when, in your case, use of the systems is lower. You can examine the data and see during which hours there are fewer logins, when fewer actions are performed and on which days there is less load. This data helps you choose a time when the move will affect as few employees and customers as possible.
Then you also go over the organization's calendar. End of month, payroll, end of quarter, financial reports, a big promotion, a conference or an important project are times when it is usually better to leave the systems as they are. You also need to check which of the relevant people will be available. Suppose the finance system is moving to the cloud. After the transfer you need someone from the department who knows it and can log in, perform a few actions and make sure everything works as usual. The same is true for sales, service, production or any other central system. When you plan the date far enough in advance, it is easier to find a date when activity is relatively low and the necessary people are available. Sometimes that is exactly the reason a date that looked excellent at first gets replaced by another.
What Actually Happens During the Transfer to the Cloud?
Before starting to transfer the information, a backup is made and checked to be sound. That way there is a copy that makes it possible to go back to the previous state if the need arises. A large part of the information can move to the cloud even before the move date itself. Afterward the changes added since the first copy are transferred. In this way there is no need to move all the information at one moment, and the downtime of the systems can be shortened significantly. How long does it take? The answer depends on the amount of information, the number of systems and their complexity. In an organization where the planning was done in advance, the move itself can take just a few hours.
Once the information is in the new environment, you start checking that everything works. Here the testing needs to be very practical. Can employees log in? Do the files open? Can an invoice be issued? Does the sales system pass information to the system that is supposed to receive it? For each system a list of actions to check is prepared in advance. The technology people check the technical side, and the employees who know the systems check the day-to-day work. This is an important point, because a system can look sound technically and still have a particular action that employees cannot perform.
Only after the tests are finished and the relevant people confirm that everything works is the move considered complete. Where appropriate, the previous environment is also kept available for a period defined in advance, to make it easier to deal with an unusual situation if one is discovered in the first days.
What Happens in the First Weeks After the Move Is Complete?
On the first day everything can work excellently, and there is still something to check. Only after employees return to a regular work routine can you see how the new environment handles the real load. You monitor the speed of the systems, resource consumption, recurring faults and unusual messages. Sometimes you discover that a certain system needs slightly more resources than estimated in the planning. Another system may consume less. In a cloud environment such adjustments can be made as needed, so the first weeks also serve for a more precise tuning of the environment.
It is also very important to talk with employees during this period. They feel things that do not always show up in reports. An employee may say that a certain screen loads more slowly, that a printer no longer appears in the same place or that an action he used to perform in a certain way has changed. These are usually small things that can be solved quickly, especially when the information arrives on time. After a few weeks it is worth conducting an orderly review to see what worked well, where adjustments were required and what is worth improving later. If the organization moves its systems in several stages, the conclusions help plan the next stage better. If all the systems have already moved, the review provides orderly documentation of the process and of the new computing environment.
Why Is a Quiet Move a Sign That the Planning Was Good?
After all the preparation, the evening before the move itself can feel fairly calm. And that is exactly what you want. People know what they need to do, the order of actions has already been set, the backup is ready and the checklist is waiting for the team. If a question arises, it is already clear who should answer it. When the planning is done properly, most of the important decisions are made in the weeks before the move, so on the night itself what remains is mostly carrying out what was already planned.
This is also the reason it is worth starting a cloud migration well before the date on which you want to carry out the move. You need time to map the systems, understand the connections between them, check the organization's calendar and coordinate among all the people who need to be part of the process. Then comes the move itself, and in the weeks after it you monitor the environment and make adjustments as needed. When you give each stage its time, the move becomes much clearer to managers and employees alike. You know when each system moves, how long it is expected to be less available, who tests it and when you return to regular work. That way the whole process proceeds in a calmer and more orderly way.
ExSitu: We Accompany You from Planning Until the Systems Work in the Cloud
At ExSitu we accompany businesses and organizations in cloud migration projects, from mapping the systems and understanding the needs through carrying out the move and monitoring in the period afterward. Together with you we examine which systems exist, what depends on what, what time is suitable for carrying out the move and who needs to be available at each stage. Then we plan the transfer, run the tests and continue to monitor the new environment as employees return to working in it fully.
The ExSitu team includes about fifty technology experts and serves hundreds of customers and tens of thousands of users. Alongside projects and migrations we also provide managed cloud, system administration services, information security and 24/7 human support, working in accordance with the ISO 27001 standard and the requirements of GDPR and HIPAA. If you are already thinking about a date when you would like to move to the cloud, you are welcome to contact us today. Together we can understand exactly what is required in your case, build a schedule that fits your activity and reach the move when every stage is already clear.
