Removing 3000 opportunities

Hi Hugo Geyskens,

Methods of mass deletion include, but are not necessarily limited to, the following. The best choice is the one that aligns best with your interest:

1. ListView filtered search. This method lets you filter a list of records, then select up to 1000 of them at a time. If you need to delete 3k, this can be performed in 3 batches to fulfill your need.

2. Import to delete. This is not limited to 1k records, but is limited to the scale your system can handle when importing to update existing records. Here is documentation about importing to update records. To delete records this way, add a column to your CSV file with a 1 in each row you wish to delete.

3. Custom API or scheduler.  These require developer experience. An API script can log into Sugar as one of your users and can be programmed to delete the desired records. Alternatively, if you wish to routinely delete records, a scheduler can be created by a developer and installed in Sugar using a Module Loader package.

4. MySQL updates directly in the database. This approach side-steps the functionality of the application and therefore involves more than simply updating the one module's deleted column. The application runs code to also delete relationships between the deleted records and other modules, so those relationships would also need to be identified and updated if this approach is used.

I hope this helps!

Hi Hugo Geyskens,

Methods of mass deletion include, but are not necessarily limited to, the following. The best choice is the one that aligns best with your interest:

1. ListView filtered search. This method lets you filter a list of records, then select up to 1000 of them at a time. If you need to delete 3k, this can be performed in 3 batches to fulfill your need.

2. Import to delete. This is not limited to 1k records, but is limited to the scale your system can handle when importing to update existing records. Here is documentation about importing to update records. To delete records this way, add a column to your CSV file with a 1 in each row you wish to delete.

3. Custom API or scheduler.  These require developer experience. An API script can log into Sugar as one of your users and can be programmed to delete the desired records. Alternatively, if you wish to routinely delete records, a scheduler can be created by a developer and installed in Sugar using a Module Loader package.

4. MySQL updates directly in the database. This approach side-steps the functionality of the application and therefore involves more than simply updating the one module's deleted column. The application runs code to also delete relationships between the deleted records and other modules, so those relationships would also need to be identified and updated if this approach is used.

I hope this helps!

Thanks Patrick, these are very valuable options.

We are running SugarCRM on own premises and I'm experiencing trouble importing (for update) more then let's say a couple of 100 records at the time...Maybe when importing for deletion goes more reliable/faster. I'll give it a try. Thanks again !

Hugo