Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comments for Data Migration Tips #1936

Open
sethjensen1 opened this issue Feb 4, 2023 · 1 comment
Open

Comments for Data Migration Tips #1936

sethjensen1 opened this issue Feb 4, 2023 · 1 comment

Comments

@sethjensen1
Copy link
Contributor

Comments for https://www.endpointdev.com/blog/2023/02/migration-tips-and-tricks/
by Josh Tolley

To enter a comment:

  1. Log in to GitHub
  2. Leave a comment on this issue.
@jonjensen
Copy link
Member

Great article, Josh! Many of the principles you mention have saved me over and over.

A few other things on my data migration checklist:

  • As early in the project as possible, give us a copy of all the data as it is now, complete, unmodified, in its messy actual state in the standard export format for the database it lives in.
  • During a multi-month migration project give us a fresh database export about once every week so we can re-run our automation scripts against the latest data and catch new things that will break it. (As they often do.)
  • Data migration scripts and mappings should be visible to everyone involved in the project, including managers and subject matter experts, as well as developers and database experts. People who can't understand everything about the programming may still spot things that could be wrong and should be discussed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants