A Sitecore site carries years of structured content, personalisation rules, forms, integrations and URLs that search engines trust. A WordPress agency that is excellent at new builds may never have had to move all of that at once. These questions help you find out before you sign.
About the content and data
- How will you map our Sitecore templates and fields to WordPress? Can we see an example field map?
- Will content move by script or by hand, and how many times will you rehearse the migration before launch?
- How do you handle media, multilingual content and multiple sites in one Sitecore instance?
About search and URLs
- How will you capture every indexed URL, and will every one get a redirect?
- How do you test redirects before launch, and what do you monitor in the weeks after?
About integrations and features
- Which of our Sitecore features do you recommend dropping, and why?
- How will our CRM, search, single sign-on and forms connect to WordPress?
- What happens to personalisation, and to the analytics history held in xDB?
About the project
- Who will run the project day to day, and will we meet them before we sign?
- What does the cutover weekend look like, and what is the rollback plan if it goes wrong?
If an agency can't show you a field map and a redirect plan before build, they will be writing them during it.
Red flags
- A fixed price before anyone has looked at your content tree
- Plans to rebuild every Sitecore feature, whether you use it or not
- A redirect plan that covers top pages only
- No named person who will run the project
We start Sitecore migrations with a Migration Blueprint: three weeks to audit what you use, map the content and URLs, and give you a costed plan. It's yours to take to any agency, so it's also a fair way to compare suppliers.
Shortlisting migration partners?
Book a free 30-minute call with the person who would run your project. You'll get a straight answer on what it involves, how long it takes and roughly what it costs.



