|
Renee,
My clients
have used three options:
The least
technical one is to institute a set of rules stating that one database is the
"corporate" database. It's the one that will be used for all
mailings. All address changes must be entered there, and when there's a
conflict, that database is presumed to be the accurate one.
The next
option is to maintain separate databases but build bridges between them.
Changes made in one database (which might still be the corporate database) are
synchronized with the others. Again, you'll need a good set of rules to
keep the sync process from deleting good data.
The third
option is to replace your various databases with one system that does it
all. In addition to selecting and converting to the system, you'll need to
develop policies about how departments share data. In a shared system, one
department can change contact info that another believes is correct. These
are the mirror images of the policies you need for the first
option.
Robert
__________________________
Robert L. Weiner Consulting
Providing Strategic Technology
Consulting to Nonprofits and Education
San Francisco,
CA
415/643-8955
www.rlweiner.com
--- You are currently subscribed to mcn_mcn-l as: [email protected] To unsubscribe send a blank email to [email protected] |
- Donor Information Maintenance Montgomery, Renee
- Re: Donor Information Maintenance Robert Weiner
- Re: Donor Information Maintenance Chuck Patch
- Re: Donor Information Maintenance James Landrum
