Edge Delivery pilot: scope and timeline
What the pilot includes, how long it takes, what drives the size of a full migration and what you receive at the end.
The short answer
An Edge Delivery Services pilot with Prolifico takes about three weeks: discover, build and validate. It rebuilds a few pages from your current website, whatever CMS it runs on, and produces working pages, a performance comparison and the data Prolifico uses to estimate a full migration.
What the pilot is
The Edge Delivery pilot rebuilds a few pages from your current website on Edge Delivery Services, so your team can compare speed, Lighthouse scores and authoring on real pages before committing to a full migration. It is designed to answer two questions: how fast could our pages be, and what would a full migration take?
It takes about three weeks, and nothing changes on your live site while it runs.
Your pages can come from any CMS
AEM is not a requirement.
| Where the pages live today | What we need from you | How they reach Edge Delivery |
|---|---|---|
| AEM Sites | The page URLs and, if the content is not public, access to the authoring environment. | Structure and content are rebuilt as Edge Delivery blocks. |
| WordPress, Drupal, Sitecore or another CMS | The page URLs and a content export or access if the pages are not public. | Content is migrated with tooling or rebuilt by hand into blocks. |
| A custom, legacy or hosted platform | The page URLs and the design assets or style guide. | Pages are rebuilt from the rendered design and content. |
| A static or hand-coded site | The page URLs and the source files, if you have them. | Pages are rebuilt as blocks; there is no CMS to migrate from. |
AEM is not required. The pilot works the same way whichever system your pages come from today.
Choosing the pilot pages
A pilot typically uses two representative pages from your current site.
- A mix of types: one content-rich page and one simpler or campaign page, so authoring is tested across kinds of content.
- Your common templates: pages built from the templates you use most, so what we learn applies to many pages.
- A known speed problem or high traffic: where the gains are easiest to see and matter most.
- Light on integrations: pages that do not depend on complex integrations, which belong in the full migration plan.
Week by week
About three weeks end to end.
Week 1: Discover
Workshops to align on goals, select the pages to test and confirm performance targets. We capture a baseline Lighthouse score for each selected page.
Week 2: Build
Prolifico configures the sandbox, rebuilds the selected pages on Edge Delivery Services and sets up authoring with the Universal Editor or document-based editing.
Week 3: Validate
Your team works with the pages and we compare performance and authoring side by side, review the business impact with leadership and outline the roadmap and estimate for a full migration.
What is in scope, and what is not
| In scope | Not in scope |
|---|---|
| A small set of pages from your current site, typically two, rebuilt on Edge Delivery Services. | A full production migration. |
| Authoring set up with Universal Editor or document-based editing. | Custom integrations beyond the selected pages. |
| A performance comparison before and after. | Content or design changes beyond the pilot pages. |
| Environment access for up to three weeks after implementation. | Ongoing support. That is a separate service. |
How the pilot is judged
Agreed in discovery, so everyone knows what a good result looks like.
| Measure | How it is measured |
|---|---|
| Performance | Google Lighthouse score and Core Web Vitals for each page, before and after, side by side. |
| Authoring | How long it takes your authors to create or update a page, and what they say about the experience. |
| Parity | Whether content, structure and tracking match the original pages. |
| Feasibility | Which components and templates become blocks, and what turns out to be hard. |
| Effort | How long each page takes to rebuild, which feeds the migration estimate. |
What we need from you
A small team, for a short time.
| Who | What they do |
|---|---|
| Sponsor | Agrees the goals and attends the results review. |
| Web owner | Chooses the pages, provides the URLs and any access needed. |
| Content authors | Two or three authors try the rebuilt pages and give feedback in week 3. |
| Design or brand | Shares the style guide or design files, if they exist. |
| Analytics | Names the events and reports that must match the original pages. |
What drives the size of a full migration
These are the factors Prolifico uses to turn pilot results into an estimate.
| Driver | Why it matters |
|---|---|
| Templates and blocks | Each distinct template and component becomes a block to build and test. |
| Content volume | More pages mean more migration and review, even with tooling. |
| Integrations | Forms, search, commerce and personalization each need a plan. |
| Analytics and SEO parity | Tracking and redirects have to match before cutover. |
| Languages and regions | Each adds content and review. |
| Authoring change | More authors and tools mean more training. |
What you receive
- Working pilot pages on Edge Delivery Services.
- A before and after performance comparison.
- Author feedback on the editing experience.
- A phased migration plan and a proposal for the full migration, based on what the pilot showed.
- A walk-through of the environment for your team.
After the pilot: your options
Move forward
Turn the pilot into a phased migration plan and start with the pages that matter most.
How migration worksGo further
Extend the pilot to more templates or a second brand before you commit.
Pause with evidence
Keep the performance and authoring results to build your business case.
Keep exploring.
Want to see your pages on Edge Delivery?
Generate a proposal or talk to our team about your pilot.
Frequently asked questions
How long does an Edge Delivery proof of concept take?
About three weeks: discovery, a quick build of the selected pages, and validation with your team. The environment stays available for hands-on use for up to three weeks afterward.
Can we pilot pages from a CMS other than AEM?
Yes. Pages can come from AEM Sites, any other CMS, or a static or custom site. Prolifico rebuilds the selected pages on Edge Delivery Services, so AEM is not required.
What is included in an Edge Delivery pilot?
A small set of pages from your current website, typically two, rebuilt on Edge Delivery Services, authoring set up for your team, a before and after performance comparison and a roadmap for a full migration.
How do we choose the pages for the pilot?
Pick a mix of content types built from your common templates, ideally with a known speed problem or high traffic, and without complex integrations. Prolifico helps select them in the first week.
How do we get a migration estimate?
The pilot produces the data for it. Prolifico uses the results to estimate the full migration and creates a proposal that reflects what the proof of concept showed.
What affects the cost of an Edge Delivery migration?
The number of templates and blocks, content volume, integrations, analytics and SEO parity, languages and regions, and the amount of authoring change.
Do we need AEM Sites to run the pilot?
No. If you are considering AEM Sites as your CMS, Prolifico can also run a proof of concept of AEM Sites with Edge Delivery Services. See the AEM Sites POC.
How much does an AEM proof of concept cost?
The AEM Sites proof of concept is no charge and takes about 6 weeks. The Edge Delivery Services proof of concept is no charge and takes about 3 weeks. The AEM Assets proof of concept is $10,000, a one-time fixed fee, over about 4 weeks. A combined AEM Sites and Assets proof of concept is $10,000 over about 6 weeks. What affects the price: Whether the proof of concept covers AEM Sites, AEM Assets, Edge Delivery Services, or a combination. Generate a POC proposal.