Move from HighLevel to Seedly: The GoSeedly Migration Guide

Do this

Unzip into its own folder. On a Mac, double-click Start GoSeedly.command; if macOS says it cannot verify the developer, right-click, choose Open, then Open again. On Windows, double-click Start GoSeedly.bat. From a terminal inside the folder:

npx pnpm install
npx pnpm start

The first start installs dependencies, checks the computer, opens the local page in your browser, and creates a private data folder at ~/.goseedly. Leave the window open while you work.

Check

Choose Explore sample data and walk all five stops. Sample mode is deterministic, synthetic and offline; it never touches a real account or the network. The same run works headless:

npx pnpm cli sample --tier small     # or --tier messy; add --json for a summary

Do this

From the unzipped folder, check first, then install. The dry run checks the Seedly version and extension ownership, lists every file it would write, and changes nothing.

node seedly-module/bin/install.mjs --seedly /absolute/path/to/your/seedly-checkout --dry-run
node seedly-module/bin/install.mjs --seedly /absolute/path/to/your/seedly-checkout

The installer copies the add-on into convex/goseedly/, writes the extension registry lines Seedly expects, records the install in .modules.json, runs Seedly's own install, build, type check and the add-on's tests, and prints the deploy command. It never deploys and never touches SETUP/, LICENSE.md or SUPPORT.md. Deploy to development yourself:

npx convex dev --once

Then

In the Seedly dashboard, as an agency owner: Settings → API Keys → Create key. Grant exactly two scopes, GoSeedly - Read and GoSeedly - Write, and nothing else. A sub-account key (sk_live_…) locks the tool to that one destination; an agency key (sk_agency_live_…) lets you pick the destination per job.

In the wizard, enter the Convex HTTP Actions URL, https://<name>.convex.site, and the key. Not the dashboard login address and not the .convex.cloud client URL.

Check

Test connection should show the add-on version, the destination agency and sub-account IDs, and the users available for owner mapping. Read the destination it names, not just the green message. A blank key field after saving is normal: the key lives in the vault and is not shown again.

OAuth

1. Create the app as Private, target user Sub-account, installable by everyone, bulk install allowed. Private is visibility; the version must also be published Live for normal agency OAuth. Never submit it for public review.
2. Add scopes from the wizard's preset as a checklist, one by one. Core CRM is 12 permissions; Everything readable is 69, 68 reads plus oauth.write for the token exchange. Never use a group's Select all; it includes write permissions.
3. Add the redirect URL the wizard shows, http://127.0.0.1:48231/oauth/callback by default, click Add, and Save. A URL typed but not added is not registered.
4. Under Manage → Secrets → Client keys, add a key and paste the Client ID and secret into the tool. Not the Shared secret; that is a different feature.
5. Start the connection from the tool so it can verify the callback, then run Check access.

PIT

Create one read-only token per sub-account, paste it with the agency and location IDs, and run Check access. To replace a rotated token later, use Saved connections → Replace token on the same connection; adding a new connection does not repair an existing job.

Do this

Tick the sub-accounts, choose categories and a date range, and pick an archive folder with room. An empty date range defaults to the last ten years; set From explicitly if your history is older. Start with core CRM for a focused first test; broader archive coverage is a separate check.

npx pnpm cli jobs create --location <id> --sub-account <id>   # add --everything for the whole readable surface
npx pnpm cli run <job id>
npx pnpm cli status <job id>   # pause, resume and cancel take the same id

Check

Progress shows fetched against known totals. When HighLevel cannot say how many records exist, it says counting. Rate-limit waits are automatic; a large account simply takes longer, and restarting does not make it faster.

Decide

• Duplicates: a shared phone or name is a match signal, not proof. Keep records separate when unsure.
• Owners and users: invite or create people in Seedly first, assign their permissions there, then refresh and map. The tool never invents users.
• Pipelines and stages: map to existing ones, or create empty pipelines and append missing stages from the mapping page. Updates are append-only and same-name stages are reused.
• Custom fields: create now, or leave as create during import. Existing definitions are reuse-only; the tool never renames a field or changes its type.
• Anything it refuses to invent stays on the issues list until you decide.

Do this

Run the dry run. Read the create, link, skip and reject counts and resolve every blocker. Then approve that exact plan.

npx pnpm cli run <job id>                                # from Review: runs the dry run, prints the plan hash
npx pnpm cli approve <job id> --plan-hash <hash>

Do this

npx pnpm cli run <job id>      # after approval: imports, then verifies
npx pnpm cli report <job id>   # the summary and where the files are

Check

Open representative contacts, deals and historical conversations in Seedly yourself. Completed with exceptions is not Completed: open the exception list, which names each record, the reason and the recommended action. Typical entries are an attachment that had expired in HighLevel, a phone number without a country code, or an owner with no matching Seedly user.

If stuck

Jobs resume from their last safe checkpoint. Run the doctor and read the recovery guide in the download before retrying an interrupted import. A support bundle from the report screen contains counts, codes and IDs only; preview it before you share it.

npx pnpm run doctor
npx pnpm cli resume <job id>