Enterprise sites, migrated without the risk.
Our enterprise team moves large marketing sites onto a platform your team can run, and engineers the applications around them. The security review, access model and procurement paperwork are part of the scope, not a conversation six weeks after kickoff.
Delivered by our enterprise team. Until Terminal’s general release.
Terminal is in public alpha, and enterprise work runs through one team end to end. Its general release adds a choice of who builds, not a change in how the work is scoped.
-
One accountable team, today.
While Terminal is in public alpha, every enterprise build is scoped, engineered and supported by our enterprise team, from the first audit to the last redirect.
Public alpha
-
A marketplace of creators.
When Terminal reaches general availability, a marketplace of creators who build on it opens alongside the release, and you choose who delivers the work.
General availability
-
Our internal team stays on the list.
Our internal development team is one of the creators you can choose, so a build that starts with the enterprise team can stay with it.
Either way
Three meetings, answered before they happen.
Enterprise migrations stall in the same three conversations. Each one is part of the scope here, not a surprise halfway through the build.
-
Who publishes, decided up front.
Roles, review steps and publishing rights are written into the scope and set up as part of the build, so a marketer can change a page without anyone wondering what else moved.
Governance
-
Your questionnaire, answered in scoping.
We complete your security questionnaire as part of scoping, at no cost. Our own practices, and what we do not have yet, are published for your team to read first.
Read the security practicesSecurity
-
Content modelled for how you publish.
Collections, reference fields and localization are designed around how your team works, and every existing URL gets a mapped redirect so search traffic survives the move.
Content at scale
How the migration runs. Nothing goes dark.
Your current site keeps serving traffic the whole time. The new build runs on its own staging link, where every old address is mapped to its new page and tested, and nothing is cut over until the replacement is signed off.
Add a redirect
Applies immediately — redirects are routing, not content, so no republish.
Active redirects
- /about-us→ /about 301
- /services/estate-planning→ /practice/estate-planning 301
- /team→ /people 301
-
Audit what you actually have
We inventory every template, page, integration and redirect on the current site, then find out what is genuinely in use. Large sites carry years of pages nobody opens, and knowing which ones they are keeps the rebuild scope honest.
-
Model the content properly
Collection structure, reference fields and localization get designed around how your team publishes, not around how the old CMS forced you to work. It is the decision that decides whether a new hire can ship a landing page in an afternoon two years from now.
-
Build in parallel, then cut over
The new site goes up on a staging domain while the current one keeps serving traffic, with weekly demos so there is no reveal at the end. Cutover covers DNS, redirect mapping, analytics continuity and access handover, followed by 60 days of support.
Questions procurement will ask.
Answered here so this page can be forwarded to your legal, IT and finance teams as it is.
- Who delivers an enterprise build?
- Our enterprise team. While Terminal is in public alpha, every enterprise build is scoped, engineered and supported by that team directly. When Terminal reaches general availability, a marketplace of creators opens alongside it, and you choose who builds with you, including our internal development team.
- Can you complete our security questionnaire?
- Yes, as part of scoping and at no cost. Our current practices, including what we do not have yet, are documented on the security page. Security practices
- Do you sign an MSA and an NDA?
- Yes. Our standard Master Services Agreement is public, and we are equally willing to work under your paper instead. Read the MSA
- How are enterprise engagements priced?
- Applications start at $15,000 and enterprise engagements are scoped individually. You receive a fixed written figure before anything is committed.
- Who owns the code and the data?
- You do, in full, from the first commit. Repositories, infrastructure and accounts transfer to your organisation at handover, with no ongoing dependency on us.
- How do you handle data residency?
- We scope it before building. Where a region is required, the proposal names the hosting that meets it, or says plainly that we cannot.
Tell us what you're working with.
The more detail here, the more useful the first conversation. You get a reply within one business day, and a scoped plan or an honest answer that the move is the wrong fit.
Thank you. Your brief has been received.
We reply within one business day, including when the answer is no. If nothing arrives, check your spam folder and then write to support@stacklumen.com.