Exporting Salsa for CiviCRM » History » Version 29
Jon Goldberg, 01/21/2015 04:35 PM
1 | 24 | Jon Goldberg | {{lastupdated_at}} by {{lastupdated_by}} |
---|---|---|---|
2 | |||
3 | 1 | Jon Goldberg | h1. Exporting Salsa for CiviCRM |
4 | |||
5 | 2 | Jon Goldberg | When logged in as a Manager, "Query/Export" will give you a full export of contact data. There's a "Select My Entire List" button. There's also an "include my deleted supporters" checkbox, which you may want to check (but probably not). This will NOT get you groups/tags. |
6 | 1 | Jon Goldberg | |
7 | 14 | Jon Goldberg | h2. Exporting Data not on the Contact Entity |
8 | 2 | Jon Goldberg | |
9 | 25 | Jon Goldberg | You need to get to custom reports. If you have the Reports tab, great; if not, you can get there by clicking "Supporter Management" tab, then "Built-in Reports", then "Clone and Edit" a report, then select "List Your Custom Reports". Or go straight here: https://hq-org.salsalabs.com/dia/hq/reports/list.jsp?table=report |
10 | 1 | Jon Goldberg | |
11 | 8 | Jon Goldberg | *Important*: When selecting foreign keys (e.g. "Supporter KEY") from the Columns tab, be sure to give a custom label. This will cause the key to display correctly, instead of giving a link to the supporter's record. |
12 | |||
13 | 11 | Jon Goldberg | h3. Groups |
14 | 12 | Jon Goldberg | |
15 | 3 | Jon Goldberg | * Create a new report. |
16 | * Select the type of report you would like to create: Standard report |
||
17 | * Use "Advanced Object Chooser". |
||
18 | 9 | Jon Goldberg | * Report "Supporter Groups", then "Groups". Press "Save". |
19 | 1 | Jon Goldberg | * Select the "Columns" tab and select your columns. I like just "Supporter Key" and "Group Name". |
20 | 7 | Jon Goldberg | * In Conditions, "Group Name" should be "Not Empty". |
21 | 4 | Jon Goldberg | * Save, Run the report. |
22 | * Click the "Export" link. |
||
23 | 1 | Jon Goldberg | |
24 | 11 | Jon Goldberg | h3. Tags |
25 | 12 | Jon Goldberg | |
26 | 5 | Jon Goldberg | * Create a new report. |
27 | * Select the type of report you would like to create: Standard report |
||
28 | * Use "Advanced Object Chooser". |
||
29 | * Report on "Tags", then "Tags Data", then "Database Table". Press "Save". |
||
30 | * Select the "Columns" tab and select your columns. I like just "Tag" and "Table Key". |
||
31 | 1 | Jon Goldberg | ** "Table Key" is the Supporter Key. It's similar to "entity_id" in CiviCRM. |
32 | 7 | Jon Goldberg | * In "Conditions", "Table Name" should equal "supporter". |
33 | 10 | Jon Goldberg | * Add another condition: "Tag.Tag" is "Not Empty". |
34 | 1 | Jon Goldberg | * Save, Run the report. |
35 | * Click the "Export" link. |
||
36 | |||
37 | 11 | Jon Goldberg | h3. Events |
38 | 1 | Jon Goldberg | |
39 | 15 | Jon Goldberg | As above, but no conditions, and report on the "Event" table. If you're only importing legacy events, this is a good list of easy fields to import: |
40 | Event KEY |
||
41 | Reference Name |
||
42 | Event Name |
||
43 | Description |
||
44 | Start |
||
45 | End |
||
46 | Deadline |
||
47 | Maximum Attendees |
||
48 | |||
49 | 1 | Jon Goldberg | h3. Participants |
50 | 16 | Jon Goldberg | |
51 | As above. Report on tables "Supporter Event", then "Event". Note that there are a lot of tables that _look_ like "Supporter Event", like "Supporterevent" and "Supporter Events"! |
||
52 | |||
53 | Note that if you're matching on a unique field from "Events", you can just export "Supporter Event" and not the "Event" table. |
||
54 | Here are the fields I exported and what I matched them to: |
||
55 | Supporter KEY external_identifier |
||
56 | Event KEY event_key |
||
57 | Status status |
||
58 | Type role |
||
59 | Date Created register_date |
||
60 | |||
61 | 28 | Jon Goldberg | h3. Recurring Donations |
62 | |||
63 | Export on table "Recurring Donation". Here's the field mapping: |
||
64 | |||
65 | Recurring Donation Key -> trxn_id |
||
66 | Supporter Key -> external_identifier |
||
67 | Transaction date -> create_date |
||
68 | Start Date -> start_date |
||
69 | RPREF -> invoice_id |
||
70 | RESULT (exclude 37, they're tests) |
||
71 | Amount -> amount |
||
72 | Pay Period -> use to remap to frequency_unit and frequency_interval |
||
73 | TERM -> installments |
||
74 | Status(?) |
||
75 | |||
76 | Note that in Salsa, there's no clear-cut way to tell whether a contact's recurring donation is still working or not - "Status" isn't a complete indicator, and thus doesn't cleanly map into Civi. |
||
77 | |||
78 | 27 | Jon Goldberg | h3. Donations |
79 | |||
80 | It's important to link the recurring donations to the donations when exporting if you need to identify the first recurring donation (e.g. to generate thank-you letters if it's a first donation and recurring). |
||
81 | |||
82 | 29 | Jon Goldberg | Export on table "Donation" linked to table "Donate Page". You'll want these fields (more or less): |
83 | 27 | Jon Goldberg | |
84 | Donation.donation KEY(donation) |
||
85 | 1 | Jon Goldberg | Donation.supporter KEY(donation) |
86 | 29 | Jon Goldberg | donate_page.Reference_Name |
87 | Donation.Date_Entered |
||
88 | 27 | Jon Goldberg | Donation.Transaction Date(donation) |
89 | 1 | Jon Goldberg | Donation.amount(donation) |
90 | 27 | Jon Goldberg | Donation.Transaction Type(donation) |
91 | Donation.RESULT(donation) |
||
92 | Donation.Tracking Code(donation) |
||
93 | 29 | Jon Goldberg | Donation.Designation Code(donation) |
94 | 1 | Jon Goldberg | Donation.In Honor Name(donation) |
95 | 27 | Jon Goldberg | Donation.In Honor Email(donation) |
96 | Donation.In Honor Address(donation) |
||
97 | 1 | Jon Goldberg | Recurring donation.Transaction Date(recurring_donation) |
98 | 29 | Jon Goldberg | Donation.Order_Info |
99 | 27 | Jon Goldberg | |
100 | 19 | Jon Goldberg | h3. Actions |
101 | 17 | Jon Goldberg | |
102 | 19 | Jon Goldberg | Salsa has a separate table for actions, making them structurally comparable to Civi Events. A good match in Civi is the Survey entity, which is used for petitions. |
103 | 1 | Jon Goldberg | |
104 | 19 | Jon Goldberg | Export as above. Report on table "Action". |
105 | Condition: "Reference Name" is not empty. |
||
106 | |||
107 | *Note*: "Description" is likely to contain HTML that breaks the export. I find it helpful to export it as the last column. |
||
108 | |||
109 | h3. Supporter_Actions |
||
110 | 11 | Jon Goldberg | |
111 | 22 | Jon Goldberg | Export "action" and "supporter_action" and "supporter_action_comment" in that order. |
112 | 23 | Jon Goldberg | Condition: supporter_key IS NOT NULL |
113 | 20 | Jon Goldberg | |
114 | Here's the fields I grabbed with their mapping: |
||
115 | 22 | Jon Goldberg | supporter_action.supporter_key |
116 | 21 | Jon Goldberg | action.Reference Name |
117 | 22 | Jon Goldberg | supporter_action.Date_Created |
118 | supporter_action_comment.Comment details |
||
119 | 20 | Jon Goldberg | |
120 | 11 | Jon Goldberg | h3. Chapters |
121 | 12 | Jon Goldberg | |
122 | 7 | Jon Goldberg | * Create a new report. |
123 | 1 | Jon Goldberg | * Select the type of report you would like to create: Standard report |
124 | 7 | Jon Goldberg | * Use "Advanced Object Chooser". |
125 | 8 | Jon Goldberg | * Report "Supporter Chapter", then "Chapter". Press "Save". |
126 | * Select the "Columns" tab and select your columns. I like just "Supporter KEY" and "Chapter.Name". |
||
127 | * In Conditions, "Chapter.Name" should be "Not Empty". |
||
128 | 5 | Jon Goldberg | * Save, Run the report. |
129 | 1 | Jon Goldberg | * Click the "Export" link. |
130 | |||
131 | 7 | Jon Goldberg | h3. Receive_Email field |
132 | 1 | Jon Goldberg | |
133 | Here's a TSV of how to interpret the "Receive_Email" field. |
||
134 | 26 | Jon Goldberg | |*code*|*meaning*| |
135 | |-24|INACTIVE: (5.1.1 User Unknown)| |
||
136 | |-26|INACTIVE: Address contains RFC spec. invalid characters / is improperly formatted| |
||
137 | |-3|INACTIVE: UNSUBSCRIBED (actively unsubscribed by user)| |
||
138 | |-30|INACTIVE (Reported as Spam): Other Blacklist (BLACKLIST)| |
||
139 | |-32|(Unknown Status)| |
||
140 | |-35|INACTIVE (Reported as Spam): Outblaze| |
||
141 | |-4|(Unknown Status)| |
||
142 | |-42|INACTIVE (Recipient Initiated Spam Report): MSN/Hotmail/WebTV| |
||
143 | |-44|INACTIVE (Recipient Initiated Spam Report): UNTI (Juno/NetZero/FreeServers)| |
||
144 | |-45|INACTIVE (Recipient Initiated Spam Report): Yahoo| |
||
145 | |-46|INACTIVE (Recipient Initiated Spam Report): Comcast.net| |
||
146 | |-47|INACTIVE (Recipient Initiated Spam Report): AOL| |
||
147 | |-48|INACTIVE (Recipient Initiated Spam Report): RoadRunner| |
||
148 | |-50|ISP Specific Bounces: AIM.com Unactivated account| |
||
149 | |-51|INACTIVE (Recipient Initiated Spam Report): Excite| |
||
150 | |-52|INACTIVE (Reported as Spam): Earthlink| |
||
151 | |-53|(Unknown Status)| |
||
152 | |-54|(Unknown Status)| |
||
153 | |-60|Bad Address/Expired address, etc (n.b.: These addresses are all @democracyinaction.org)| |
||
154 | |-9|INACTIVE: DEATH (supporter has died)| |
||
155 | |0|0 - Inactive or Unknown(not subscribed)| |
||
156 | |1|1 - Imported or unknown (subscribed)| |
||
157 | |10|ACTIVE: CONFIRMED (Double opt-in)| |
||
158 | |3|ACTIVE: CLIENT (Client has directly signed up)| |