Check out the Brochure (PDF) for a high-level summary.
Watch a video of the installation here
Once you've purchased the customization, unzip the downloaded file.
Inside, you will find a bbappfx folder, and under that, more folders with the same file structure as your Blackbaud CRM server.
Simply copy the \bbappfx\ folder to your server.
Then, log into BBCRM and navigate to Administration>Application>Catalog Browser. Once you are there, filter for a type of "Package" and an author of "Styons Software".
Load the Individualization package.
To register your product, go to Administration>SSC License Keys. Enter your license key and click "Save". Now the product is fully installed.
When you are viewing an individual, a new task will be available on the left side of CRM called 'Convert to organization'.
Simply click that task, and answer 'Yes' to the prompt. The page will refresh, and you will now see your constituent as an organization.
When you are viewing an organization, a new task will be available on the left side of CRM called 'Convert to individual'.
Simply click that task, and answer 'Yes' to the prompt. The page will refresh, and you will now see your constituent as an individual.
Individualization includes two Global Changes. One converts a selection of constituents into organizations. The other (you guessed it) does the reverse.
If your selection includes constituents who are neither constituents nor orgs (for example, Groups) then they will be ignored.
Individualization a configuration area for constituencies. It is under Administration>Styons Software>Individualization Configuration
In that area, you can define rules related to constituencies when changing to an organization, or to an individual.
These rules apply for manual one-off conversions, as well as for conversions that take place in bulk via the Global Change.
When you specify that a constituency should be end dated, then it will be end-dated upon conversion.
The end date will have the date that the conversion occurred.
When you specify that a constituency should be created, then it will be created upon conversion.
The start date given to the new constituency will be the date of the conversion.
If the constituency is already present and active, then no change will occur.
If the constituency is already present, but was end-dated, then the end date will be removed.
Replacing a constituency will remove the previous constituency, and create the desired constituency in its place.
For example, you might specify that converted organizations with a constituency of "Matching Gift Organization" should instead receive a "Major Giving Prospect" constituency.
If the "replace this" constituency is not present on the constituent record, then this rule will have no effect.
Blackbaud CRM has database-level constraints on the constituent ISORGANIZATION flag, which prevent organizations that have org-specific data from being changed.
To satisfy the database requirement that indviduals never have org data, a custom table contains org data after conversion. This means that a former organization can be
changed back without losing data. If you need to access this backed-up data directly, you can do so by looking in these two tables: