Skip to main content
Agencies and studios often build a project once and reuse it as a starting template for the next client. Cloning a project copies the site structure — pages, navigation, optionally blog posts — into a fresh project you can customize.

​
When to Clone

  • Spinning up a new client site from your agency template
  • Starting a variant of an existing site (e.g., a landing page for a new campaign)
  • Testing changes on a copy before applying to the original
For one-off duplicates of a single page, use the page duplicator in the content editor instead.

​
How to Clone

1

Open the dashboard

Go to app.hiveku.com/dashboard.
2

Find the source project

Scroll or search to the project you want to copy.
3

Open the 3-dot menu

Hover the project card. A three-dot icon (⋮) appears in the corner. Click it.
4

Choose Clone Project

A menu appears with actions. Click Clone Project.
5

Confirm the options

Modal asks whether to include blog posts (on/off toggle). Leave on to copy existing posts as starter content; turn off for a clean slate.
6

Hiveku creates the copy

New project name defaults to {Original Name} (Copy). You’re redirected into the editor.
7

Rename immediately

Go to Settings > General > Project Information and click Edit. Give it the real client name. See Rename or Delete a Project.

​
What Gets Copied

CopiedNot Copied
All pages and their sectionsDatabase tables and data
Navigation structureAuth configuration
Blog posts (toggleable)Custom domains
Asset references (images, files)Environment variables
Page meta and SEO settingsDeployment history
Sitemap hierarchyTeam discussions and tasks
Asset references mean the new project points at the same image URLs as the original. This saves storage, but editing an image in the source affects the clone too. If you need independence, re-upload images in the clone — the editor’s asset panel lets you replace any image.

​
What You’ll Need to Set Up in the Clone

Since not everything copies, here’s the typical post-clone checklist:
1

Rename the project

Settings > General > Project Information.
2

Replace branding and copy

Logo, colors, headlines, calls to action — use the AI: “Update all copy to be for Acme Landscaping, a family-run business in Portland”.
3

Re-upload images if you need independence

Otherwise the clone and source share image URLs.
4

Configure environment variables

If your template uses env vars (API keys, feature flags), set new values. See Environment Variables.
5

Rebuild database and auth

Schema and auth config don’t copy. See Create Database Tables and Set Up User Authentication.
6

Add custom domain when ready

Clone starts on a Hiveku subdomain — add the client’s domain when you’re ready to launch. See Custom Domain.
7

Deploy

Click Deploy to push the cloned site to its new Hiveku subdomain.

​
Verifying the Clone

1

Check the dashboard

Your new project appears with “(Copy)” in the name (unless you already renamed it).
2

Open it

Click the card. The editor loads with all the original’s pages in place.
3

Deploy and visit the subdomain

Click Deploy, then visit https://{new-project-slug}.hiveku.com. The site should match the source visually.

​
Troubleshooting

Check your role on the source project. Owner, Admin, and Member roles can clone. Viewer cannot. Also, some plans limit the number of projects you can own — see Monitor Usage & Costs.
Your plan’s project limit is hit. Upgrade your plan or delete/archive an old project first. See Rename or Delete a Project.
If the source project had images deleted after the clone, shared references break. Re-upload the missing images in the clone’s asset panel.
The clone modal has a toggle for blog posts. If you left it off, blog posts weren’t included. Ask the AI to re-import from the original: “Copy the blog posts from project X into this project.”
That’s by design. Each site needs its own domain — add one to the clone via Custom Domain when you’re ready to launch.

​
What’s Next?

Rename or Delete a Project

Rename the clone and clean up when done

Custom Domain

Point the client’s domain at the new site