How to Import Stripe Products into GoHighLevel SaaS Configurator (Legacy V1)

What the Stripe import actually does

The GoHighLevel SaaS Configurator (Legacy V1) provides a way to connect Stripe products to SaaS plans configured in GoHighLevel. The important relationship is between a GoHighLevel plan and the specific Stripe billing information selected for it.

In practical terms, the setup has three layers:

• Stripe product: The commercial item or subscription offering stored in Stripe.
• Stripe price: The amount, currency, and recurring interval associated with that product.
• GoHighLevel SaaS plan: The plan customers see or receive through the GoHighLevel SaaS setup.

Importing or selecting a product does not remove the need to verify the price attached to the plan. A product can have more than one price, such as monthly and annual recurring prices. The business meaning of the plan must be clear before a price is selected.

Prepare Stripe and GoHighLevel before importing

Preparation reduces ambiguity during the mapping step. Before opening the SaaS Configurator, write down the plans you intend to offer and the exact billing option for each one. For example, a plan might be called Pro Monthly in the customer experience but use a Stripe product named Pro with a monthly recurring price.

Check the following conditions:

• You can access the relevant GoHighLevel agency account and Agency View.
• The correct Stripe account has been created, verified, and is available for connection.
• The required Stripe products exist and are active.
• Each product has an appropriate recurring price, currency, and billing interval.
• The corresponding SaaS plans have been defined in GoHighLevel, including their intended names and commercial terms.
• You know which account owns billing and which system is responsible for customer access or provisioning.

Use clear names where possible. Naming a price or product by amount alone makes future maintenance harder. A consistent naming pattern such as product, market, and interval can make selection safer when several similar records exist.

Connect Stripe in the Legacy V1 SaaS Configurator

The exact labels and placement of controls can change as GoHighLevel updates its interface, but the connection sequence follows the same operational logic.

1. Sign in to GoHighLevel and open the relevant Agency View.
2. Open the SaaS Configurator area.
3. If more than one configurator experience is available, open the Legacy V1 version required for this workflow.
4. Find the Stripe connection or billing integration section.
5. Choose the option to connect Stripe and complete the authorization flow.
6. Return to GoHighLevel and confirm that the intended Stripe account is shown as connected.

Do not assume that a successful authorization means the plan mapping is complete. Connection gives GoHighLevel access to the relevant Stripe catalog. It does not determine which product or price belongs to each SaaS plan.

Import and map Stripe products to SaaS plans

Once Stripe is connected, configure each SaaS plan individually. Mapping one plan at a time makes it easier to review the commercial meaning of every selection and reduces the risk of copying the wrong price across several plans.

Step 1: Open the product mapping area

From the Legacy V1 configurator, open the settings for the SaaS plan you want to configure. Look for a product, Stripe product, billing product, or similar field. The label may vary by interface version.

Start with one plan rather than selecting products in bulk. The first plan establishes whether the connected Stripe catalog is the correct one and whether the available records contain the billing options you expect.

Step 2: Select the Stripe product

Use the available import, dropdown, or selection control to load Stripe products. Select the product that represents the intended SaaS offering. Do not choose based only on a familiar product name. Compare the product name, status, price information, and plan documentation.

If the list is empty, stop and resolve the catalog or connection issue before continuing. Creating a duplicate product in Stripe to make the list easier to read can create a second source of truth and make later maintenance more difficult.

Step 3: Verify the associated price

After selecting a product, inspect the price details presented by GoHighLevel. Confirm all of the following:

• Amount: The charge matches the intended SaaS plan.
• Currency: The currency matches the market and checkout expectation.
• Interval: Monthly, yearly, or another recurring interval is correct.
• Trial settings: Any trial period or introductory arrangement matches the plan design.
• Active status: The selected product and price are available for the intended use.

Where Stripe contains several prices for one product, the price is the critical selection. A product name alone is not enough to prove that the plan is configured correctly.

Validate the mapping before publishing

Configuration should be tested as a business transaction, not only as a saved setting. The purpose of validation is to confirm that a customer selecting a particular GoHighLevel SaaS plan reaches the intended Stripe billing record and receives the expected access or provisioning outcome.

Run a controlled test where the platform allows it. Confirm the selected plan, the Stripe subscription details, the recurring price, and the downstream GoHighLevel behavior. The test should answer a practical question: if a customer buys this plan, does the correct business state appear in every system that needs it?

Maintain imported products safely

Stripe catalog changes should be managed as controlled changes to a live operating process. Review the related GoHighLevel plan whenever a product or price is created, archived, replaced, or materially changed.

For recurring billing, avoid treating a price change as a minor text edit. Depending on how the change is made and how the integration behaves, existing subscriptions and new subscriptions may not be affected in the same way. Record which price is used for new customers and which price is associated with existing subscribers.

Use an ownership rule: Stripe owns the authoritative billing amount and interval, while GoHighLevel owns the plan configuration and the workflows that depend on the subscription state. When ownership is unclear, administrators may update one system and assume the other has changed automatically.

If your wider sales or customer lifecycle process also depends on CRM stages, define those stages as meaningful business states rather than as a list of activities. A clear ownership model is easier to maintain when the billing and customer workflows are designed together. ConsultEvo’s CRM consulting services cover pipeline architecture, integrations, and operational visibility.

Troubleshoot common Stripe import problems

Stripe is not connected

Reopen the connection area and confirm that authorization completed for the intended Stripe account. If multiple accounts or environments are involved, check the account identity rather than assuming the most recently opened Stripe session was used.

The product list is empty

Confirm that products exist in Stripe, are available to the connected account, and meet the status requirements of the configurator. Refresh the selection area after checking the connection. If the list remains empty, verify that you are using the Legacy V1 configurator and that the account has the necessary access.

The expected price is missing

Inspect the Stripe product directly and confirm that the required recurring price exists. Check currency, interval, and active status. A product may be visible while the particular price required for the SaaS plan is not available or is not selected.

The wrong amount or interval appears

Return to the plan mapping and compare the selected price with the intended commercial definition. Do not correct the display by changing unrelated plan fields. First identify whether the error is in Stripe’s catalog, the selected price, or the GoHighLevel plan configuration.

Billing works but access does not

This usually indicates that the billing mapping and the provisioning workflow are separate concerns. Review the event, status, or automation that should move the customer into the correct access state. The subscription can be valid in Stripe while the handoff into GoHighLevel remains incomplete.

A practical operating model for Stripe and GoHighLevel

Use a simple sequence whenever you add or change a SaaS plan:

1. Define the business offer: Document the plan name, amount, currency, interval, trial, and access outcome.
2. Configure the billing record: Create or identify the corresponding Stripe product and price.
3. Map the plan: Select the correct product and price in the GoHighLevel Legacy V1 SaaS Configurator.
4. Test the handoff: Validate billing, subscription status, customer access, and internal workflow behavior.
5. Record ownership: Note where future changes must be made and who reviews them.

This sequence keeps automation downstream of a clear decision. If the plan definition is ambiguous, adding more automations or tools will not make the subscription process more reliable. For broader systems, CRM, and automation work, see ConsultEvo’s systems and automation services.

GoHighLevel and Stripe can support a streamlined SaaS setup when the catalog, plan mapping, ownership, and validation steps are treated as one workflow. The import is the middle of that workflow. The real objective is consistent billing data, predictable provisioning, and a configuration that another operator can understand and safely maintain.