Salesforce technology supporting the nonprofit sector has evolved greatly during my 10 years within the … Continue Reading
In an effort to keep up with the ever-changing landscape of technology, nearly every nonprofit … Continue Reading
The purpose of this eBook is to share lessons learned and recommendations for best practices as you move forward with your implementation. These recommendations are not intended to be Salesforce specific, but are rather globally applicable recommendations for the implementation of any new technology tool.
You’re moving from your legacy system to Salesforce. You’ve collected a lot of data over the years, but do you need to keep it all? We explore how and what you should migrate.
Making the move from a legacy system, like Raiser’s Edge? We have shared tips and tools to help you relieve the pain that many face during their data migration to Salesforce.
The Notes & Attachments related list is on the way out. Content Notes and Files will replace these features, and both have major advantages over the “old” notes and attachments. The biggest difference is enhanced sharing for both, and rich text for notes.
You’re ready for the data migration, but now it’s time to manage the data freeze. Here are some tips to work through shutting down your old system and starting up your new system.
A data map is a great way to document the process of uncovering the secrets of a data set. We use them for so many different reasons. To take a catalogue of what is in the old system. To take another catalogue of all the fields that are in the new system. To show a client where all their data is going and how.
It doesn’t matter if8ixn547AT you have 100 records or 1 million records, the data import phase of a project can seem like a daunting task. It’s kind of like moving a 5 bedroom house. There’s extracting the data from your old system, or gathering it from various places it may live. There’s prepping it for import by removing duplicates and making sure that email and phone number fields are formatted properly. And let’s not forget figuring out what pieces of data you actually want to bring over into the new system. Once these steps are completed, along comes the biggest piece – actually importing the data. This is either done by someone within your organization or by an outside consultant. A variety of tools are used, some magic is performed and then you have a new system with data that looks familiar to you.