Getting started with Power CRM

Before you start

You need three things:

• A GoHighLevel agency account with at least one sub-account (location).
• Permission to install marketplace apps on that agency.
• A decision about which locations Power CRM may access. You can add more later.

You do not need to migrate or export anything. GoHighLevel stays the source of truth; Power CRM reads from it, caches it, and writes back to it.

1. Install from the GoHighLevel marketplace

Find Power CRM in the GoHighLevel marketplace and install it against your agency (not a single sub-account). GoHighLevel will show you the scopes the app requests — contacts and their custom fields, location custom fields and custom values, calendars and appointments, users, and the objects the modules you plan to use require. Approve them and you land back in the app.

Your team does not create a Power CRM account. The app decrypts the GoHighLevel SSO payload, so opening it inside the GoHighLevel iframe logs your team straight in.

2. Connect your locations

The OAuth flow uses GoHighLevel's chooselocation screen. Select the sub-accounts Power CRM should manage. The tokens are stored and kept alive by a token-refresh worker — you should never have to reconnect manually.

If there are sub-accounts you deliberately do not want touched, add them to the location blacklist in sync settings.

3. Let discovery and backfill run

Two things now happen without you:

• Client discovery. A background worker finds the locations from your installs and creates the matching client records.
• Sync backfill. Run the one-shot backfill from settings to pull historical contact and custom-field data for the connected locations. Do this once, when you first connect an agency that has been on GoHighLevel for a while.

Watch progress on the Sync Status screen. Every worker shows its last run and its current state, and you can trigger or force any of them by hand.

4. Map your fields

Open Sync → Mapping. This is where you tell Power CRM which GoHighLevel contact custom fields correspond to which location custom values. Search a contact, assign the location, pick both sides, save. Recent mappings are kept so a second sub-account is much faster than the first.

Field-value sync then runs in both directions on a schedule. Anything that diverges lands in Sync → Conflicts as an explicit decision rather than being silently overwritten.

5. Configure onboarding stages and statuses

This is the step that determines whether the app fits your agency. Take your time here.

1. Stages and sections. In Settings → Onboarding Config, define the stages your onboarding actually moves through, the sections inside each stage, and the fields inside each section. Set the order and the required flags.
2. Field names and descriptions. Give every field a friendly name and a description. If you do not want to write them, the AI description generator will draft an actionable instruction with an example using your agency context and the field's siblings.
3. Status flow. In Settings → Status Flow, define the states a field moves through — for example: supplied by client → reviewed by team → approved, plus not-applicable. This is what makes the Missing Info queue meaningful.
4. Client visibility. Mark which fields an account-level (client) user may see and edit. Everything else stays internal.
5. Field → service map. Assign fields to Website, SEO, Paid Ads, Social or Email so each delivery team sees only its own fields.

6. Configure the AI stack

In Settings → AI, choose the provider. The ladder is Claude, OpenRouter, the Anthropic API, an internal gateway, or OpenAI. Set a standard model and an advanced model; individual requests can be toggled to the advanced one.

Optionally supply keys for the lookup tools — a Google Places key enables the Google Business lookup used during field generation. Without it, the loop degrades gracefully rather than failing.

7. Onboard your first client

1. Open the client from the client list (it is already there — discovery created it from the location).
2. Run Brand Fetch with their domain. Colors, fonts, tagline, about-us copy, socials and logo come back and are queued into the mapped GoHighLevel fields.
3. Run the website crawl so the AI features are grounded in the client's real site. Browse the result under Sync → Website KB.
4. Open the Onboarding tab and use AI generate on the fields that are publicly knowable. Review each generated value — it arrives with its status intact and still needs approval.
5. Flag what only the client can supply. The reminder scheduler chases them from there.
6. Check Dashboard → Missing Info — the client's remaining blockers now appear in the cross-client queue.

8. Turn on the optional modules

• Documents. Build your document templates first (Settings → Document Templates), then create client documents from them. Use the Pages Designer to brand the client-facing pages.
• Meetings. Create agenda templates. After a call, fetch the transcript and generate action items with assignees and priorities.
• Calendars. In Settings → Calendars, pick which GoHighLevel calendars the app uses.
• Fax. Enable the module, then provision a new fax number or attach an existing one per location.
• Plans & services. Define your services with retail prices, bundle them into plans, and assign a plan per client.
• Users & roles. Sync your GoHighLevel users into the app, then set roles (admin / manager / team) and per-service permissions.

Operating the sync

Three screens matter day to day:

• Sync → Status. Worker state, last run, manual trigger, force sync, location blacklist.
• Sync → Conflicts. The divergence queue. Resolve one, resolve all, ignore a field permanently, or delete the record.
• Dashboard → Missing Info. Every blocking field across every client. This is the delivery team's daily list.

Writes you make in Power CRM are saved locally first and pushed to GoHighLevel by a worker every 30 seconds. If a field shows as pending for longer than that, check Sync Status — the CRM API may be rate-limiting, and the queue is waiting rather than dropping your edit.

Uninstalling

Uninstall Power CRM from GoHighLevel as you would any marketplace app. The app.uninstall webhook stops the sync workers for your account, revokes the stored OAuth tokens, and deletes the cached CRM data for the affected locations. Your data inside GoHighLevel is untouched — it was always the source of truth. See the privacy policy for the full retention and deletion detail.

Getting help

Email [email protected], or use the form on the support page. If something is not syncing, include the sub-account name and a screenshot of the Sync Status screen — that is usually enough for us to answer in one reply.