The Scenario
The person who owned your LinkedIn Sales Navigator exports left the company six weeks ago. You found a folder on the shared drive with a sheet of 150 contacts — first name, last name, email, phone, and a company ID column — that were supposed to be imported into ForceManager last month. Nobody did it. The RevOps manager noticed the gap this morning and asked you to get it handled before the next rep assignment meeting.
The bad version:
- Open ForceManager, go to Contacts, click New, and start filling in the first row — first name, last name, email, phone — then scroll down to the company link field, search for the right company by ID, select it, and click Save.
- Repeat for all 150 contacts, spending 3-4 minutes per record because linking to the correct company requires a manual search each time.
- Realize partway through that the company ID in column E refers to ForceManager company IDs — but 12 of them don't exist in the CRM yet because those companies were never imported.
You didn't create this problem. But right now you're the one holding the sheet.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent that lives inside your Google Sheet. It reads the contact data, understands the column layout, and uses its ForceManager integration to create every contact record and link each one to its parent company in a single operation.
Create a ForceManager contact for each row in my sheet using columns: First Name, Last Name, Email, Phone, and Company ID
SheetXAI runs the import, creates each contact record, links it to the ForceManager company whose ID matches column E, and writes the created contact ID back to column F. Any row where the company ID doesn't resolve gets flagged in a status column.
What You Get
- A ForceManager contact record for every row in the sheet, linked to the right company.
- Created contact IDs written back to column F.
- Rows where the company ID wasn't found in ForceManager flagged in column G with a "company not found" note — separate from the rows that succeeded.
- A sheet that doubles as the import record: what was submitted, what was created, what was skipped.
What If the Data Is Not Quite Ready
Some company IDs in column E don't resolve to existing ForceManager companies
The export came from a different system and some IDs may be stale or unformatted.
Before creating the contacts, check each company ID in column E against ForceManager — write "exists" or "not found" to column G, then import only the contacts where column G says "exists" using First Name, Last Name, Email, Phone, and Company ID
Email addresses in column C are malformed or duplicated
A few rows have blank emails, some have obvious typos, and a handful are duplicated because Sales Navigator returned the same person from two searches.
Remove duplicate rows where column C email matches a previous row, flag blank or clearly malformed emails in column G, then create ForceManager contacts for the remaining rows using First Name, Last Name, Email, Phone, and Company ID
First and Last Name are in a single column instead of split
The export merged full name into column A with no separate columns for first and last.
Split the full name in column A into first name and last name, then create a ForceManager contact for each row using the split names, column C for email, column D for phone, and column E for Company ID
Deduplicate emails, split names, validate company IDs, and import all contacts in one shot
Remove email duplicates keeping the first occurrence, split full names in column A into first and last, verify each company ID in column E exists in ForceManager, then create contacts for every qualifying row — write the created contact ID to column F and any skip reason to column G
One prompt. No intermediate prep step needed.
Try It
Get the 7-day free trial of SheetXAI and open any Google Sheet with a list of contacts you need in ForceManager, then ask it to run the import in plain language. For related workflows, see how to bulk-create the company records first, or return to the ForceManager integration overview.