Conversion Conversation
When considering data conversion from an old system into FundRaiser, there are opportunites to re-think your use of the data you store, and even what data are relevant to your fundraising efforts. If you take some time to learn more about how FundRaiser stores and uses information, for instance, you'll have a better understanding of how your data can best be "ported" over to the new system. For this reason, I recommend taking the time for training, even before initiating conversion processes.
Overview
The FundRaiser Overview class is available in both video form and as a live webinar which does not count against training credits. While most live classes require one credit per class (no matter the number of attendees you have for that class), the Overview can be attended multiple times, if needed, at no cost of credits. The Overview serves multiple purposes, in that you learn some simple data entry (entring name and gift information), as well as the general layout of the program, and some of the broader points regarding codes as they are used in FundRaiser. Another purpose of the Overview class is to give you a better idea of which other classes you may want to attend (or view, in the case of the videos). There is no "set" order for viewing, so it becomes a matter of what your priorites are, and what you feel you need to learn, and when.
A rose by any other name...
Nomenclature... What we call things. How we use terms. Everyone seems to have a slightly different interpretation of many of the words we use in the non-profit fundraising world. What does "active" or "inactive" really mean? Is it a code, or an attribute, or a flag, or a "blix"? Learning how terms are used in FundRaiser, and relating them to how YOU use those same terms, will be invaluable as you begin the process of switching from another system, since no two systems speak exactly the same language, and the Overview class will help you get familiar with many of these terms. Groupings are queries, or gatherings of records that have one or more things in common. Codes are nothing more than unique identifiers, although some are attached to name records, and some to gift records, and others exist, too, although less important than name/gift codes. Are they "thank you" letters, or receipts, or gift acknowledgements? Is it a promist to pay, or a pledge? And so it goes...
GIGO: Garbage In, Garbage Out
Before any data conversion, you'll want to make certain that only pertinent data is converted, and that the existing data is as clean as possible to make the conversion easier to explain. For instance, let's say that one field of information in your old system held several possible "attributes" per name record. Maybe it holds descriptors that are important to you, such as "parent, grandparent, senior citizen, volunteer", or "dog, cat, gerbil, other", or "newsletter, do not solicit, email only, no phone calls", etc. Any one name could have multiple words in that single field, but when converting those to FundRaiser, you might want each descriptor pulled out as a unique code, like a Category code. Some might be better set as "preferences", or even as user-defined "Exclusions". Knowing how these things are handled in FundRaiser can help you understand how to get them converted, and will make for a "cleaner" transition, so that you end up with clean, usable, and distinct data.
"You can observe a lot by watching" - Yogi Berra
There are several videos available in the CUstomer Portal section of our website, including the Overview, and you will save a lot of time and frustration in the long run by viewing most of them. In particular, Coding will lay the groundwork for how FundRaiser helps you to uniquely identify people and gifts; Groupings will show how easy it is to segment your entire database according to your specific criteria; and Households wan help you decide whether or not you even need that feature activated. The more you learn, up front, the easier it will be to identify for yourselves, and for the programmer doing your data conversion, what information needs to be moved, and HOW it needs to be moved. Take time to save time.