<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: harsha tiwari</title>
    <description>The latest articles on DEV Community by harsha tiwari (@harsha_tiwari_781ecd8a91a).</description>
    <link>https://dev.to/harsha_tiwari_781ecd8a91a</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4249762%2F7151ccfe-1c31-44be-b397-a53d5b5d0f55.png</url>
      <title>DEV Community: harsha tiwari</title>
      <link>https://dev.to/harsha_tiwari_781ecd8a91a</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/harsha_tiwari_781ecd8a91a"/>
    <language>en</language>
    <item>
      <title>Seven things that break XP to Sitecore AI migration Estimates- Part 2</title>
      <dc:creator>harsha tiwari</dc:creator>
      <pubDate>Wed, 18 Nov 2026 05:36:34 +0000</pubDate>
      <link>https://dev.to/harsha_tiwari_781ecd8a91a/seven-things-that-break-xp-to-sitecore-ai-migration-estimates-part-2-32db</link>
      <guid>https://dev.to/harsha_tiwari_781ecd8a91a/seven-things-that-break-xp-to-sitecore-ai-migration-estimates-part-2-32db</guid>
      <description>&lt;p&gt;Part 2 of the series. Custom code with nowhere to go, personalization nobody uses, the CDN nobody asked about, and the parallel run that is always missing.&lt;/p&gt;

&lt;p&gt;In my last article I covered the first three gaps I keep finding in XP to SitecoreAI migration estimates: site count, rendering variants and content volumes. If you haven't read it, start there, as the same approach applies here. Connect to the XP CM with Sitecore PowerShell Extensions, pull the real numbers, and only then estimate.&lt;/p&gt;

&lt;p&gt;Let's look at the remaining four.&lt;/p&gt;

&lt;h2&gt;
  
  
  Custom pipelines and computed fields with nowhere to go
&lt;/h2&gt;

&lt;p&gt;This is the one that catches people who know XP well. In SitecoreAI there is no CD tier for you to run, no xDB, no delivery side Solr that you own, and no request time pipeline on delivery. Any customization that lived in those places has to be redesigned, moved to the front end, or dropped.&lt;/p&gt;

&lt;p&gt;To find custom pipeline processors (anything outside the Sitecore.* namespace):&lt;/p&gt;

&lt;p&gt;$config = [Sitecore.Configuration.Factory]::GetConfiguration()&lt;br&gt;
$config.SelectNodes("//pipelines//processor[@type]") |&lt;br&gt;
    Where-Object { $&lt;em&gt;.type -notlike "Sitecore.*" } |&lt;br&gt;
    Select-Object @{ n = "Pipeline"; e = { $&lt;/em&gt;.ParentNode.Name } },&lt;br&gt;
                  @{ n = "Type";     e = { $_.type } }&lt;/p&gt;

&lt;p&gt;To find computed index fields:&lt;/p&gt;

&lt;p&gt;$cs = [Sitecore.Configuration.Factory]::GetConfigNode("contentSearch")&lt;br&gt;
$cs.SelectNodes(".//fields[@hint='raw:AddComputedIndexField']/field") |&lt;br&gt;
    Select-Object @{ n = "Field"; e = { $&lt;em&gt;.fieldName } },&lt;br&gt;
                  @{ n = "Type";  e = { $&lt;/em&gt;.InnerText.Trim() } }&lt;/p&gt;

&lt;p&gt;Treat every row as a line item. For example:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;1. A httpRequestBegin processor doing redirects may move to the front end or to the CDN.
2. A computed field feeding site search needs a redesign for Sitecore Search, where content comes in through crawlers or the ingestion API, not your own indexing code. On one prototype I worked on, the search redesign was the real effort. The pages were the easy part.
3. XP era lines like CD hardening, Solr upgrades and xDB sizing should come out of the estimate. I still see them copied from the last XP project.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;While you are here, confirm the Sitecore Search tier. An entry level appears to be included with the SitecoreAI subscription, but it can vary by deal. Get it confirmed by the account team before adding or removing a search workstream.&lt;/p&gt;

&lt;h2&gt;
  
  
  Personalization that nobody checked
&lt;/h2&gt;

&lt;p&gt;xDB, Experience Profile, EXM and the XP rules engine do not carry over. So the question "do we need CDP and Personalize?" comes up in every migration. Very often the honest answer is that personalization was bought but is barely used.&lt;/p&gt;

&lt;p&gt;Check the layout fields for personalization rules:&lt;/p&gt;

&lt;p&gt;Get-ChildItem -Path "master:/sitecore/content/" -Recurse |&lt;br&gt;
    Where-Object {&lt;br&gt;
        $&lt;em&gt;["&lt;/em&gt;&lt;em&gt;Renderings"] -match "&amp;lt;rls" -or $&lt;/em&gt;["__Final Renderings"] -match "&amp;lt;rls"&lt;br&gt;
    } |&lt;br&gt;
    Select-Object Name, ItemPath&lt;/p&gt;

&lt;p&gt;If it returns a handful of pages, personalization is a small rebuild or a phase two conversation. If it returns hundreds, it is a proper scope item with a licensing question attached.&lt;/p&gt;

&lt;p&gt;There are alsodata questions which is not technical. What happens to historical xDB contacts and interactions? Keep, export or purge? That is a decision for the client's data protection officer. Raise it early, as the answer decides whether you need a data export task at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which CDN is actually in front?
&lt;/h2&gt;

&lt;p&gt;In a RFP we need to know  the CDN,  The CDN in front of an XP site often holds redirect rules, geo logic and header rewrites, and all of that needs a new home.&lt;/p&gt;

&lt;p&gt;Check this using :&lt;/p&gt;

&lt;p&gt;Resolve-DnsName &lt;a href="http://www.example.com" rel="noopener noreferrer"&gt;www.example.com&lt;/a&gt; | Select-Object Name, Type, NameHost&lt;/p&gt;

&lt;p&gt;(Invoke-WebRequest -Uri "&lt;a href="https://www.example.com" rel="noopener noreferrer"&gt;https://www.example.com&lt;/a&gt;" -Method Head).Headers&lt;/p&gt;

&lt;p&gt;A CNAME ending in edgekey.net or akamaiedge.net points to Akamai. Headers like Server, Via, X-Cache or CF-Ray usually tell you the rest. Then ask the client what rules live there and add a line for moving them.&lt;/p&gt;

&lt;h2&gt;
  
  
  The parallel run, and the estimate's own sanity checks
&lt;/h2&gt;

&lt;p&gt;Every phased migration keeps XP running for some time as a fallback. That means hosting, licences, monitoring and someone who can still deploy to it. In every estimate version I reviewed this year, this cost was missing. Not underpriced, missing.&lt;/p&gt;

&lt;p&gt;And if someone wants an AI productivity saving in the estimate, show it as a range, mark it as an assumption and tie it to a pilot sprint. You will have to defend that number in the room.&lt;/p&gt;

&lt;p&gt;To sum up the series, before sending an XP to SitecoreAI estimate:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;1. Confirm the real site list in writing.
2. Count rendering variants and Scriban templates, and drop unused renderings.
3. Pull item counts per language, media size and unreferenced media.
4. List custom pipeline processors and computed index fields, and confirm the Search tier.
5. Check if personalization is actually used, and ask the DPO about xDB data.
6. Find out which CDN is in front and what rules it holds.
7. Price the parallel run, and check QA percentage and contingency.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;Half a day with SPE and a few awkward questions. That is the difference between an estimate we can defen.&lt;/p&gt;

</description>
      <category>sitecore</category>
      <category>xmcloud</category>
      <category>powershell</category>
      <category>architecture</category>
    </item>
    <item>
      <title>Seven things that break XP to Sitecore AI migration Estimates- Part 1</title>
      <dc:creator>harsha tiwari</dc:creator>
      <pubDate>Wed, 18 Nov 2026 04:56:55 +0000</pubDate>
      <link>https://dev.to/harsha_tiwari_781ecd8a91a/seven-things-that-break-xp-to-sitecore-ai-migration-estimates-part-1-51fb</link>
      <guid>https://dev.to/harsha_tiwari_781ecd8a91a/seven-things-that-break-xp-to-sitecore-ai-migration-estimates-part-1-51fb</guid>
      <description>&lt;p&gt;Before you put a number on an XP to SitecoreAI migration, spend half a day with the actual instance. Part 1 covers sites, renderings and content volumes.&lt;/p&gt;

&lt;p&gt;A migration estimate is only as good as the inventory behind it. Most of this year I have been writing and reviewing estimates for moving Sitecore XP solutions to XM Cloud, now SitecoreAI. And one thing I noticed is that the spreadsheet usually looks fine, until someone opens the real Sitecore instance.&lt;/p&gt;

&lt;p&gt;So now, before estimating, I connect to the XP CM with Sitecore PowerShell Extensions (SPE) and pull the numbers myself. In this two part series I want to share the seven gaps I kept finding, along with the scripts I use to catch them. Let's look at the first three.&lt;/p&gt;

&lt;p&gt;All scripts below are read-only. Even so, run them on a non-production CM or a recent copy of master. Replace  and  with your own paths.&lt;/p&gt;

&lt;h2&gt;
  
  
  Site count taken from the database list
&lt;/h2&gt;

&lt;p&gt;On one estimate the scope said well over a dozen sites. The actual number was a handful. Somebody had counted the SQL databases (core, master, web, xConnect pools, forms and so on) and used that as the site count. Every downstream line, be it content migration, front-end build or QA, got multiplied by the wrong number.&lt;/p&gt;

&lt;p&gt;The fix is simple. Let Sitecore tell you how many sites there are.&lt;/p&gt;

&lt;p&gt;For SXA sites, list the site definitions:&lt;/p&gt;

&lt;p&gt;Get-ChildItem -Path "master:/sitecore/content/" -Recurse |&lt;br&gt;
    Where-Object { $&lt;em&gt;.TemplateName -eq "Site Definition" } |&lt;br&gt;
    Select-Object Name,&lt;br&gt;
        @{ n = "SiteName"; e = { $&lt;/em&gt;["SiteName"] } },&lt;br&gt;
        @{ n = "HostName"; e = { $_["HostName"] } },&lt;br&gt;
        ItemPath&lt;/p&gt;

&lt;p&gt;For config based sites:&lt;/p&gt;

&lt;p&gt;[Sitecore.Sites.SiteManager]::GetSites() |&lt;br&gt;
    Where-Object { $&lt;em&gt;.Properties["rootPath"] -like "/sitecore/content/*" } |&lt;br&gt;
    Select-Object Name,&lt;br&gt;
        @{ n = "RootPath"; e = { $&lt;/em&gt;.Properties["rootPath"] } },&lt;br&gt;
        @{ n = "HostName"; e = { $_.Properties["hostName"] } }&lt;/p&gt;

&lt;p&gt;The rootPath filter removes system sites like shell, login and admin.&lt;/p&gt;



&lt;p&gt;Add this output to the estimate as an appendix and get the client to confirm it in writing. It is a ten minute exercise and it can move the estimate by months.&lt;/p&gt;
&lt;h2&gt;
  
  
  Rendering variants not counted
&lt;/h2&gt;

&lt;p&gt;If you have worked on SXA, you know a lot of the presentation logic lives in rendering variants, and on newer versions in Scriban. When moving to headless, every meaningful variant becomes rebuild work in Next.js or the ASP.NET Core SDK. I reviewed one sizing where the variant count was zero. On a mature SXA site that is never the case.&lt;/p&gt;

&lt;p&gt;Count variants per rendering, and Scriban templates separately:&lt;/p&gt;

&lt;p&gt;$root = "master:/sitecore/content///Presentation/Rendering Variants"&lt;br&gt;
$all  = Get-ChildItem -Path $root -Recurse&lt;/p&gt;

&lt;p&gt;Variants per rendering&lt;br&gt;
$all | Where-Object { $&lt;em&gt;.TemplateName -eq "Variant Definition" } |&lt;br&gt;
    Group-Object { $&lt;/em&gt;.Parent.Name } |&lt;br&gt;
    Sort-Object Count -Descending |&lt;br&gt;
    Select-Object @{ n = "Rendering"; e = { $_.Name } }, Count&lt;/p&gt;

&lt;p&gt;Scriban templates&lt;br&gt;
($all | Where-Object { $_.TemplateName -eq "Scriban" }).Count&lt;/p&gt;

&lt;p&gt;Do confirm the template names on your SXA version before running this.&lt;/p&gt;

&lt;p&gt;The other half is custom renderings. The list is almost always longer than what the site actually uses. Here is how to find renderings nothing points at:&lt;/p&gt;

&lt;p&gt;Get-ChildItem -Path "master:/sitecore/layout/Renderings/Project" -Recurse |&lt;br&gt;
    Where-Object { $&lt;em&gt;.TemplateName -in @("Controller rendering", "View rendering") } |&lt;br&gt;
    ForEach-Object {&lt;br&gt;
        [pscustomobject]@{&lt;br&gt;
            Rendering = $&lt;/em&gt;.Name&lt;br&gt;
            UsedBy    = @(Get-ItemReferrer -Item $_).Count&lt;br&gt;
        }&lt;br&gt;
    } | Sort-Object UsedBy&lt;/p&gt;

&lt;p&gt;A few things to note:&lt;/p&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;1. Run it for the Feature folder as well if your renderings live there.
2. Get-ItemReferrer reads the link database, so rebuild it first if you are not sure it is current.
3. Anything with UsedBy as 0 is a candidate to drop. Agree it with the client and record the decision.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;
&lt;p&gt;Once you have the final list, rate each rendering simple, medium or complex by looking at a real page that uses it. A complexity split decided without opening the renderings is just a guess.&lt;/p&gt;
&lt;h2&gt;
  
  
  Content and media volumes left as "TBC"
&lt;/h2&gt;

&lt;p&gt;At RFP stage the client often can't share item counts or media size. But if you have access to an instance, you can get them in a few minutes.&lt;/p&gt;

&lt;p&gt;Items per language:&lt;/p&gt;

&lt;p&gt;Get-ChildItem -Path "master:/sitecore/content/" -Recurse -Language * |&lt;br&gt;
    Group-Object { $&lt;em&gt;.Language.Name } |&lt;br&gt;
    Select-Object @{ n = "Language"; e = { $&lt;/em&gt;.Name } }, Count&lt;/p&gt;

&lt;p&gt;Media library size, and how much of it is actually referenced:&lt;/p&gt;

&lt;p&gt;$media = Get-ChildItem -Path "master:/sitecore/media library" -Recurse |&lt;br&gt;
    Where-Object { $_["Size"] }&lt;/p&gt;

&lt;p&gt;$totalGB = ($media | ForEach-Object { [long]$_["Size"] } |&lt;br&gt;
    Measure-Object -Sum).Sum / 1GB&lt;/p&gt;

&lt;p&gt;$orphans = $media | Where-Object { -not (Get-ItemReferrer -Item $_) }&lt;/p&gt;

&lt;p&gt;"Media items: {0}  Total: {1:N1} GB  Unreferenced: {2}" -f `&lt;br&gt;
    $media.Count, $totalGB, $orphans.Count&lt;/p&gt;



&lt;p&gt;On a large library, narrow the path, for example to /sitecore/media library/Project. The unreferenced count is the interesting one. If a good portion of the library is not linked from anywhere, you can propose leaving it behind and reduce migration effort straight away.&lt;/p&gt;

&lt;p&gt;If you really can't get access, write the volumes as an assumption with a range, like "up to N items across M languages and up to X GB of media", and price that range. A silent assumption becomes your problem later.&lt;/p&gt;

&lt;p&gt;In &lt;a href="https://dev.to/harsha_tiwari_781ecd8a91a/seven-things-that-break-xp-to-sitecore-ai-migration-estimates-part-2-32db"&gt;Part 2&lt;/a&gt; I will cover the remaining four: custom pipelines and computed index fields, personalization, the CDN in front of the site, and the parallel run cost that keeps going missing.&lt;/p&gt;

&lt;p&gt;Read more:&lt;br&gt;
&lt;/p&gt;
&lt;div class="crayons-card c-embed text-styles text-styles--secondary"&gt;
    &lt;div class="c-embed__content"&gt;
      &lt;div class="c-embed__body flex items-center justify-between"&gt;
        &lt;a href="https://doc.sitecorepowershell.com/" rel="noopener noreferrer" class="c-link fw-bold flex items-center"&gt;
          &lt;span class="mr-2"&gt;doc.sitecorepowershell.com&lt;/span&gt;
          

        &lt;/a&gt;
      &lt;/div&gt;
    &lt;/div&gt;
&lt;/div&gt;
&lt;br&gt;
&lt;div class="crayons-card c-embed text-styles text-styles--secondary"&gt;
    &lt;div class="c-embed__content"&gt;
        &lt;div class="c-embed__cover"&gt;
          &lt;a href="https://doc.sitecore.com/sai" class="c-link align-middle" rel="noopener noreferrer"&gt;
            &lt;img alt="" src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdoc.sitecore.com%2Fapi%2Fog%3Ftitle%3DSitecoreAI%26logo%3Dhttps%253A%252F%252Fdelivery-sitecore.sitecorecontenthub.cloud%252Fapi%252Fpublic%252Fcontent%252F9d5e81514f3a438990f5d3b43c557e4c%253Fv%253Df2bb1e8d" height="630" class="m-0" width="1200"&gt;
          &lt;/a&gt;
        &lt;/div&gt;
      &lt;div class="c-embed__body"&gt;
        &lt;h2 class="fs-xl lh-tight"&gt;
          &lt;a href="https://doc.sitecore.com/sai" rel="noopener noreferrer" class="c-link"&gt;
            SitecoreAI | Sitecore Documentation
          &lt;/a&gt;
        &lt;/h2&gt;
          &lt;p class="truncate-at-3"&gt;
            Access the latest documentation for SitecoreAI, an enterprise-grade agentic platform designed to accelerate content creation, personalization, and digital experience management across the Sitecore ecosystem.
          &lt;/p&gt;
        &lt;div class="color-secondary fs-s flex items-center"&gt;
            &lt;img alt="favicon" class="c-embed__favicon m-0 mr-2 radius-0" src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdelivery-sitecore.sitecorecontenthub.cloud%2Fapi%2Fpublic%2Fcontent%2F9d5e81514f3a438990f5d3b43c557e4c%3Fv%3Df2bb1e8d" width="270" height="270"&gt;
          doc.sitecore.com
        &lt;/div&gt;
      &lt;/div&gt;
    &lt;/div&gt;
&lt;/div&gt;


</description>
      <category>sitecore</category>
      <category>xmcloud</category>
      <category>powershell</category>
      <category>architecture</category>
    </item>
  </channel>
</rss>
