Checking Migration Results and Validating Homepage Content

Confirming the migration finished and reviewing the result summary

1. Open the Migration Tool in Sherkety ERP & Website Platform and return to the migration run you just completed. If you came here right after following Running Homepage Migration Workflows, use the same run record instead of starting a new one.

2. Check the final status first. Make sure the run shows Completed. If it still shows Queued, Running, or Failed, do not begin homepage validation yet because the visible content may still be incomplete or inaccurate.

3. Review the result summary on the migration screen. Pay close attention to the counters for:

   • Migrated items
   • Skipped items
   • Failed items

   A completed run can still contain skipped or failed items, so do not assume the homepage is correct just because the status says Completed.

4. Look through any warning or notice area in the results screen. Watch for messages about:

   • missing images or other media
   • unpublished content
   • unresolved links
   • items that could not be matched in the destination site

   These warnings often explain why a homepage section is blank, why a button goes nowhere, or why an image does not appear.

5. Record the details of the run before you move into visual checks. Capture the following so your findings match the correct migration:

Checking the homepage structure after migration

1. Open the destination homepage in Sherkety ERP & Website Platform and scroll from top to bottom without editing anything first. Your goal is to confirm the page structure before checking individual words, images, or links.

2. Compare the visible section order with the expected homepage layout from the source site. Look for major homepage blocks such as:

   • the hero area at the top
   • featured or promotional sections
   • comparison or value sections
   • trust, team, or ecosystem highlights
   • footer callouts and footer content

   If a section is missing entirely, note its position on the page. A missing middle section usually points to a migration or publishing issue, while a missing footer callout may point to shared content that was not brought over.

3. Check for blank spaces where content should appear. A section may technically exist but still be unusable if you see:

   • an empty banner area
   • cards with no text
   • buttons without labels
   • image frames with no image
   • large gaps between sections

4. If you have access to the content editing view, use it to confirm that each homepage section is connected to the correct migrated content. Open the homepage editing area or section list and compare the visible section names with what you expect to see on the live page. This is especially helpful when the page shows the wrong section in the right position.

5. Also check whether any homepage content was intentionally left out because it was hidden, draft, or unpublished before migration. If a section does not appear on the live homepage, but you can see it in editing tools with an unpublished state, treat that as a publishing decision rather than a layout defect.

Inspecting text, links, and media in each homepage section

1. Start at the top of the homepage and inspect one section at a time. Read every visible heading, paragraph, card title, teaser, and button label. Look for common migration problems such as:

   • cut-off text
   • missing line breaks
   • awkward spacing
   • fallback wording that does not belong on the final page
   • mixed-language text where the wrong language appears in one section

2. Test every homepage button and text link. Open each link and confirm it goes to the expected destination. Check:

   • navigation to the correct public page
   • links to the correct ERP app or service page
   • anchor links that jump to the correct section on the same page
   • buttons that should open a contact or next-step path

   If a link opens the wrong page, returns an error, or goes nowhere, note the exact button label so it can be corrected quickly.

3. Review all media in each section. This includes hero images, background visuals, thumbnails, icons, and promotional graphics. Watch for:

   • missing images
   • old images from the source site
   • stretched or badly cropped visuals
   • thumbnails that do not match the related content
   • image descriptions that no longer fit the image

4. Pay extra attention to repeated content blocks such as cards, sliders, featured items, or article lists. Confirm that:

   • the expected number of items appears
   • the order matches the source homepage
   • no duplicate cards are shown
   • each item has the right title, image, and link

Comparing migrated homepage content with the source site

1. Open the source homepage and the destination homepage side by side. This is the fastest way to catch differences that are easy to miss when reviewing one page at a time. Compare the pages from top to bottom in the same scroll order.

2. Match each homepage section visually first. Confirm that the same major blocks appear in both places and in the same sequence. Then compare the details inside each block:

   • section titles
   • supporting text
   • button labels
   • images
   • featured cards or highlighted items

3. When a section looks similar but not identical, verify that the destination page is using the correct migrated content. If the editing area shows titles, slugs, or other identifying labels for content items, use those labels to confirm that the right source entry was brought across. This is especially useful when two sections have similar wording or when older homepage versions still exist.

4. Check dynamic or curated areas carefully. Featured lists, manually selected cards, and promotional blocks may not update correctly if the destination homepage is pointing to the wrong items. Compare the actual items shown on both pages rather than only checking whether the section title matches.

5. Keep a separate note for intentional differences. For example, branding updates, approved wording changes, or legacy sections that were purposely excluded should not be logged as migration defects. Only record unexpected differences that affect what visitors see.

A simple review note can include:

• section name
• source result
• destination result
• issue found
• whether the difference is intentional

Validating what visitors can actually see on the live homepage

1. After checking the editing view, open the published homepage as a visitor would see it. Do not rely only on preview screens. A section can look correct in editing tools and still fail to appear on the live page.

2. Confirm that the homepage is visible without any editor-only access. Open the page in a regular browser tab and review:

   • hero text and main call-to-action buttons
   • section headings and body content
   • images and promotional panels
   • footer callouts and footer links

   If content only appears while you are signed in, that is a visibility problem and should be treated as a publishing issue.

3. Check the homepage on both desktop and mobile-sized views. Resize your browser or use your device to confirm that migrated content still appears in the correct order. Watch for:

   • hidden sections on smaller screens
   • stacked cards appearing in the wrong sequence
   • buttons disappearing below images
   • text overlapping media
   • mobile menus or callouts covering homepage content

4. If recently migrated content does not appear right away, refresh the page and load it again. If your team uses cache clearing after migration, perform that step before logging a defect. Then recheck the same section on the live homepage.

5. Finish by testing the homepage as a public visitor would: scroll the page, open key links, and confirm the main calls to action work without requiring admin access.

Fixing common homepage migration issues

1. If a homepage section is missing, go back to the migration results and confirm that the content item was actually included in the completed run. Then check whether that section is published and assigned to the homepage in the correct position. A migrated section that is not published or not attached to the homepage will not appear on the live page.

2. If text or media looks outdated, compare the visible content with the source homepage and the migration run details. This often means the migration brought over an older version instead of the latest published content. Recheck the source content version before rerunning anything.

3. If links are broken, open the affected section in the editing area and review each button or linked item. Broken links usually come from:

   • page references that were not matched correctly
   • missing destination pages
   • old source links that were carried over
   • links pointing to the wrong language version

4. If images do not display, confirm that the image was imported and still attached to the correct homepage field. A section may show the text correctly while the visual stays blank because the image did not transfer or the section is still pointing to an unavailable file.

5. After each fix, return to the live homepage and test the exact section again. Do not assume one correction fixed the whole page. Recheck the heading, image, buttons, and item order in that section before closing the issue.

Common issue tracking notes:

• section name
• visible problem
• likely cause
• action taken
• retest result

Overview

This document focuses on the review stage after a homepage migration run in Sherkety ERP & Website Platform. At this point, the migration has already been launched and completed, and your job is to confirm that the destination homepage looks correct to real visitors. The main goal is not to rerun the migration, but to validate what actually arrived: section order, visible text, links, images, and repeated content such as cards or featured lists.

Use this guide when a homepage migration shows Completed, but you still need to verify quality. A completed run only tells you the process finished. It does not guarantee that every homepage block is present, every image is attached, or every button opens the right destination page. That is why this review combines the migration results screen with a full visual check of the live homepage.

This guide is especially useful when you need to:

• confirm that the destination homepage matches the source homepage
• identify skipped or failed items that affect visible sections
• catch broken links, missing media, or outdated wording
• verify that public visitors can see the migrated content
• separate true migration defects from intentional content changes

If you need help with launching or managing the migration itself, return to Running Homepage Migration Workflows. If you need broader result review patterns, you can also refer to Reviewing Migration Results and Follow Up Checks. The steps here stay focused on homepage validation and what should be visible after the migration is done.

Prerequisites

Before you start validating homepage content in Sherkety ERP & Website Platform, make sure you have access to the screens and information needed for a proper comparison. You do not need advanced admin knowledge, but you do need enough access to review both the migration outcome and the published homepage.

Prepare the following:

• Access to the Migration Tool so you can open the completed homepage migration run
• Permission to view the destination homepage in its live or published state
• Access to the source homepage for side-by-side comparison
• Access to the homepage editing view if you need to confirm section assignments, publishing state, or linked content
• The correct migration date, source environment, and destination site details for the run you are validating

It also helps to have these items ready before you begin:

• a browser window for the source homepage
• a second browser window or tab for the destination homepage
• a simple note sheet for recording missing sections, broken links, or image problems
• mobile access or a resized browser window for checking smaller screen layouts

Before starting this guide, you should already know how to run the homepage migration workflow. If not, review Running Homepage Migration Workflows first.

Once you finish the checks in this guide and confirm what did or did not migrate correctly, continue with Planning Safe Follow Up Actions After Migration to decide what to fix immediately, what to rerun, and what to document for the next migration cycle.