Many organizations and, particularly, the people responsible for donor information management make a critical error when it comes to planning for the conversion. Beyond the due-diligence that it is so reasonable to execute on the new product's functionality, cost, stability, flexibilty, ease of use and learning, lies a whole other due-diligence arena and a large trap.
The oft-ignored due diligence I refer to is that which examines both the inputs required and outputs produced by your new software and how that can impact your work processes. It means evaluating your work processes to see if the new tool will make it easier to achieve the same outcomes by altering that work process. Often, new tools deliver opportunities to shorten time and effort cycles, eliminate paper-churn, and deliver better, i.e. more meaningful data. But it doesn't stop there. Sometimes you'll discover some work processes are simply no longer necessary at all!
This process is very hard to do, without doubt. At the least, you will be talking "scared cows" based on the "we always did it this way" mentality. At worst, you may be diminishing the very need for a perosn to be employed, ala "work obsolescence". Still, this absolutely should be done to maximize the benefit of conversion for your organization. But there is one more caution in this tale: The Trap.
The Trap is so easy to fall into when evaulating new fundraising software for purchase. And the danger doesn't diminish even after the decision is made and you are in the thick of conversion. The Trap is the difficulty we have in separating out the functionality we formerly had from the intent of the process or outcomes it was supposed to help us achieve.
Let me cite a hard example: The user facing conversion says "We need these four fields labeled MA, MB, MC and MD, each with a pull-down menu of 8 possible values." If you step back from that statement to understand that all that "machination" was just directed to handle a simple mailing function that depended on past donor behavior, then you get to the crux of the matter. The former system "forced" the user to hardcode highly variable information in order to "track" that behavior. Maybe your new tool can streamline that whole process, eliminate that coding ritual (time-waster) and deliver better related results reporting to boot. The lesson: Don't let past processes blind you to opportunities for process improvement.
The total benefits accruing from conversion are up to you.