ebase migration to Salesforce.com
Last Updated on Wednesday, 4 March 2009 05:38 Written by Steve Friday, 17 March 2006 10:09
ebase is a desktop database for tracking members and supporters of a nonprofit. It was built back in the day in Filemaker, a database application akin to Microsoft Access. I’ve had the pleasure of doing two ebase migrations to Salesforce.com, and what follows is a quick list of my thoughts on the matter. If you have ebase (1.x), and want to move to Salesforce.com, hopefully this will be helpful:
I first set up an Access database, as I find it pretty easy/quick to work with.
Ebase has a table called names. Each row in the table is a household of up to two people. Contact information is on this row. There are lots of fields in the table (200+) just find the ones you care about.
Export the names table to excel, and import it to access. You now have a table with one row per household. Grab all the fields and export it to excel, then import it to salesforce.com with the Sforce Data Loader, mapping only the household fields to the household object in salesforce.com. This next step is importnatReimport the
Use the names table id field as a unique identifier for the household. When you migrate, you’ll have to break the two contacts on the one record in the names table into two. Make sure each of them has the household id (you’ll want that to associate them with the household later) and give them each a unique contact id.
Ebase has a table called payments. This is a list of all membership payments and gift payments related to the member/donor in the
Membership migration
Find all the eligible membership payments
* query for all membership record type
* drop out anything weird, like monthly payments
Get the last membership payment for each Contact
* run a contact role opp report, only show primary roles, get opp id, contact id, account id
* drop out previous payments
Create new membership opps 1 year out from Last Opp
* new name with new year
* set stage to some form of open
* set record type correctly
Create contact roles
* use result from import