Project

General

Profile

Migration Documentation » History » Version 2

Jon Goldberg, 05/11/2018 09:50 PM

1 1 Jon Goldberg
{{last_updated_at}} by {{last_updated_by}}
2
# Migration Documentation
3
4
### Introduction
5
As the point person for your organization's data migration to CiviCRM, you'll be responsible for reviewing inconsistencies in your source data and making decisions on how to correct it.  This will generally fall into three categories:
6 2 Jon Goldberg
* Data that's incorrect - e.g. an email of `jonatgmailcom`.  The migration script will generate lists of invalid data (e.g. `invalid emails.csv`).  You should clean this data in your source database.  **Do not clean it in the CSV file.**  The script works from a copy of your old database.  If there are too many corrections to be done by hand, contact me for alternative options.
7 1 Jon Goldberg
* The data doesn't map exactly from your old database to CiviCRM.  For instance, your contacts might have "Home", "Summer Home" and "Winter Home" addresses - but CiviCRM only has "Home".  We need to decide whether to add "Summer Home" and "Winter Home", or convert them to something else - perhaps change both to "Home 2".
8
9
### Sharing Data
10
You should have a login to https://share.mayfirst.org from me.  When you log in, you should see five folders: `data`, `errors`, `importlogs`, `raw data`, and `transforms`.
11
* `raw data` is where you should upload your old database (or exported data from your database).  When I ask for a fresh copy of your data, please upload it here.
12
* `data` contains your raw data converted into spreadsheets that CiviCRM can import.  You'll rarely need to look at these.
13
* `errors` contains files you'll need to review (like `invalid emails` above).  Ignore files with a size of `0 KB`.  When all files have a size of `0 KB`, there are no more errors.
14
* You don't need to worry about `importlogs` and `transforms`!