Migrate Salesforce Accounts to GoHighLevel via Google Sheets

Migrate Salesforce Accounts into GoHighLevel from Google Sheets—automatically

This n8n workflow manually migrates Salesforce Account records stored in Google Sheets into GoHighLevel Business records using the LeadConnector API. It creates the business, updates a GoHighLevel custom object with Salesforce fields, bulk-associates related contacts, and logs progress and errors back to Sheets.

What this workflow does

• Runs on demand: execute by clicking Execute workflow in n8n.
• Reads pending rows: pulls Salesforce Account rows marked NOT DONE from a Google Sheets tab and applies a batch size limit.
• Tracks migration progress: processes each account sequentially and marks the row as DONE in Google Sheets.
• Creates GoHighLevel Business records: uses the LeadConnector API to create a Business record with mapped fields such as name, address, phone, website, and description.
• Updates a GoHighLevel custom object: writes Salesforce-specific properties (e.g., Account ID, Parent ID, price book, and other mapped attributes) via the LeadConnector API.
• Associates related contacts: looks up GoHighLevel contact IDs in a separate Google Sheets contacts tab by Salesforce Account ID, then bulk-associates those contacts to the new GoHighLevel Business (if present).
• Writes results back to Sheets: stores successful GoHighLevel Business IDs and logs errors for business creation, custom object updates, and contact association in dedicated error tabs.

Use cases

• Move legacy Salesforce Accounts into GoHighLevel during CRM cutover.
• Iteratively migrate records in controlled batches, using Google Sheets as the staging layer.
• Backfill GoHighLevel custom object fields and ensure contacts are linked to the correct migrated businesses.

Technical details

• Workflow nodes: if, code, limit, sticky note, http request, google sheets.
• API integration: GoHighLevel LeadConnector API via HTTP Request.
• Authentication: create a GoHighLevel private integration token and replace YOUR_GHL_API_TOKEN in the Authorization header for every LeadConnect call.