Data Management Best Practices

Phone calls, emails and messages - every minute, information arrives at your desk. And every bit of it is essential information that you use to manage your business and schedule your day. While this data is key to your business operations, in weeks or months, it can become less relevant, replaced by new information.

In database terms, this is called data aging. Over time, your data ages, and is no longer current. Eventually, your database becomes cluttered with old, irrelevant information. When this happens, system performance can suffer.

If a search takes longer today than it did six months ago, it may be that the system has hundreds of thousands more records to look through. If this is happening to you, work with your System Administrator to identify data that is no longer needed and can be removed.

Two options are available to resolve this situation:

• Delete Old Data
• Purchase additional storage space

• Learn more: Modify your Service Plan

Delete Old Data

Use the Mass Operations feature to identify outdated information and Mass Delete Data. Optionally, reassign the records to a new owner Mass Ownership Change, or update the records in one big batch Mass Update Data.

Follow these guidelines to cleanse the database and optimize performance in order to keep your system operating at peak efficiency.

Delete Old Activity Associated with Accounts and Contacts

Good examples of data you can safely remove:

• "left a voice mail message" activities
• "call again" note
• "mailed an information kit" completed task
• "faxed proposal version 2a" activity

Remove Unused Fields

If you customized your application with additional fields and tabs, you might want to review your system every six months or so and consider what is no longer used. Follow these steps as a guide:

1. Build a View to find fields you no longer use
2. Confirm that no activity has been applied to those records
3. Delete the fields or tabs

A good practice is to schedule these types of operations after business hours to maintain optimal performance.

Automatically Mark Records for Deletion

Add a Data Policy: Just as you can flag a message in your email system, you can flag a record when it meets your criteria for "old" information. A data policy can help automate this process.

1. Add a new field, called "To Be Deleted" (choose field type = checkbox)
2. Create a data policy that marks records that were created over 365 days ago, but have not had activity in the last three months (or whatever is meaningful in your organization)
3. Create a view to display the records that are marked "To Be Deleted"
4. At a future date, use the Mass Delete Data to remove these records