Scribd
Upload
7 views

Best practices for database migration

To ensure a smooth data migration project, understand the data's usage, assess source and target environments, and verify business requirements early on. Key risks include security concerns, long transfer times, and unexpected costs due to improper planning. Despite these risks, the long-term benefits of modernizing IT systems generally outweigh the challenges associated with data migration.

Uploaded by

Tesfaye
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
7 views

Best practices for database migration

To ensure a smooth data migration project, understand the data's usage, assess source and target environments, and verify business requirements early on. Key risks include security concerns, long transfer times, and unexpected costs due to improper planning. Despite these risks, the long-term benefits of modernizing IT systems generally outweigh the challenges associated with data migration.

Uploaded by

Tesfaye
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/ 1

Best practices

To ensure that your project goes smoothly, adhere to the following best practices:

Understand the data and what it’s used for. Who uses the data now, who will use it in the future, and
how will it be used? Data that’s leveraged for analytics, for example, may have very different storage and
formatting requirements than data being retained for regulatory compliance. Be sure to gather
information from all relevant stakeholders and business units throughout the migration process.

Assess the source and target environments carefully. Will the same operating system be running in both
environments? Will database schemas or other formatting need to change? Are there any problems (like
redundancy issues or an excess of “dirty” data) that need to be addressed before the migration?

Verify business requirements and potential impact early in the process. What kind of migration
timeline is necessary? If a data center is being decommissioned, when will its lease expire? What types
of data security must you maintain throughout the migration process? Is any data loss or corruption
tolerable, and if so, how much? How would delays or unexpected stumbling blocks affect the business?

Risks

Though the benefits of modernizing IT systems outweigh the risks associated with data migration—
especially over the long term—data migration can be stressful and risky. Here are some of the risks to
account for:

 Security: Make sure all data is securely encrypted before migration. For offline migrations that
involve shipping data storage devices, verify security of the shipper’s freight and logistics
services.

 Long transfer times: It can be challenging to predict online transfer times with complete
accuracy. Network bottlenecks may restrict connection speeds, or system hardware limitations
might throttle the amount of data that can be read from or written to them.

 Higher-than-expected costs: Unanticipated costs often result from improper planning. For
example, online transfers that take longer than expected will incur additional charges. Retaining
a vendor-provided storage appliance for longer than you’d initially agreed to keep it (which can
result from transferring the data to the appliance or shipping delays) can incur extra charges as
well.

You might also like