Exporting Salsa for CiviCRM

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.

Exporting Data not on the Contact Entity

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 Custom Groups". Or go straight here: https://hq-org.salsalabs.com/dia/hq/reports/list.jsp?table=report

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.

Groups

Tags

Events

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:
Event KEY
Reference Name
Event Name
Description
Start
End
Deadline
Maximum Attendees

Participants

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"!

Note that if you're matching on a unique field from "Events", you can just export "Supporter Event" and not the "Event" table.
Here are the fields I exported and what I matched them to:
Supporter KEY external_identifier
Event KEY event_key
Status status
Type role
Date Created register_date

Activities (aka "Actions")

Salsa has a separate table for actions, making them structurally more comparable to Civi events than Civi activities. Supporters are joined via a many-to-many relationship to the action (supporter, supporter_action, supporter). In a more full-featured import, surveys and petitions are also a good potential place to import actions.

Export as above. Report on tables "Supporter action", then "Action"

Chapters

Receive_Email field

Here's a TSV of how to interpret the "Receive_Email" field.
code # of records meaning
-24 11066 INACTIVE: (5.1.1 User Unknown)
-26 1265 INACTIVE: Address contains RFC spec. invalid characters / is improperly formatted
-3 10596 INACTIVE: UNSUBSCRIBED (actively unsubscribed by user)
-30 8 INACTIVE (Reported as Spam): Other Blacklist (BLACKLIST)
-32 11 (Unknown Status)
-35 1 INACTIVE (Reported as Spam): Outblaze
-4 1 (Unknown Status)
-42 349 INACTIVE (Recipient Initiated Spam Report): MSN/Hotmail/WebTV
-44 10 INACTIVE (Recipient Initiated Spam Report): UNTI (Juno/NetZero/FreeServers)
-45 818 INACTIVE (Recipient Initiated Spam Report): Yahoo
-46 69 INACTIVE (Recipient Initiated Spam Report): Comcast.net
-47 545 INACTIVE (Recipient Initiated Spam Report): AOL
-48 1 INACTIVE (Recipient Initiated Spam Report): RoadRunner
-50 10 ISP Specific Bounces: AIM.com Unactivated account
-51 3 INACTIVE (Recipient Initiated Spam Report): Excite
-52 18 INACTIVE (Reported as Spam): Earthlink
-53 15 (Unknown Status)
-54 1 (Unknown Status)
-60 4 Bad Address/Expired address, etc (n.b.: These addresses are all @democracyinaction.org)
-9 5 INACTIVE: DEATH (supporter has died)
0 1101 0 - Inactive or Unknown(not subscribed)
1 64352 1 - Imported or unknown (subscribed)
10 3 ACTIVE: CONFIRMED (Double opt-in)
3 8924 ACTIVE: CLIENT (Client has directly signed up)