## Understanding what the Homepage Migration Tool changes In **Sherkety ERP & Website Platform**, the **Homepage Migration Tool** is used when you need to carry an existing homepage setup into the current homepage structure. Its purpose is not to redesign the homepage from scratch. Instead, it helps administrators move homepage-specific setup so the destination homepage starts with the right content placements and section assignments already in place. When you run a homepage migration, you should expect the tool to focus on **homepage content and homepage configuration only**. Depending on what appears in the migration screen, this can include: - **Homepage section assignments** - **Featured content selections** - **Homepage-specific display settings** - **Content mapped into homepage areas** - **Promotional or highlighted homepage blocks** [SCREENSHOT: Homepage Migration Tool showing source, destination, and included homepage items] It is equally important to understand what the tool does **not** do automatically. The Homepage Migration Tool is not a shortcut for updating the entire website. It does **not** handle unrelated public pages, and it does **not** replace manual review in the homepage editor. If the new homepage design uses different visuals, different wording, or different section layouts, those adjustments still need to be checked and updated after the migration. The expected result after a successful run is straightforward: - The destination homepage reflects the migrated homepage setup - Homepage sections show the carried-over content mappings - Editors can open the homepage in preview or editing view and review what was brought over - The homepage is ready for verification before publishing If you already worked through follow-up planning in [Planning Safe Follow Up Actions After Migration](doc:planning-safe-follow-up-actions-after-migration), think of this tool as the action that applies the homepage setup you prepared for. ## Knowing when to open the migration tool The **Homepage Migration Tool** should be opened only when you are making a meaningful homepage-level change. In **Sherkety ERP & Website Platform**, the most common reason is a homepage transition where an existing homepage setup needs to be reused in a new homepage structure. Typical situations include: - Launching a **redesigned homepage** - Replacing an older homepage configuration with a newer one - Copying homepage setup into another environment for rollout or testing - Preparing a destination homepage so editors do not need to rebuild every section manually This is mainly an **administrator task**. Administrators open the migration screen, choose the source and destination, review what will be included, and confirm the migration. Content editors usually do **not** run the migration itself. Their role begins after the migration, when they review the homepage content in the editor or preview view and make any needed refinements. The best time to use the tool is: - **After** the destination homepage structure is available - **After** the target sections or content areas exist - **Before** final publishing or public release - **Before** editors begin final copy, image, and link review That timing matters because migrated content needs a valid place to land. If the destination homepage is incomplete, the results may be partial or require extra cleanup. You should **not** open the Homepage Migration Tool for routine content work. Skip it when you only need to: - Change a single banner - Update homepage text - Swap an image - Edit one section directly in the homepage editor - Make normal content corrections that are already supported by inline editing or the content editor For those smaller updates, use the regular editing workflow described in [Editing Content Directly From the Website](doc:editing-content-directly-from-the-website) or [Choosing Between Inline Editing and Admin Pages](doc:choosing-between-inline-editing-and-admin-pages). ## Reviewing the information before starting a migration Before opening the **Homepage Migration Tool**, confirm the homepage details you expect to move. This avoids running a migration with the wrong source or applying content into a destination that is not ready. Start by identifying the two most important items: - The **source homepage** you want to migrate from - The **destination homepage** that will receive the migrated setup You should also know which homepage areas are expected to carry over. Depending on what your team prepared, that may include hero content, featured sections, promotional blocks, or other homepage content areas shown in the migration screen. If you are unsure what should move, align with your content team before you begin rather than guessing during the migration. Next, confirm that you can actually access the migration area in the admin side of **Sherkety ERP & Website Platform**. The migration screen is intended for users with the right administrative access. If you can sign in but do not see the migration option, your role may not include permission to run homepage migrations. Before you continue, verify that the destination homepage structure already exists and includes the target areas needed for migrated content. This is one of the most important checks because migrated items need matching homepage sections or content slots. If the destination layout is missing expected areas, some content may not appear where you expect. It also helps to prepare editors for what happens after the migration. Agree in advance on which homepage areas they will review, such as: - **Headlines and body copy** - **Images and visual blocks** - **Buttons and links** - **Featured items** - **Section order and placement** [SCREENSHOT: Admin area with Homepage Migration Tool access and homepage selection fields] If your team already planned safe follow-up work, use that preparation here rather than repeating it. The earlier guidance in [Planning Safe Follow Up Actions After Migration](doc:planning-safe-follow-up-actions-after-migration) fits directly into this checkpoint. ## Following the migration workflow from selection to completion Once you are ready, open the **Homepage Migration Tool** from the administration area in **Sherkety ERP & Website Platform**. The screen is designed to guide you through a source-to-destination workflow, so your main job is to confirm each selection carefully before you run anything. Begin by selecting the **source homepage configuration**. This is the homepage setup that already contains the content assignments or homepage settings you want to reuse. After that, choose the **destination homepage** or target configuration where the migrated homepage setup should be applied. Before you confirm the migration, review the options shown on the screen. The tool may list which homepage parts are included in the migration. Pay close attention to items such as: - **Homepage sections** - **Featured content assignments** - **Homepage settings** - **Content blocks included in the transfer** - **Any visible include or exclude choices** This review step is where administrators catch mistakes early. If the source is wrong, or if the destination is not the intended homepage, stop and correct it before continuing. When everything looks right, run the migration using the action button shown on the screen. During processing, watch the interface for status changes. In Sherkety ERP & Website Platform, you may see loading feedback followed by a completion message. The result can appear as: - A **success** message when the homepage migration finishes as expected - A **warning** message when some items need review - A **partial** result when only some homepage content could be applied [SCREENSHOT: Migration confirmation area with selected source, destination, and completion message] Do not treat the completion message as the final approval step. A finished migration means the homepage setup has been applied as far as the tool could carry it. The next task is always to open the homepage in preview or editing view and verify the result. ## Checking the results after the migration finishes After the migration finishes, move immediately into review. In **Sherkety ERP & Website Platform**, the best place to confirm the outcome is the homepage **preview** or **editor** view, where you can see whether the migrated content appears in the correct sections. Start by checking the homepage areas you expected to receive migrated content. Look for: - **Featured sections** - **Promotional blocks** - **Homepage links or call-to-action areas** - **Visual placements** - **Any homepage-specific settings reflected on the page** Compare the destination homepage against the source homepage setup you intended to copy. You are not only checking whether content exists; you are checking whether it appears in the **right location** and still makes sense in the new homepage structure. Focus especially on high-visibility areas such as top promotional content, featured items, and key navigation or action links. A successful outcome looks slightly different depending on the user’s role: - For **administrators**, success means the homepage configuration has been applied and the destination homepage now reflects the migrated setup. - For **content editors**, success means the homepage opens with content already in place and ready for final review, refinement, and publishing preparation. [SCREENSHOT: Homepage preview showing migrated sections and featured content placements] Even with a successful migration, some follow-up work is normal. Common examples include: - Updating outdated text - Replacing images that do not fit the new layout - Checking buttons and links - Adjusting section content for the destination homepage design - Cleaning up any content that looks incomplete after transfer This is where migration ends and editorial review begins. If you need a broader validation process after this point, continue with [Reviewing Migration Results and Post Migration Checks](doc:reviewing-migration-results-and-post-migration-checks). ## Handling common migration issues If the **Homepage Migration Tool** does not appear in the admin area, first confirm that you are signed in with the correct account and role. In **Sherkety ERP & Website Platform**, homepage migration is an administrative action, so users without the right access may not see the migration option at all. If other admin pages are available but the migration area is missing, check with the person who manages user access and roles. If the migration runs but some homepage content does not appear afterward, the most likely issue is a mismatch between the source homepage and the destination homepage structure. Review whether the destination homepage has the same sections or compatible content areas needed for the migrated items. If the target homepage is missing those areas, some content may not display even though the migration completed. When the migrated homepage looks incomplete or visually out of place, compare the source and destination homepage layouts. A redesigned homepage often uses different section arrangements, image proportions, or content priorities. In that case, the migration may have carried over the content assignment, but the result still needs manual cleanup in the homepage editor. Editors may also report that they cannot approve the migrated homepage. When that happens, check these points: - The migration showed a **completed** or **successful** result - The editor is reviewing the **correct homepage** - The homepage is opened in the proper **preview** or **editing** context - The expected migrated sections are actually part of the destination homepage [SCREENSHOT: Warning or partial migration message in the Homepage Migration Tool] If you see a warning or partial result, do not rerun the migration immediately without checking the cause. Review the destination homepage structure first, then inspect the migrated homepage in the editor. For general interface feedback such as notices and warning messages, see [Recognizing Warnings Errors and Dismissible Notices](doc:recognizing-warnings-errors-and-dismissible-notices). ## Overview The **Homepage Migration Tool** in **Sherkety ERP & Website Platform** is a focused admin feature for moving homepage setup from one homepage configuration into another. Its value is speed and consistency: instead of rebuilding homepage assignments manually, administrators can apply an existing homepage setup to a destination homepage and then hand it off for editorial review. At a high level, the workflow looks like this: - Open the migration screen from the admin area - Select the **source homepage** - Select the **destination homepage** - Review the homepage items included in the migration - Run the migration - Check the result in preview or editing view The tool is best used during larger homepage changes, such as a homepage redesign or a rollout into a new destination setup. It is not meant for routine homepage maintenance. If you only need to update text, swap images, or adjust one section, use the normal editing tools instead of migration. Keep these scope boundaries in mind: - It is for **homepage-related content and configuration** - It does **not** replace editorial review - It does **not** automatically fix layout differences - It does **not** update unrelated site pages The most important sign of success is not just a completion message. Success means the destination homepage shows the expected migrated sections, featured content, and homepage placements, and editors can continue with review and refinement. [SCREENSHOT: Full Homepage Migration Tool screen with source, destination, options, and status area] If you need help understanding where this fits in the broader migration sequence, connect it with the earlier preparation work in [Planning Safe Follow Up Actions After Migration](doc:planning-safe-follow-up-actions-after-migration), then move on to [Reviewing Migration Results and Post Migration Checks](doc:reviewing-migration-results-and-post-migration-checks). ## Prerequisites Before using the **Homepage Migration Tool** in **Sherkety ERP & Website Platform**, make sure the basic conditions for a clean migration are already in place. This tool works best when the destination homepage is prepared and your team knows exactly what should be carried over. Confirm these prerequisites before you begin: - You can sign in to the **admin area** - Your account has permission to access homepage migration - The **source homepage** has the setup you want to reuse - The **destination homepage** already exists - The destination homepage includes the sections or content areas needed for migrated items - Your team knows which homepage content should be reviewed after migration It is also helpful to have alignment between administrators and content editors. Administrators should know which homepage configuration to migrate and where it should be applied. Editors should know which homepage areas they are expected to validate afterward, especially visible sections such as featured content, promotional blocks, images, and links. Before running the migration, prepare for post-migration checking by identifying: - Which homepage sections are highest priority - Which visual assets need review - Which links or calls to action should be tested - Which content may need rewriting for the new homepage layout [SCREENSHOT: Admin navigation leading to the Homepage Migration Tool] Do not use the migration tool as a substitute for normal homepage editing. If the destination homepage is still being built, or if the change is only a small content update, wait until the homepage structure is ready or use the regular editor instead. Once these prerequisites are met, you can run the migration with much less risk of missing sections, incomplete placements, or unnecessary rework.