Project

General

Profile

Exporting Raiser's Edge for CiviCRM » History » Version 44

Jon Goldberg, 10/01/2014 11:43 PM

1 44 Jon Goldberg
{{lastupdated_at}} by {{lastupdated_by}}
2
3 24 Jon Goldberg
{{toc}}
4
5 1 Jon Goldberg
h1. Exporting Raiser's Edge for CiviCRM
6
7 23 Jon Goldberg
There are two basic approaches to exporting RE data.  There's the built-in export tool, and there's direct SQL interaction.  This document will try to cover both approaches where possible.  The Export tool has a lower barrier to entry, but a) there's some data you can't export with the tool, and b) the data will be denormalized, requiring additional transformation compared to extracting normalized SQL data.
8 1 Jon Goldberg
9 23 Jon Goldberg
h2. Export tool - general guide.
10
11
The Raiser's Edge Export tool is on the left toolbar when you first enter Raiser's Edge.
12
13 1 Jon Goldberg
From the tool, you will create a number of exports.  When you first create an export, you'll be asked a number of questions, including Export Type (Constituent, Gift, etc.), a checkbox to include inactive records (check this), and an export file type (select CSV).
14
15 23 Jon Goldberg
For most export, select Constituent as the Export type.  This is the "base table" - all records will be joined relative to it.
16 3 Jon Goldberg
17 1 Jon Goldberg
h2. Constituent Based Exports
18
19 21 Jon Goldberg
h3. Contact Information
20 1 Jon Goldberg
21 23 Jon Goldberg
RE differentiates between constituents and non-constituents in their system.  If you create a new contact, they're a constituent - but then you might decide to add a spouse or employer record, which is NOT considered a constituent, and doesn't show up in most queries.  Notably, non-constituents aren't exported when using the Export tool and your base table is "Constituent".
22 1 Jon Goldberg
23 23 Jon Goldberg
h3. SQL
24
25 1 Jon Goldberg
If extracting directly from SQL, @SELECT * FROM RECORDS@.
26 21 Jon Goldberg
27 23 Jon Goldberg
Note that you can extract only constituents by adding @WHERE IS_CONSTITUENT = -1@.  For a Civi migration, I recommend importing all contacts.
28 21 Jon Goldberg
29 23 Jon Goldberg
h3. Export tool (NOTE: This ONLY gets constituents).
30
31 1 Jon Goldberg
Tab 1. General:
32
- Include all records.
33
- Head of Household processing: Export both constituents separately.
34
- Check all of the "Include these Constitutents": Inactive, deceased, no valid address
35
36
Tab 2: Output.
37
First, expand the "Constituent Information" in the left pane, and add every field to the export.  Do the export (as a CSV).
38 6 Jon Goldberg
39 3 Jon Goldberg
h3. Constituent Codes
40 15 Jon Goldberg
41 19 Jon Goldberg
In RE: Found at the bottom of the "Bio 2" tab.
42
In SQL: CONSTITUENT_CODES maps to "GroupContact".  TABLEENTRIES stores the codes ("groups").  In my case, @SELECT *  FROM [CCR_July_snapshot].[dbo].[TABLEENTRIES] WHERE [CODETABLESID] = 43@ did the trick.  YMMV - see "deciphering stored procedures" below.
43 3 Jon Goldberg
44 1 Jon Goldberg
Export as _one to many_, below.
45 3 Jon Goldberg
These map to "groups" in Civi - can also be mapped to "tags" if you don't need to track the begin/end date on them.
46
47
No need to export these fields:
48
System Record ID
49
Import ID
50 23 Jon Goldberg
As of Civi 4.4.6, there's no way to import Group Begin/End dates via API, you need to do it via direct SQL.
51 6 Jon Goldberg
52
h3. Solicit Codes
53
54
Export as _one to many_, below.
55
These can map to groups - but also may map to privacy preferences or custom fields (e.g. Email Only, Do Not Solicit)
56
Export the "Solicit Code" only (along with the Constituent's System Record ID, of course).
57 3 Jon Goldberg
58 20 Jon Goldberg
h3. Addresses
59
60
SQL tables: ADDRESS, CONSTIT_ADDRESS
61
62
Addresses are a many-to-many relationship in RE.
63 27 Jon Goldberg
Not all addresses in the database are visible in RE.  Addresses with a 1 or 7, for instance.  Make sure to look your data over and filter those out accordingly.
64 20 Jon Goldberg
65 25 Jon Goldberg
h3. Phones/E-mail/websites
66 1 Jon Goldberg
67 25 Jon Goldberg
RE is a children of the 90's, so a) phones are tied to addresses, not contacts, and b) e-mails and websites are a type of phone.
68
69 26 Jon Goldberg
Notes:
70
* You can NOT have duplicate phone types in RE, so no need to try and catch multiple "Home" numbers!
71
* Oh - except that one contact can have two home phone numbers on two different addresses.
72
* Don't forget to filter out duplicate numbers/e-mails/etc. when someone puts the same phone number on two different addresses.
73 22 Jon Goldberg
74
This SQL gets me a useful list of phones and e-mail for further processing in Kettle:
75
<pre>
76
SELECT DISTINCT
77
  CONSTITADDRESSID
78
, CONSTIT_ID
79
, PHONETYPEID
80
, CONSTIT_ADDRESS_PHONES."SEQUENCE"
81
, NUM
82
, DO_NOT_CALL
83
, TEXT_MSG
84
FROM CONSTIT_ADDRESS_PHONES
85
LEFT JOIN PHONES ON CONSTIT_ADDRESS_PHONES.PHONESID = PHONES.PHONESID
86
LEFT JOIN CONSTIT_ADDRESS ON CONSTITADDRESSID = CONSTIT_ADDRESS.ID
87
</pre>
88
89 9 Jon Goldberg
h3. Relationships
90
91 29 Jon Goldberg
Relevant SQL table: CONSTIT_RELATIONSHIPS
92
93 9 Jon Goldberg
Relationships are different in Civi and RE in the following significant ways:
94
* Relationships don't have to have a relationship type.
95 1 Jon Goldberg
* The A-B relationship doesn't have to have the same relationship type as B-A (e.g. if my relationship is "parent", the reciprocal relationship could be "son" or "daughter".
96 29 Jon Goldberg
* Related contacts need not have their own constituent record (though they can).  If they don't have their own constituent record, they nevertheless have a record in RECORDS, they're just not a constituent.
97 30 Jon Goldberg
* There need not be a relationship type at all.  This doesn't make sense, except that:
98
* There are hardcoded fields for IS_SPOUSE, HON_MEM_ACKNOWLEDGE, IS_HEADOFHOUSEHOLD, and SOFTCREDIT_GIFTS.
99
100 32 Jon Goldberg
Because relationships aren't necessarily reciprocal, I find it helpful to take my list of invalid relationships and do BOTH of the following:
101
* Look up the RELATIONSHIP_TYPE against the @name_b_a@ field in @civicrm_relationship_type@.
102
* Look up the RECIP_RELATIONSHIP_TYPE against both @name_a_b@ and @name_b_a@ in @civicrm_relationship_type@.
103 9 Jon Goldberg
104 10 Jon Goldberg
h3. Attributes
105
106
Attributes are the RE equivalent of custom fields.  However, unlike custom fields, they can also have a "date" value and a "comments" value.  While this can be replicated in Civi via multi-record custom field groups, ideally the data is evaluated attribute by attribute.
107
108 11 Jon Goldberg
Valuable information about the setup of the attributes is available in RE from *Config > Attributes*.
109 1 Jon Goldberg
110 33 Jon Goldberg
* The analogous field to @civicrm_custom_field@ is @AttributeTypes@.
111
* @AttributeTypes.CODETABLESID@ gives a lookup for the RE "option group" that contains valid options for that attribute.
112 37 Jon Goldberg
* All constituent attribute data is stored in the table @ConstituentAttributes@.  Note that it's stored in a Key-Value Pair-style table - you'll need to do a bunch of SQL queries, or run a Kettle "Row Denormaliser" step to get this data in order.
113
 
114 33 Jon Goldberg
Here's my preliminary SQL to export attributes from RE:
115
<pre>
116
SELECT
117 36 Jon Goldberg
ca.PARENTID as external_identifier
118
, ca.ATTRIBUTETYPESID
119
, at.DESCRIPTION as Category
120
, TABLEENTRIES.LONGDESCRIPTION as Description
121 33 Jon Goldberg
, TEXT
122
, NUM
123
, DATETIME
124
, CURRENCY
125
, "BOOLEAN"
126 35 Jon Goldberg
, COMMENTS
127 33 Jon Goldberg
, ca.ATTRIBUTEDATE
128
FROM ConstituentAttributes ca
129
JOIN AttributeTypes at ON ca.ATTRIBUTETYPESID = at.ATTRIBUTETYPESID
130 36 Jon Goldberg
LEFT JOIN TABLEENTRIES ON ca.TABLEENTRIESID = TABLEENTRIES.TABLEENTRIESID
131 33 Jon Goldberg
</pre>
132
133 34 Jon Goldberg
*note:*  In the SQL above, "PARENTID" and not "ConstitID" is the correct foreign key to link this to the contact.
134
135 38 Jon Goldberg
To get a list of option values out of RE for the attributes, use this SQL:
136
<pre>
137
SELECT
138
DESCRIPTION
139
, at.CODETABLESID
140
, LONGDESCRIPTION
141
FROM TABLEENTRIES te 
142
LEFT JOIN AttributeTypes at ON te.CODETABLESID = at.CODETABLESID
143
ORDER BY DESCRIPTION
144
</pre>
145
146 39 Jon Goldberg
Attributes can be multi-record custom fields by their nature, so you have to account for that.  Here's some alpha-grade SQL for sussing out which fields have multi-record custom fields:
147
<pre>
148
SELECT ATTRIBUTETYPESID, PARENTID, COUNT(LONGDESCRIPTION)
149
FROM ConstituentAttributes ca
150
JOIN TABLEENTRIES te ON ca.TABLEENTRIESID = te.TABLEENTRIESID
151
GROUP BY PARENTID, ATTRIBUTETYPESID
152
HAVING COUNT(LONGDESCRIPTION) > 1
153
ORDER BY ATTRIBUTETYPESID
154
</pre>
155
156 38 Jon Goldberg
*note:*  In Civi 4.5+, you could conceivable use "EntityRef" functionality to facilitate chained selects of OptionValue lists.  That would let you create a multi-record custom field group that would very closely map how Attributes work in RE - but you'd have all the disadvantages of multi-record custom fields.
157 10 Jon Goldberg
158 3 Jon Goldberg
h3. Other constituent tables:
159 5 Jon Goldberg
160 2 Jon Goldberg
Skip these tables:
161
* Spouse
162
* Gifts
163
* First Gift, Last gift, Largest Gift
164
* Actions
165 1 Jon Goldberg
* First Action, Last Action
166
* Summary Information
167
168 41 Jon Goldberg
h2. Contribution-related exports
169
170
h3. Contributions/Gifts
171
172
Contributions (in RE parlance: Gifts) are complicated beasts!
173
174
Here are some relevant database tables and their equivalent in Civi:
175
GIFT	civicrm_contribution
176
GiftSplit	civicrm_line_item
177
CAMPAIGN	Roughly maps to Campaign.  Your mapping may vary and/or include custom fields.
178
APPEAL	Also roughly maps to Campaign (or Source).  Your mapping may vary and/or include custom fields.
179
FUND	Roughly maps to Financial Type.  Your mapping may vary and/or include custom fields.
180
181
Note that gift type is hardcoded into a function called "TranslateGiftType) - so you may want to include that function in your SQL, e.g.:
182
<pre>
183
SELECT
184
gs.GiftId
185
, g.CONSTIT_ID
186
, gs.Amount
187
, g.DTE as gift_date
188
, FUND.DESCRIPTION as fund
189
, CAMPAIGN.DESCRIPTION as campaign
190
, APPEAL.DESCRIPTION as appeal
191
, g.PAYMENT_TYPE
192
, g.ACKNOWLEDGE_FLAG
193
, g.CHECK_NUMBER
194
, g.CHECK_DATE
195
, g.BATCH_NUMBER
196
, g.ANONYMOUS
197
, gst.LONGDESCRIPTION as giftsubtype
198
, g.TYPE
199
, DBO.TranslateGiftType(g.TYPE) as type2
200
FROM GiftSplit gs
201
LEFT JOIN FUND on gs.FundId = FUND.id
202
LEFT JOIN APPEAL on gs.AppealId = APPEAL.id
203
LEFT JOIN CAMPAIGN on gs.CampaignId = CAMPAIGN.id 
204
LEFT JOIN GIFT g on gs.GiftId = g.ID
205
LEFT JOIN TABLEENTRIES gst on g.GIFTSUBTYPE = gst.TABLEENTRIESID
206
</pre>
207
208 42 Jon Goldberg
Payment Type is also hard-coded, it seems:
209
1	Cash
210
2	Personal Check
211
3	Business Check
212
4	Credit Card
213
6	Direct Debit
214
8	Other
215
216
h3. Soft Credits
217
218
Stored in GIFTSOFTCREDIT.  RE does NOT have the concept of a soft credit type - which is fine.
219
<pre>
220
SELECT
221
, GiftId
222
, ConstitId
223
, Amount
224
, 'Soft Credit' as soft_credit_type
225
FROM GiftSoftCredit
226
</pre>
227
228
h3. Solicitor
229
230
I imported these as soft credits, but a different TYPE of soft credit.  Here's the SQL I used to get the data out of RE:
231
<pre>
232
SELECT
233
ParentId as gift_id
234
, SolicitorId as soft_creditee_external_identifier
235
, Amount
236
, 'Solicitor' as soft_credit_type
237
FROM GiftSolicitor
238
</pre>
239
240 41 Jon Goldberg
h3. In Honor/Memorial Of (aka Tributes)
241
242
As of CiviCRM 4.5, In Honor/Memorial of is considered a form of soft credit.  In RE, they're still separate, and are called Tributes.  The structure is a little more complex - the table structure is Constituent <-> Tribute <-> Gift_Tribute <-> Gift.  Civi is Contact <-> Soft Credit <-> Contribution.  
243
244
Here is some preliminary SQL that pulls tribute data suitable for transformation and import to Civi as ContributionSoft entities.  Note that CiviCRM doesn't have a concept of a "Description" but does have the concept of a PCP Note, so I'm importing the description there - in the future, I could see the argument for Civi exposing the PCP Note as a description.
245
246
<pre>
247
SELECT
248
gt.GIFT_ID
249
, gt.TRIBUTE_TYPE
250
, t.DESCRIPTION
251
, t.RECORDS_ID as tributee_extenal_identifier
252
, te.LONGDESCRIPTION as tribute_type
253
FROM GIFT_TRIBUTE gt
254
JOIN TRIBUTE t ON gt.TRIBUTE_ID = t.ID
255
LEFT JOIN TABLEENTRIES te on gt.TRIBUTE_TYPE = te.TABLEENTRIESID
256
</pre>
257
258 43 Jon Goldberg
h2. And More
259
260 7 Jon Goldberg
h3. Tables that Civi doesn't have a direct counterpart for
261 5 Jon Goldberg
262 3 Jon Goldberg
* Aliases (stores Maiden Name and d/b/a - unsure how to import into Civi just yet)
263 7 Jon Goldberg
* Solicitor Goals - Can be found on an RE contact record on "Bio 1" tab by clicking "Details" next to "Is a Solicitor" checkbox.  Don't know how to use them.
264 2 Jon Goldberg
265
266
Open each CSV file in Excel or similar.  Sort each field by ascending AND descending to see if any data is stored in that field.  If every record has no data or the same data, delete it - it's not being tracked in the current system.  If you see only one or two records with a particular field, they're also probably fine to go, but check with the client first.
267
268 1 Jon Goldberg
269
Next, strip out all of the constituent information except for primary/foreign keys.  I like to keep in First/Middle/Last name just for human readability though.  So leave in those three fields, plus any field with the word "ID" in it.  This is your base constituent info, and will be in every other export you do.
270
271
Now comes the fun part!  Export each table, one at a time, by adding those fields to an export that already includes the base constituent info.
272
273
For one-to-many relationships, the system will ask you how many instances of the information to export.  I default to 12, then look over the data to see how many are actually used, then re-export with a higher or lower number.
274
275
I also remove records that don't contain the relevant data.  For instance, when exporting Solicit Codes, I sort by the first Solicit Code.  Then I scroll down past the folks that have Solicit Codes to those who have none, and delete the rows for folks who have none.
276
277
Note that for simplicity's sake, RE contains many views of the tables that, if you export them all, you'll have redundant data.  There's no need to export "First Gift", "Last Gift", or "Largest Gift" - simply export all gifts.  Likewise for "Preferred Address".
278
279
When exporting one-to-many tables that themselves contain one-to-many tables (e.g. Addresses contains Phones), do NOT select 12 of each!  That means you're exporting 144 phone numbers per record.  First determine the maximum number of addresses being tracked, re-export with that number, THEN export with phone numbers.  Also, it's reasonable to export with 5 phone numbers per address.
280
281
NOTE: Letters sent is incomplete, there's more than 12 letters to some folks!
282
283
GIFTS is related to constituent on the last column (Constituent System Record ID)
284 8 Jon Goldberg
285 13 Jon Goldberg
h3. Code Tables/Option Groups/Option Values
286
287 17 Jon Goldberg
If you're extracting data from the SQL back-end, you'll see that the RE equivalent to Civi option groups is "code tables".  There's two functions that handle lookups: dbo.GetTableEntryDescription and dbo.GetTableEntryDescSlim.  To determine where the data is being accessed by the function, see "Deciphering MS SQL", below.  Use the "lTableNumber" passed to those functions and you'll find your data in dbo.CODETABLES (comparable to civicrm_option_group), dbo.CODETABLEMAP and dbo.TABLEENTRIES (comparable to civicrm_option_value).
288
289
h2. Deciphering MS SQL
290
291
SQL Server Profiler is a tool that lets you spy on SQL statements passed to MS SQL, which is good for determining where certain data lives.  However, RE depends on functions and stored procedures, so sometimes the SQL won't tell you exactly where to look.
292
293
h3. Looking Up Functions
294
295
These are embedded in SQL and have a nomenclature like: dbo.GetTableEntryDescSlim. Find them in SQL Server Management Studio: database > Programmability > Functions > Scalar-valued Functions.
296
297
h3. Looking Up Stored Procedures
298
299 18 Jon Goldberg
If, in the profiler, taking a certain action shows a command like this:
300 17 Jon Goldberg
These have a syntax like:
301 1 Jon Goldberg
<pre>
302 18 Jon Goldberg
exec sp_execute 48,43,'Acknowledgee'
303 1 Jon Goldberg
</pre>
304
305 18 Jon Goldberg
You're dealing with a stored procedure.  You need to find the corresponding @exec sp_prepexec@ command (in this case, the one with a 48).  In this case, it looks like:
306
<pre>
307
declare @p1 int
308
set @p1=48
309
exec sp_prepexec @p1 output,N'@P1 int,@P2 varchar(255)',N'SELECT  Top 1 TABLEENTRIESID  FROM DBO.TABLEENTRIES WHERE CODETABLESID = @P1 AND LONGDESCRIPTION = @P2  ',43,'Acknowledgee'
310
select @p1
311
</pre>
312
313 40 Jon Goldberg
Note that there's a tool called "SQL Hunting Dog", a free plug-in for SQL Server Management Studio, which makes locating stored procedures, etc. easier.
314 17 Jon Goldberg
315 13 Jon Goldberg
316 14 Jon Goldberg
h3. Addressee/Postal Greeting/E-mail greeting
317
318
RE has a much wider variety of greeting formats out-of-the-box.  The "spouse ID" is stored on the record to enable quick lookups of addressee greetings that include the spouse.
319
320 8 Jon Goldberg
See also:
321
http://support.littlegreenlight.com/kb/migration/migrating-from-the-raisers-edge-to-lgl
322 14 Jon Goldberg
323
h3. Things I see that RE does better than Civi:
324
325
* Better greetings/salutations UI out of the box.  In Civi, you must in-line edit the greetings, then press "Edit" next to the greetings, and even then you only see the tokens you'll use.  RE lets you edit with no clicks, and parses the tokens for you.
326
* The equivalent of option values are stored with their id, not their value.  This isn't a big deal, but it DOES make data transformation easier in RE, and I suspect it makes their equivalent of pseudoconstant code easier to read.
327 28 Jon Goldberg
* There's a lot more data stored in many-to-many tables.  For instance, job titles are stored in the relationship tab, reflecting the fact that someone can have more than one job.
Go to top