Bulk migration for agencies (upcoming)
Bulk migration is being built for members of the agency programme. The steps below are the intended steps and may change before release.
If you look after many websites, you do not want to start them one at a time. Bulk migration takes a spreadsheet of website addresses and builds a preview of each site for you, in the background, over hours or days.
Who can use it
Members of the agency programme. The Agency section appears in your workspace once your account is enrolled. If you are not enrolled, the section explains how to apply.
What you upload
A CSV file with one row per website and a header row. The columns:
| Column | Required | What it holds |
|---|---|---|
url | Yes | The website address to migrate, for example https://example.com |
provider | No | The platform the site is on today, if you know it |
template_id | No | For a redesign onto a template: the template to use for that row |
Up to 5,000 rows per file. Rows without a usable address are listed as Skipped with the reason, so nothing disappears silently. A site that appears twice in the file is built once.
What happens
- Every row becomes a project in All Projects, exactly as if you had started it yourself.
- Wigoh builds a limited number of sites at a time and moves through the list. A large file takes days; you can close the browser and come back.
- The batch page shows how many sites are queued, building, finished, failed and skipped, and lists every row with its status.
- One site failing does not stop the others. Failed rows are marked and can be retried.
- You can Cancel a batch. Sites already built stay; queued rows are left untouched.
Each finished site is an ordinary Wigoh project: open it, edit it with the assistant, buy a plan for it and take it live, one at a time, as described in Go live.
What it builds
The first version builds the home page of each site, the same as a single migration does today. Redesigning every site onto one template is planned next; the template_id column is there for it.