snowdrift/tasks
12
1

Import old contacts data into CiviCRM #586

Open
opened 2020年04月24日 00:00:13 +02:00 by Salt · 9 comments
Owner
Copy link
  • 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
- [ ] 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 - [x] 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

marked this issue as related to #438

marked this issue as related to #438
Author
Owner
Copy link

mentioned in issue #587

mentioned in issue #587
Author
Owner
Copy link

changed title from Import old data into CiviCRM to Import old {+contacts +}data into CiviCRM

changed title from **Import old data into CiviCRM** to **Import old {+contacts +}data into CiviCRM**
iko commented 2021年10月22日 23:48:18 +02:00 (Migrated from gitlab.com)
Owner
Copy link

mentioned in issue #582

mentioned in issue #582
iko commented 2021年10月23日 00:06:20 +02:00 (Migrated from gitlab.com)
Owner
Copy link

mentioned in issue #680

mentioned in issue #680
iko commented 2021年10月23日 00:07:20 +02:00 (Migrated from gitlab.com)
Owner
Copy link

marked this issue as related to #680

marked this issue as related to #680
Author
Owner
Copy link

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.

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.
Author
Owner
Copy link

marked the checklist item import old database backups as completed

marked the checklist item **import old database backups** as completed

Also related to #374

Also related to #374
Sign in to join this conversation.
No Branch/Tag specified
master
master-pre-reset
v0.1.4
v0.1.3
v0.1.2
v0.1.1
release-0.1.0.1
Labels
Clear labels
Blocked
Confidential
We track some issues in a private repo, typically when they contain personal information. In the interest of transparency (and ease of tracking for us), we also keep a stub here in the public issues.
design
Visual design and assets
dev
dev/frontend

Archived

docs
Documentation
finances
Management of financial accounts; Grants and other funding sources
good first issue
Issues that do not require in-depth understanding of background or code
governance
Organisational structure and bylaws
legal
Legal terms, policies and documents
needs-info

Archived

ops
Operations
outreach
Community messaging and recruitment
product/blog
For the blog / Ghost
product/crm
For the CRM / CiviCRM
product/elm-site
Relates to https://codeberg.org/snowdrift/elm-website
product/forum
For the forum / Discourse
product/wiki
product/yesod-site
Relates to https://codeberg.org/snowdrift/snowdrift
research
Research, reference materials and studies
security
Issues about authorisation and authentication
type
bug
Broken feature or regression
type
chore
Housekeeping
type
feature
New feature or functionality
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
snowdrift/tasks#586
Reference in a new issue
snowdrift/tasks
No description provided.
Delete branch "%!s()"

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?