With any credible, effective and extensively used centralised CRM database (irrespective of the actual database, with Caspian it can be its own, MS SQL Server, Oracle and IBM DB2) there comes a time when large changes and sometimes-global changes and/or updates are required.

With Caspian system administration tool, a business administrator (rather than having to use internal IT services) can safely and efficiently carry out numerous changes. The following is a small selection of examples.

• A salesperson has left and all of their future follow-up actions need to be distributed to not just one, but many other staff

• There has been misspelling of a number of Cities when the data was manually inserted or imported from external sources, these need to be merged with the correct city name. The same situation can apply to Counties!

• Several Job titles are mistakenly recorded in the incorrect job group, irrespective of how many Contact records are affected, it must be corrected so that the mailing selections are accurate

• A number of products are to get the recommended sales price increased by 10% so that the quotations being generated are accurate

• There are about 240,000 records in the prospects database, which must be transferred to a different database

• After purchasing and importing 1,000,0000 database records for emarketing, you have to delete those 998,000 records which did not generate a response, otherwise there will be financial penalties for continuing to use the data

• The contract services hired by you to do telesales follow-ups against 200,000 personalised mailings have now finished their work and there are still 8,000 records, which need to be transferred to internal permanent staff for follow-up

• There are specific customer records, which in total add up to over 30,000 records that need to be archived