- check that all relationships from old DB have been included in updated CiviCRM
- verify that contacts are consistent across the multiple backups/migrations
- make snapshot of database before import
- import old database backups
- confirm external/SSO IDs for civi entries map to Snowdrift.coop accounts
- add new entry and confirm fields match up with imported entries
- add entries from contacts made while civi was unavailable (e.g., business cards)
- deduplicate entries
Import old contacts data into CiviCRM #586
marked this issue as related to #438
mentioned in issue #587
changed title from Import old data into CiviCRM to Import old {+contacts +}data into CiviCRM
mentioned in issue #582
mentioned in issue #680
marked this issue as related to #680
I actually went ahead and started on this, without it being as well executed. That said, old backups have been imported, but a snapshot wasn't taken. Also, they have not yet been compared with yet older backups. Finally, relationship data has not been verified, and I'm not certain an easy manner to do that with the mappings we had exported.
All contacts have (hopefully) been de-duped from this particular round of imports.
My next steps on this are to try and compare the current db across various migrated ones. Also, business cards collected or entered elsewhere still need to be added. Relations should be checked and decided on whether they are worth the effort, and SSO IDs need to be verified. Finally, current team members should be given Drupal accounts.
marked the checklist item import old database backups as completed
Also related to #374
Archived
Archived
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?