[mjohnson]

David,

That is a valid point about searching on the import IDs. Our idea is to still use the Constituent ID as a way to track people through Raisers Edge. If the constituent ID ever changes in Raisers, an update process would change it in the 3rd party system. The same goes for the reverse. That way the records would always be linked up through the import ID, invisible to the user.

Part of the update process will check for the last update date in both systems and move the data accordingly.

To the point about duplicate constituent IDs, we plan on moving all the data over to the 3rd party system; and for new ID's in the 3rd party system start it with a new series numeral or letter that would be independent of what is currently in Raisers Edge. That way when the update process occurs across both systems there will not be a duplicate ID error.

At the same time new people are created a duplicate person process will take place to make sure they are not already in the system.

Thanks for your ideas!

- Matt