- Published
- Byline
- GoHighLevel Partners Editorial
- Filed under
- GoHighLevel Automation
A step is a page plus a set of references — the page travels, most of the references do not, and each one left behind fails quietly.
Move step between funnels: what travels with the page and what stays behind
A step looks like a self-contained thing. It has its own canvas, its own sections, its own settings panel, and moving it to another funnel feels like it should be a drag. In practice a step is a page plus a set of references — to a path, to a position in an order, to a product, to a form, to whatever is listening for a visit. The page travels. Most of the references do not, and each one that is left behind fails quietly rather than loudly.
This is worth doing carefully because the usual reason for the move is that a step is working: a landing page that converts, an application form that gets filled in, a confirmation that reads well. Copying a good step into a second campaign is one of the cheaper wins available. Losing its wiring on the way over turns it into a page that looks right and produces nothing.
There is no true move, and that is fine
What is actually available is a copy. You duplicate the step into the target funnel and then decide what happens to the original — leave it, unpublish it, or delete it once the new one is proven. Thinking of it as copy-then-retire rather than move is not pedantry: it is what lets you verify the new step against a still-working original instead of against a memory.
If the step is one you expect to reuse repeatedly rather than move once, the better mechanism is saving a section to the library. A saved section can be dropped into any funnel on demand, which turns a one-off migration into a component you keep. The same thinking sits behind a funnel template import — a funnel template is that idea at whole-funnel scale.
What comes with the page
| Element | Travels | What to check afterwards |
|---|---|---|
| Sections, rows, design | Yes | Responsive settings, which are per-breakpoint and easy to miss |
| Text and images | Yes | Alt text, and any link written into the copy |
| Form or survey element | The element does | Which form is selected, and where it redirects after submit |
| Buttons | Yes | Their action — a next-step button points at the old funnel’s step |
| Step path | No | The new funnel gives it a new address |
| Position in the order | No | It lands wherever you drop it |
| Products and order form | Re-attach | The product exists once; the page reference is new |
| Head and body code | Per page, re-paste | A frequent cause of tracking code that stops firing |
| SEO fields | Re-enter | Blank fields fall back to something generic |
The button that points backwards
The single most common breakage is a button. Inside a funnel, a call to action usually resolves to “the next step”, or to a named step in that funnel. Copy the page into a different funnel and the button keeps its old reference, so a visitor in campaign B is handed to a page in campaign A. Nothing errors. The visitor simply leaves the campaign you were measuring.
Open every button, every image link and every text link on the copied page and re-point it against the new funnel’s steps. The ones written inline in a paragraph are the easiest to overlook, because they are not in the settings panel where you are already looking.
Order-dependent behaviour does not survive a position change
Some behaviour is a property of where a step sits rather than of the page itself. an order bump belongs to a checkout position. the thank-you step means something because of what precedes it. A one-click follow-on offer assumes a purchase happened a moment ago. Drop any of those into a different position and they still render, but the logic around them no longer holds.
Decide the position in the target funnel before copying, not after. And if the step was part of split testing at step level, copy the winning variant deliberately — a split test does not carry across, and copying while a test is running gives you an arbitrary half of the traffic’s experience.
Things listening for the old step
The references that break most quietly are outside the funnel. A workflow with a page-visit trigger, a condition that names the old step, an automation that redirects to a specific path after an action, a tracking event configured on that page: all of them point at the original and keep pointing there.
Two of these deserve a direct check. Anything driven by the payload a webhook sends may carry the old path as a redirect target in its response handling. And code placed in the page header is per-page, so a pixel or a consent script that was pasted into the old step is simply absent from the copy until you paste it again.
Paths, links and what the outside world remembers
If the original step was live and reachable, its URL exists in places you do not control — ad destinations, already-sent emails, bookmarks, possibly search results. Copying the step does not change that; retiring the original does. If you intend to delete the original rather than leave it, put a redirect from the old path to the new one first, and re-check what belongs in a sitemap so the retired path falls out of it.
Where the move is part of a larger restructure — many steps heading to a new container rather than one step heading to a sibling campaign — the redirect mapping question is the same one that governs moving pages into a website container, and it is better answered once for the whole set than step by step.
Domains, and why the copy sometimes looks broken
The target funnel may sit on a different domain from the source. If so, the copied step inherits the target’s domain, and anything hard-coded to the source domain — an absolute link, a script restricted to one origin, an embedded form pointing at the old host — now crosses a boundary it did not before. If the target domain is newly attached, give it time before judging: a certificate that has not issued produces exactly the symptoms of a broken page while being nothing of the kind.
A short verification pass
- Load the copied step on the target funnel’s live domain, not in preview.
- Click every button and link; confirm each lands inside the new funnel.
- Submit the form and confirm both where the record lands and where the visitor is sent.
- Confirm the automation you expect actually fired, rather than assuming it.
- Re-paste head code and confirm the events register.
- Check the step on a phone, since responsive settings copy per breakpoint and one of them is usually wrong.
- Only then decide the fate of the original.
Two small refinements worth making while you are in the page: reconsider inline against popup form placement for the new context, since a form that worked inline in a long landing page often works better as a popup on a shorter one, and check whether a progress bar copied from the old funnel still describes the number of steps in the new one. A progress indicator that says step two of five inside a three-step funnel is a small thing that tells a visitor nobody is looking.
Frequently Asked Questions
Can a step be moved rather than copied?
Work as though it cannot. Duplicate the step into the target funnel, verify it there, and only then retire the original. Copy-then-retire lets you compare the new step against a working original, which is exactly what you need when a button or an automation turns out to be pointing the wrong way.
Why does the copied page send visitors to the wrong funnel?
Because its buttons kept their original targets. A next-step or named-step action resolves against the funnel it was created in, so after a copy it hands the visitor back to the source campaign. Re-point every button, image link and inline text link against the new funnel.
Do form submissions still work after the copy?
The form keeps working, since it is a separate object the page displays. What needs checking is the redirect after submission, which may still name an old path, and any workflow whose trigger or condition refers to the original step rather than to the form.
What happens to a running split test on that step?
It does not come across. Decide the outcome first, copy the variant you intend to keep, and treat the new funnel as a fresh test if you want one there. Copying mid-test moves one arbitrary half of the visitor experience and tells you nothing about either version.
Will the old URL keep working?
Only while the original step exists and is published. If you delete it, the old path stops resolving and every ad, email and bookmark pointing at it fails. Put a redirect from the old path to the new one in place before deleting anything.
Does tracking code come with the step?
Site-wide tracking applies wherever it was configured, but code pasted into an individual step’s header or footer is a property of that step and is not present on the copy. Re-paste it and confirm the events register rather than assuming they do.
Is it better to save the step as a template instead?
If you expect to use it more than once, yes. A saved section or a template turns the page into a component you can drop anywhere, which removes the copy step entirely for the next campaign. A one-off move does not justify the extra structure, but a page you keep reaching for does.
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
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.