I have a question in regards to prospects and the Constituent Import.
Are you currently using this function in Tessitura? If so what has your experience been with it? My concern is that there is no way to back out this import if there is an error takes place. Eventhough there is a validation report.
We use it a lot - and have no problem with it at all.
We make sure that whoever wants the import to happen fills in the data in an Excel Spreadsheet that we send them that has all the columns in the correct order. We then do a visual check of the data - just to spot any glaring errors.
We will then always run the procedure in Review in our Test system first to check the data. We will sometimes also run the import fully in Test so we can check the data there (especially if there are a large number of records that are being imported).
Caryl
I use the utility several times a month importing lists for various organizations and departments in our consortium. I have a formatted spreadsheet that they put the data into so everything is in the correct order for the import. I spot check formatting and edit as needed or will return to the user for them to edit appropriately. I run in review mode first before doing the actual import. I’ve never had any issues with the utility. There are usually several lines that don’t import because of being identified as potential duplicates (a feature I like). I print out the report and give to the person requesting the import so they are aware of what names were already in the database.
Teresa
From: Tessitura Marketing Forum [mailto:forums-marketing@tessituranetwork.com] On Behalf Of Robert Taulty Sent: Monday, October 26, 2009 10:45 AM To: Teresa Dean Subject: [Tessitura Marketing Forum] Consitituent Import
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Marketing Forum. You may reply to this message to post to the Marketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Here in the Sydney UCSS consortium, we have a custom version (based on the canned version) that will import data into the LT_TKT_HIS table - it also deduplicates on the way in.
We have a very clearly defined set of data entry standards that all consortium members have agreed to adhere to. As the person who does the importing here at the ACO, I spend a reasonable amount of time ensuring that the data to be imported also adheres to these guidelines so that the data to be imported will properly be deduplicated with the data already in the database. I cannot stress how important and useful this is!
Martin
Something to keep in mind (unless this has changed in v9) is that the constituent import doesn't call lp_customer_rank, so if you have anything set to run using lp_customer_rank when you create an account it will not happen with the imported constituents.
I've just started experimenting with it. It certainly beats manually entering names and addresses! There are a few limitations, but you can get around them with SQL scripts:
1. It doesn't add any marketing restrictions, so if you're in the habit of adding marketing restrictions (phone, email, mail) to records, you'll need to go back and add that after they've been put in.
2. The only way to distinguish the new people is either a) they show up on the TW_CONSTITUENT_IMPORT table or b) you create a unique Original Source for them before you import them. It'd be nice if you could add a Constituent or Attribute to them on the way in, but that feature isn't there currently.
3. One other limitation - at least according to the documentation - is that it won't import people with blank states. Doesn't matter in the US or Australia, but it might be an issue for folks in New Zealand or other countries of the world.
However, I prefer the system you all have where you get someone else to put the data in the right columns before they give it to you . . .