Scribd
Upload
145 views2 pages

Data Centre Migration Discovery Checklist

This document provides a checklist of information that should be collected during the data discovery phase of a data center migration project. The checklist includes details about devices, workloads, locations, dependencies, backups, support contracts, and other important attributes. Gathering this information upfront will help identify any potential compatibility issues or special considerations for migrating applications and workloads to the cloud.

Uploaded by

Amit Awasthi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
145 views2 pages

Data Centre Migration Discovery Checklist

This document provides a checklist of information that should be collected during the data discovery phase of a data center migration project. The checklist includes details about devices, workloads, locations, dependencies, backups, support contracts, and other important attributes. Gathering this information upfront will help identify any potential compatibility issues or special considerations for migrating applications and workloads to the cloud.

Uploaded by

Amit Awasthi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Data Centre Migration Discovery Checklist

A lot of organizations are discussing and actioning plans to migrate either part or all their workloads
from on prem into the Cloud. Regardless of how much you are moving or the size of your
organization everyone must start with the same common start point, a discovery.

This checklist can be used as a starting point to guide you on what information you need to start to
collate for your discovery phase.

☐ Device Name - What is the device name

☐ Device Type/Model - What is this device, physical server, virtual, networking switch

☐ Firmware versions (if appropriate) - A check in on firmware versions will help you understand
if you may hit any compatibility issues etc

☐ Operating System - What is the operating system version, again this will help you understand
if you may hit any compatibility issues etc

☐ Physical Location - Where is the device physically location in your data centre

☐ What does the device/server do? - What does this server or device do? Is it the server that
runs your payroll system? Or the one that hosts your canteen lunch menu?

☐ Workload owner & contact details - Who in the business is the owner of this workload, who
needs to authorise outages, changes etc

☐ Workload manufacturer - If you are running an application on the server, who made it, is it
external? is it internal?

☐ Workload lifecycle - Is the workload a long term one, one that will be replaced or retired in a
few months

☐ Support contract information (hardware) - Contact information for your hardware vendor
support

☐ Support contract information (workload) - Contact information for your workload vendor
support

☐ Environment (prod, dev, test, etc) - Which environment does this server/device sit in?

☐ Dependencies (what does this server interact with) - What does this server/device/workload
interact with, what does it rely on what what relies on it? Data information (connection details,
sources, etc)

☐ Certificates - Are there any certificate implications? Secure HTTPS website etc that need to be
sourced/saved/moved?

☐ Availability - Does the workload need to be available 24/7? Or are there times when an
outage can be accepted?

☐ Backup information - What is backed up and needs to be protected on this workload

☐ Backup schedule - What is the backup window for this workload


☐ Criticality - How important is this workload to the business?

☐ Disaster Recovery information - What current plans are in place should the worst happen?

☐ System and/or network diagrams - Diagrams of your environment can be useful quick
reference guides

☐ Sensitive Data/Personally Identifiable Information (PII) being stored - Is the system storing
sensitive data and as such will need to be considered when moving to the Cloud?

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy