The Scenario
You've been the CRM admin for seven months. Somewhere in the first three months, before anyone had a deduplication process, ForceManager filled up with duplicate company records — the same prospect entered by three different reps under slightly different names, or the same client imported twice when the team switched territory structures. You ran a deduplication script last week and it spat out a cleanup sheet with 90 company IDs flagged as duplicates or stale records. Now you need to delete them.
The bad version:
- Open ForceManager, go to Companies, search for the first ID, open the record, click the delete button, confirm the deletion.
- Go back, search for the second ID, open it, delete, confirm.
- Work through 90 deletions in sequence, spending 45 seconds each time navigating to the record and confirming the action.
- On deletion 73, accidentally search for the wrong ID because you copied from the wrong row in your sheet, delete an active client record, and spend an hour with ForceManager support trying to restore it.
The deduplication work is done. The cleanup sheet is clean. The only thing left is the mechanical part — and the mechanical part is how mistakes get made.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent that lives inside your Google Sheet. It reads the list of company IDs marked for deletion and removes each one from ForceManager in a single operation — no tab-switching, no per-record confirmation dialogs.
Delete every ForceManager company whose ID is listed in column A of this sheet
SheetXAI runs through each ID, sends the delete call to ForceManager, and writes a deletion status back to column B — confirmed deleted, or an error reason for any ID that couldn't be removed (linked records, insufficient permissions, ID not found).
What You Get
- All 90 company records deleted in a single operation.
- Deletion status written to column B for every row — confirmed or error with reason.
- Any record that couldn't be deleted identified with a reason — linked contacts, linked orders, permissions — so you can investigate those separately without re-running the full batch.
- The cleanup sheet becomes your deletion audit log.
What If the Data Is Not Quite Ready
Some IDs may have linked contacts or orders that would become orphaned on deletion
Deleting a parent company with active contacts or open orders may fail or create referential issues in ForceManager.
Before deleting, check each company ID in column A for linked contacts or open orders in ForceManager — flag those in column B, then delete only the records where column B is blank
The cleanup sheet has a mix of company IDs and contact IDs in the same column
The deduplication export accidentally combined both entity types in one sheet.
Look at the ID type column in column B — delete the ForceManager record from column A only where column B says "company", skip all rows where column B says "contact" or anything else
You want to archive instead of delete for records that have historical activity
Some of the duplicate companies have past activities tied to them. Deleting them would wipe the activity history. You want to mark those as inactive instead.
For each company ID in column A, check if the record has any logged activities in ForceManager — if it does, set the status to inactive instead of deleting; if it has no activities, delete it — write the action taken to column B
Check for linked records, handle actives differently, and clean up the full list in one prompt
For each company ID in column A where column B says "delete", check ForceManager for linked contacts or open orders — if linked records exist, mark the company as inactive and write "archived" to column C; if no linked records, delete the company and write "deleted" to column C; write any error to column D
One pass handles the entire cleanup sheet intelligently.
Try It
Get the 7-day free trial of SheetXAI and open any Google Sheet with a list of ForceManager company IDs you need to remove, then ask in plain language. For related workflows, see how to bulk-create fresh company records after the cleanup, or return to the ForceManager integration overview.