Kartra to GoHighLevel - platform migration plan
Twenty pages moving between platforms, each dragging its forms, calendars and integrations along with it. One row per page, one owner, one status, one place to record the exception.
The brief
Liviti’s pages had to move from Kartra to GoHighLevel: main website pages and landing pages, each with forms, calendars and integrations attached. The risk in a migration like this is not the building, it is the bookkeeping. Without a page-level view it is easy to mark a page complete while a link, a form or a destination still needs work, and easy to lose which of four people is holding it.
My role
I built and migrated pages, configured forms and calendars, and checked links and integrations. Twelve of the twenty pages were mine; the rest sat with three other named owners. The platform decision itself was made above me.
What I did
I worked from a plan organised across six labelled weeks. Each row connected the page name, its category - main website or landing page - the assigned resource, the form or calendar state, the integration notes, and both the Kartra source URL and the new GoHighLevel destination URL side by side, so the move was auditable page by page rather than in one lump at the end.
Exceptions stayed in the plan rather than being quietly dropped. Two pages were flagged as link not found, which is a smaller problem when it is written down in week two than when it is discovered after launch.
The output
A twenty-page migration schedule across six weeks with four named owners and per-page source and destination links. Two planning notes in it did the real work. The first: a landing page never moves alone - it drags its thank-you page and its calendar page with it, so the unit of work is the set, not the page. The second: the industry landing pages could all be done in one week by templating one and swapping the content, which is the difference between a six-week plan and a much longer one.
What happened next
The pages went live. The plan stayed useful afterwards because it recorded where each page came from as well as where it went, which made review during the transition much faster.
One reflection
Nothing in this project was technically difficult. It worked because delivery activity was tied to the operational details that usually disappear between design, build and launch - one row, one owner, one status, and somewhere to record the thing that did not fit.