Funnel template import in GoHighLevel: what moves, what breaks

The three ways a funnel moves between sub-accounts, and the dependencies each one leaves behind for you to rebuild.

A funnel that took a week to build can land in another sub-account in about a minute, and that speed is exactly why the copy so often arrives half working. The pages come across. The things those pages quietly depend on — a merge tag the headline reads from, the domain the checkout button posts to, the product sitting behind an order form — do not always come with them, and nothing in the interface stops to tell you which ones are missing.

The cure is not a slower import. It is knowing, before you click anything, which route you are using and what that route is actually able to carry.

Funnel template import in GoHighLevel: what moves and what stays behind

Every way of getting a funnel from one place to another is doing one of three jobs: reading a share link, unpacking a snapshot, or duplicating inside the sub-account you are already standing in. In the menus they look interchangeable. In behaviour they are not.

The three routes, and what each one carries

A share link

Sharing a funnel produces a URL. Anyone holding that URL, with write access to a location, can pull in a copy of the funnel’s steps, sections and page content. It is the narrowest route by design: it brings the funnel, and it leaves behind the automation that makes the funnel do anything. A share link is the right choice when you are moving a design, not a system.

A snapshot

A snapshot captures a whole sub-account as a template — funnels alongside workflows, pipelines, custom fields, calendars and triggers. Loading one into a fresh location brings the funnel and its supporting objects together, which makes it the correct route when the funnel is one part of an offer rather than a standalone page. Whoever built the snapshot can also lock individual assets inside it, which changes what someone importing it is allowed to open afterwards; that mechanism is covered separately in the guide to protected snapshot assets.

An in-account clone

Duplicating a funnel inside the sub-account that already holds it is the only route where custom values, media and products are present from the first second, because you never left the container that owns them. It is the route for A/B variants and for keeping a working copy before you edit a page that already receives traffic.

Choosing a route before you click

Importing from a share link, step by step

1. Open the destination sub-account first and read the name at the top of the screen. The import lands wherever you are standing, and correcting that afterwards means importing again and deleting the first copy.
2. Paste the share URL. The screen names the funnel it is about to bring in and asks which location receives it. Read the funnel name back — a share link that has been passed around a team is often a link to an older revision.
3. Let the funnels list populate rather than refreshing the browser. A funnel with many steps arrives step by step, and a refresh mid-import produces a list that looks incomplete when it is simply not finished.
4. Open every step once in the builder. A page that has never been opened after import is the page that surfaces a missing asset three days later in front of a client.
5. Attach a domain and set the path before you point any traffic at it.

What does not travel, and what to rebuild first

Custom values

Text merged into a page from a custom value arrives as the merge tag, not as the text. If the source account defined a value for a booking link or a company phone number, the imported page still asks for that value by name, and the destination account has never heard of it. The visible result is a blank where a sentence used to be, or a button whose link resolves to nothing. Create the custom values in the destination sub-account first, spelled exactly as the source spelled them, then reload the page in the builder.

Domains and paths

A funnel step’s public address is a domain plus a path, and domains are attached per sub-account. An imported funnel therefore has paths and no domain until you give it one, which is why a freshly imported funnel returns nothing at all when you try to preview it publicly. This is the same class of dependency as the sending domain an email step relies on, described in the write-up on workflow sender domains: the object imports cleanly, and the account-level thing it points at has to exist on the other side.

Media, fonts and images

Images placed on a page can arrive as references back to the source account’s media library. That keeps working right up until someone tidies the original library, at which point the image disappears from a funnel in an account nobody connected to it. Re-upload the images you intend to keep into the destination library and repoint the sections that use them, starting with anything above the fold.

Products, order forms and payment connections

An order form is a reference to a product, and products belong to the sub-account’s own payments area along with the payment provider connection behind them. The step imports; the product does not follow it. Expect to rebuild the product, reconnect the provider, and then re-select the product inside the order form element rather than assuming the element remembered it.

Forms and surveys

A funnel step that embeds a form is embedding a reference to a form, not a copy of one. After an import, confirm the element is pointing at a form that exists in this account, then check that form’s own availability rules — forms and surveys can be scheduled to open and close, and an expired one renders as an empty block on an otherwise healthy page. The schedule visibility settings for forms and surveys are worth a look before you blame the import.

Why an imported funnel looks broken when it is not

Four symptoms account for most of what gets reported as a failed import, and none of them are damage to the funnel itself.

A section that renders blank is usually an unresolved custom value. A page that returns nothing on a public URL usually has no domain attached yet. Steps appearing in an unexpected order happens because order is a property of the funnel, not of the pages, and it is reset by hand in the funnel view. And a button that does nothing is typically an action pointing at a step identifier that no longer exists in the new account — open the element, re-select the destination step from the dropdown, and save.

A post-import checklist

1. Confirm you are in the intended sub-account.
2. Recreate the custom values the funnel expects, by exact name.
3. Attach the domain and set each step’s path.
4. Open every step in the builder and save it once.
5. Re-upload media that still points at the source library.
6. Rebuild products and re-select them inside order form elements.
7. Re-point every button and form element at objects in this account.
8. Load the live URL on a phone before you hand it over.

Treated as a two-part job — move the design, then rebuild the dependencies — an import stops being a gamble. The route you choose decides how much of part two is left, and that decision is made before the click, not after it.

See also: Multiple Domains One Funnel: Canonicals and Duplicate Pages

Frequently Asked Questions

What is the difference between a funnel share link and a snapshot?

A share link moves one funnel: its steps, sections and page content. A snapshot moves a whole sub-account template, so the funnel arrives alongside the workflows, custom fields, pipelines and calendars it works with. Use a share link when you want a design and will wire the logic yourself, and a snapshot when the funnel is one part of an offer you are standing up in a new location.

Why is my imported funnel page blank in places?

Almost always an unresolved custom value. Text merged into a page arrives as the merge tag rather than the text, and the destination sub-account has never heard of the value the source defined. Create the custom values with exactly the same names in the receiving account, then reload the page in the builder.

Do workflows come across with a funnel share link?

No. A share link carries the funnel and not the automation attached to it, which is deliberate rather than a fault. If you need the triggers and workflows to travel with the pages, move the whole thing as a snapshot instead, or rebuild the automation in the destination account after the pages arrive.

Why does the imported funnel return nothing on its URL?

A step’s public address is a domain plus a path, and domains are attached per sub-account. An imported funnel has paths and no domain until you attach one, so a public preview resolves to nothing. Attach the domain, set each step’s path, then load the live URL rather than the builder preview.

Do products and order forms import with the funnel?

The order form element imports, but the product it points at does not, because products belong to the receiving sub-account’s own payments area along with the payment provider connection behind them. Rebuild the product, reconnect the provider, then open the order form element and re-select the product rather than assuming it remembered.

Can I import the same funnel template into several sub-accounts?

Yes, and a share link is built for exactly that. The cost is that each destination needs its own pass of the rebuild work: custom values, domain, media, products and any element that points at another object. If you are doing this repeatedly, capture the finished sub-account as a snapshot so the supporting objects travel too.

What should I check before handing an imported funnel to a client?

Open every step in the builder and save it once, confirm no merge tag is showing on the rendered page, load the live URL on a phone, submit the form or order form yourself, and confirm the submission lands where you expect it. A page that has never been opened since the import is the one that surfaces a missing asset in front of the client.

We build your GoHighLevel account for you

CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.

• Setup (one-time)$850
• Ongoing (per month)$38.80

Get my free setup quote

No obligation quote · reply within 1 business day

This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.