Content migration is where website projects lose time and money.
Page lists, briefs, content and sign-off all live in different places, so the programme slips in the part nobody budgeted for. Blueprints holds all four in one plan, built from an audit you have already agreed.
Someone rebuilds the page list in a spreadsheet. Someone else chases copy and images across email and shared drives. Briefs get written twice, and sign-off drifts because nobody can see what is still outstanding. By the time the build team is handed the plan, it has aged.
Up to 20 days
of content migration production time given back, according to clients who have run a migration with us.
One plan
in place of a page spreadsheet, a brief document, an asset folder and a sign-off email thread.
Nothing built twice
audit decisions, structure, briefs and handover all read from the same plan, so a change lands everywhere.
Five steps, in the order your studio already works. Each one hands the next a decision that has been made rather than a question that is still open.
Keep, rewrite and remove decisions come straight from the audit your client has already signed off, each one still linked to the page it came from.
Instead of rebuilding the page list by hand.
Drag pages into the new shape, rename, merge and group them, then lock it. Every move is logged, and versions worth returning to can be saved.
Instead of three competing site maps in three file formats.
Each page carries its sections, the words each one needs with length guidance, and a completeness score. Images and documents are collected from the pages they sit on.
Instead of chasing copy and assets across email and shared drives.
Give every page an owner and a reviewer, leave comments where they belong, and run a review flow you can rename to match how your studio works.
Instead of guessing which pages are still with the client.
One pack for the build team: the site map, the redirect list, a brief per page, the repeatable content and the menus, all reflecting what was approved.
Instead of a handover call and a folder of good intentions.
Blueprints reads the same brand profile, voice and personas that govern the rest of BrandHalo. Briefs and first drafts arrive already shaped by how the brand sounds, so writers spend their time on judgement rather than set-up.
BrandHalo is not a content factory. It is the governance layer around the work: the plan holds the standard, and people hold the approval.
When the plan is approved, the build team gets everything at once, in the formats they asked for.
The agreed structure page by page, with the type and status of each one.
Every removed or merged page mapped to where it should now go, so old links keep working.
Sections, copy and guidance, as a PDF for the client or a spreadsheet for the build team.
People, locations, services and articles in one grid, checked before it goes anywhere.
Main, utility and footer menus with the order and nesting already decided.
Compare the finished site against the approved plan and get a list of what did not make it.
Straight into the build
Approved content can be pushed into Contentful. Sanity, WordPress and Drupal builds get a mapped specification your developers can work from, so nothing is retyped.
Data sovereignty (AU, EU, US) · Enterprise SSO · Privacy-first architecture · No lock-in
Bring the audit you have already agreed, and let production start from a plan everyone can see.
Blueprints is part of the Enterprise plan and is currently in preview.