Reviewing Migration Results and Post Migration Checks

Opening the completed migration task and locating the result details

After you run a homepage migration, stay in the Migration Tool area and return to the list of migration tasks. Look for the row that shows the homepage migration you just finished. The most important thing to check first is the visible status on that row. Open the task whose status shows that it has finished, completed, or ended with a result you need to review.

1. Sign in to Sherkety ERP & Website Platform and open the Migration Tool screen.
2. In the task list, find the homepage migration you want to review.
3. Check the visible status before opening it. A completed task may still contain warnings, so do not assume everything transferred correctly just because the run has ended.
4. Click the task row to open its result details.

On the task details screen, focus on the summary area at the top first. This area usually gives you the clearest picture of the migration run before you inspect individual items. Look for:

• A clear status indicator
• A visible completion state
• Any counts that show how many items were processed
• A results area with messages, warnings, or errors

Before leaving this screen, scroll through the full result details. If Sherkety ERP & Website Platform shows item-by-item results, read those entries carefully. A task can finish successfully overall while still skipping a banner, failing to move an image, or leaving a link unchanged. If you see validation notes or warning text, keep the task open while you compare those notes with the homepage itself.

If you need a refresher on what the migration was intended to do, refer back to Understanding Homepage Migration Tool Purpose and Scope rather than repeating the setup review here.

Interpreting the visible migration results on the task screen

Once the task details are open, read the results from top to bottom instead of jumping straight to the homepage. The result screen tells you what Sherkety ERP & Website Platform believes happened during the migration, and that helps you know what to verify next.

1. Start with the result summary at the top of the task screen.
2. Note any visible totals for migrated homepage items, content entries, or settings that were included in the run.
3. Review row-level results if the screen lists individual migrated items.
4. Read every warning or error message before moving on to homepage checks.

Common result labels are usually enough to guide your review:

• Created means a new item was added in the destination homepage content.
• Updated means an existing item was changed.
• Skipped means the migration left that item alone, often because it was already present or did not meet the migration rules.
• Failed means the item did not transfer correctly and needs follow-up.

A completed task with several Updated or Created entries is usually a good sign, but you still need to compare those entries with the live homepage. A task with Skipped items deserves closer attention, especially if those skipped items match missing sections you later notice on the page. A Failed label should be treated as a direct clue for what to inspect first.

If the results area shows warning text, read it literally and match it to what you see on the homepage. For example, a warning tied to media should make you check banners, icons, or image blocks first. If the screen includes a completion time, item timestamps, or source-to-destination details, record them while reviewing. Those details help you confirm that you are checking the correct migration run and not an older one.

Checking homepage content after the migration finishes

After reviewing the task results, open the homepage and confirm that the migrated content is actually visible to visitors. This is the most important post-migration check because a clean result screen does not always guarantee that every homepage section displays correctly.

1. Open the homepage in Sherkety ERP & Website Platform immediately after the migration finishes.
2. Start at the top of the page and move downward section by section.
3. Compare what you see with the expected homepage content from the migration plan or the source homepage.
4. Refresh the page and check the same sections again.

Focus on the homepage areas that are most likely to be affected by migration:

• Hero banners and headline text
• Featured service tiles
• Comparison or promotional sections
• Startup package highlights
• Trust indicators
• Team or ecosystem sections
• Contact prompts and call-to-action buttons
• Footer content if it was part of the migration scope

Check whether each section appears in the expected order. A section that exists but appears lower on the page than expected may point to a content ordering issue rather than a missing item. Also confirm that key text is complete. Watch for shortened headlines, empty cards, missing button labels, or repeated blocks that suggest the migration only partially applied.

Refresh the homepage once after your first pass. If a section appears only after refresh, or disappears between views, note that behavior in your follow-up record. Revisit the migrated sections one more time and confirm that the content is stable and fully rendered. If you already reviewed expected outcomes in earlier migration guidance, use Checking Migration Results and Validating Homepage Content for a deeper comparison approach while keeping this review focused on post-migration confirmation.

Validating links, media, and layout on the migrated homepage

After confirming that the homepage sections are present, test how they behave. A migration can move visible content successfully while still leaving broken links, missing images, or layout problems that only appear when you interact with the page.

1. Click each migrated homepage button, text link, and featured navigation entry.
2. Confirm that each one opens the expected destination page.
3. Review every visible image, banner, icon, and media area for loading problems.
4. Scan the page for layout changes such as spacing issues, broken alignment, or cards appearing in the wrong order.

Pay close attention to call-to-action areas. If the homepage includes buttons for service pages, ERP pages, company type guidance, contact actions, or demo requests, open each one and make sure it leads to the correct destination. If a button opens the wrong page, opens nothing, or returns you to an unexpected section, note the exact button text and where it appears on the homepage.

For media checks, look for:

• Blank image spaces
• Placeholder-style image areas
• Cropped banners
• Missing icons
• Sections where text appears but the visual element does not load

Layout review matters just as much as content review. Compare the migrated homepage with the expected arrangement. Watch for uneven spacing between sections, cards wrapping awkwardly, banners overlapping text, or a featured block appearing before another section that should come first. These issues often become obvious only when you scroll through the full page.

If the homepage includes featured announcements or promotional blocks, make sure they still look clickable and complete. A button with missing text, a card with no image, or a section with shifted spacing should be treated as a migration issue even if the task itself shows as completed.

Recording issues that need follow-up after reviewing the results

When you find a problem, record it while the migration task details and the homepage are still open. Good notes make it much easier to match a visible homepage issue to the exact migration result that caused it.

Start by capturing the basic task information from the migration result screen:

• The migration task name or identifier
• The visible completion time
• The final status shown on the task
• Any warning or error messages displayed in the result area

Then describe the homepage issue in plain, specific terms. Instead of writing “homepage broken,” record exactly what is wrong and where it appears. Useful examples include:

• Hero banner image missing
• Featured service card opens the wrong page
• Startup package section not visible
• Trust indicator icons not loading
• Contact button text appears, but the button destination is incorrect

A simple issue log like this works well:

If Sherkety ERP & Website Platform lets you inspect the migrated content behind the homepage, check whether the problem appears there too. This helps you separate a display issue from a migration data issue. If the content record looks correct but the homepage still looks wrong, note that difference clearly in your report.

Resolving common post-migration issues on the homepage

Some homepage issues appear often enough that you can review them in a consistent way before escalating them. Start with what the migration result screen already told you, then confirm the issue on the homepage.

If homepage content is missing even though the task shows as completed, reopen the task details and look for Skipped items or warning messages. A completed run may have left some homepage blocks unchanged or excluded them from transfer. Match the skipped item names or result rows to the missing section on the page.

If images, banners, or icons appear as empty spaces or placeholders, compare the homepage with the migration results and look for media-related failures or warnings. A missing visual usually means the content block transferred but the related media did not. Check whether the text for that section appears while the image does not. That pattern is a strong clue.

If links open the wrong destination, test the homepage button again and compare it with the expected target from the source content or migration plan. Then return to the task output and see whether the related item shows as updated, skipped, or failed. A skipped link entry often explains why an older destination remained in place.

If the layout looks different after migration, review the order of homepage sections and the structure of cards or banners. The content may be present but arranged differently than expected. Look for:

• Sections appearing in the wrong sequence
• Missing spacing between content blocks
• Misaligned cards or tiles
• Text wrapping differently inside banners or feature areas

If these checks do not explain the issue, use your recorded notes and compare them with the earlier follow-up guidance in Reviewing Migration Results and Follow Up Checks and Planning Safe Follow Up Actions After Migration.

Overview

This document focuses on what to do after a homepage migration has already finished in Sherkety ERP & Website Platform. Your goal at this stage is not to rerun the migration or plan the move again. Instead, you review the completed task, interpret the visible results, and confirm that the homepage now displays the expected content correctly.

The post-migration review has two parts that work together. First, you inspect the completed task in the Migration Tool and read the result details, including the final status, item counts, warnings, and any row-level outcomes such as created, updated, skipped, or failed. Second, you open the homepage itself and verify that the migrated sections, links, images, and layout behave as expected in the live page view.

This guide is especially useful when:

• A migration task appears to have completed, but you want to confirm nothing was missed
• The task shows warnings and you need to understand what to check on the homepage
• The homepage looks different after migration and you need to identify whether the issue is content, media, links, or layout
• You need clear notes for follow-up on missing or incorrect homepage content

This guide builds on the migration workflow already covered in Running Homepage Migration Tasks and the purpose explained in Understanding Homepage Migration Tool Purpose and Scope. Here, the focus stays on visible results and practical verification steps inside the completed task screen and the homepage view.

Prerequisites

Before you start this post-migration review in Sherkety ERP & Website Platform, make sure you have access to both the migration results and the homepage you need to verify. You do not need advanced setup for this stage, but you do need enough access to open the completed task and inspect the affected homepage sections.

You should have:

• Access to the Migration Tool area where completed homepage tasks are listed
• Permission to view the completed migration task details
• Access to the homepage or target page that received the migrated content
• A clear idea of which homepage sections were expected to move during the migration
• Enough time to click through homepage buttons, links, and featured sections without rushing

It also helps to have the following available while you review:

• The migration task you ran most recently, so you do not accidentally inspect an older result
• Any source homepage reference or migration expectation notes used earlier in the process
• A place to record issues, including warning text and affected homepage areas

If you have not yet run the migration itself, go back to Running Homepage Migration Tasks. If you need help deciding what should have been included in the migration, review Understanding Homepage Migration Tool Purpose and Scope. If you are already seeing warning banners, missing content, or error states in the interface, the supporting guidance in Recognizing Warnings Errors and Dismissible Notices and Understanding Loading Placeholders Empty States and Errors can help you interpret what you see.