As UX specialists in the SAP S/4HANA Regional Implementation Group and the Fiori Launchpad ABAP team, we often get to work with customers keen to leverage the significant capabilities of SAP Fiori. Are you still using the Fiori Launchpad Designer to maintain your SAP Fiori content? If so, it’s time for some good news: migrating to modern tools just got a whole lot easier with SAP S/4HANA 2025.

Why This Matters to You

In recent years, SAP Fiori Launchpad Designer has been slowly deprecated and replaced with new tools. Refer to:

• Setting Up Technical Catalogs with the SAP Fiori Launchpad App Manager
• SAP Fiori Launchpad Designer: Features Deprecated

With technical catalog migration, you can make your SAP Fiori content future-proof, clean-core compliant – and benefit from improved tools.

About this Blog

The tool for technical catalog migration – transaction /UI2/MGR_TC – is available from SAP S/4HANA 2023 FPS01 and is covered in these excellent blogs:

• SAP Fiori for SAP S/4HANA – Technical Catalog Migration – Why and Getting Ready for Migration​
• SAP Fiori for SAP S/4HANA – Technical Catalog Migration – How the migration process works​

This blog builds on these earlier posts by sharing some exciting news: SAP S/4HANA 2025 brings new features that make technical catalog migration easier and more flexible than ever before. We cover the following:

1. Recap of Technical Catalog Migration
2. The Challenge: What Held Customers Back
3. The Game changer: Partial Migration
4. What Happens Behind the Scenes During a Partial Migration
5. SAP S/4HANA 2025: Partial Migration – Example
6. When To Migrate
7. Frequently Asked Questions
8. Prerequisites & Limitations

Refer to:

• What’s New in ABAP Platform 2025 FPS01 – Migration of Technical Catalogs
• What’s New in ABAP Platform 2023 FPS01 – Migration of Technical Catalogs
• SAP Note: 3170196 – Tools for Setting Up Launchpad Content

1.    Recap of Technical Catalog Migration

In our new launchpad content model, tiles and target mappings are still being used in technical catalogs, but the way of storing them has changed:

• Previously, tiles and target mappings were loosely coupled.
• Now, with Launchpad App Descriptor Items (LADIs), they are closely coupled as a pair.

To make your launchpad content future-proof, technical catalogs created with the deprecated SAP Fiori Launchpad Designer must be migrated to the SAP Fiori Launchpad App Manager (transaction /UI2/FLPAM).

Tiles and target mappings / LADIs

• Technical catalogs created in the deprecated Fiori Launchpad Designer:

           NOTE: Technical catalogs created in the Fiori Launchpad Designer are only are visible in App Manager, only after migration.

• Migrated technical catalogs and catalogs created in Launchpad App Manager:

          Now the technical catalogs are maintained in App Manager. They are also visible (read-only) in the Fiori Launchpad Designer

Migrated technical catalog

2.  The Challenge: What Held Customers Back

Until now, the migration tool required that your technical catalogs are perfect before migration. If a catalog had some apps that could be migrated and some that couldn’t, the entire catalog was marked as “Not Ready for Migration.” This meant you had to clean up everything before you could start the migration. The migration tool has always provided detailed error descriptions and suggested fixes, but fixing all errors could still be a time-consuming process.

Here’s what could block migration:

• Tiles or target mappings with configuration errors
• Mixed catalogs, containing originals and references
• Catalog names outside the customer namespace for workbench objects
• Content not following best practices 

3. The Gamechanger: Partial Migration

With SAP S/4HANA 2025, we have introduced a feature that makes your life easier: partial catalog migration.

Now you can migrate the apps that are ready, while keeping the problematic ones in the old format temporarily. Affected catalogs have the status: “1c Ready for Partial Migration.”

Additional bonus: if your old catalog name doesn’t meet current naming requirements, you can correct the name during migration. The tool automatically updates all references, so nothing breaks in the process.     

Partial migration

 Note: The partial migration transfers all your translations automatically – as long as they’re in the same system. Maintaining translations separately? You have two options:                                                                                    

• Retranslate the content in the new Fiori Launchpad App Manager-based catalog after partial migration, or                         
• Clean up your technical catalogs first and use the full migration path available from SAP S/4HANA 2023 FPS01. 

What this means

You’re no longer blocked! Migrate what you can today and handle the exceptions separately. Apps that can’t be migrated stay in the old catalog, while everything else moves to the modern tools where you can maintain them more easily.

Already have clean catalogs that follow best practices? No problem! The ‘Full Migration’ option from SAP S/4HANA 2023 FPS01 is still fully supported in 2025. Refer to the blogs below:

• SAP Fiori for SAP S/4HANA – Technical Catalog Migration – Why and Getting Ready for Migration​
• SAP Fiori for SAP S/4HANA – Technical Catalog Migration – How the migration process works

4. What Happens Behind the Scenes During a Partial Migration

Before migration: Let’s look at a technical catalog Z_OLD_CATALOG_TC (created in the Fiori Launchpad Designer) that stores both original and reference tiles and target mappings (i.e. a mixed catalog).:

During migration: This is shown below in steps 1 and 2.

Step 1: Original tile and original target mapping are combined into a newly created LADI (launchpad app descriptor item) in an existing or new Launchpad App Manager based catalog Z_NEW_CATALOG_TC.

Step 2: In the old catalog Z_OLD_CATALOG_TC, convert the Fiori Launchpad Designer based original tile and target mapping into references pointing towards the newly created LADI from step 1. This prevents the broken references in our launchpad content. (Note: The picture below shows a different catalog name, where special characters have been replaced with compliant characters according to naming conventions.)

Before / after migration

After the migration: The new catalog Z_NEW_CATALOG_TC can be seen in the SAP Fiori Launchpad Application Manager

After migration

The Fiori Launchpad Designer based catalog Z_OLD_CATALOG still exists and may have the following statuses:

– “Not Ready” – This happens if some tiles/target mappings in the catalog could not be migrated.

• Reference tiles and target mappings are the same as before the migration.
• Originals that could be migrated have become references.
• Original apps that do not conform to the requirements in  SAP Note: 3397026 – SAP Fiori Launchpad – Technical Catalog Migration – Content Cleanup Risks stay as originals. These cannot be migrated without manual cleanup activities. Check their status for detailed errors. If you still need these apps, clean them up and migrate them automatically. Alternative: if you recreate the apps manually in App Manager, make sure to adjust your Business Catalogs to point to the new apps.

– “Not Relevant“ – all originals have successfully been migrated and only references are left (known as Business Catalogs)

Summary: You’re no longer blocked by unmovable apps. Migrate what you can and handle the rest separately!

5. SAP S/4HANA 2025: Partial Migration – Example

Let’s look at a real-life catalog that is not perfect and requires partial migration, ZCL_MGR_EXAMPLE_02_TC. Besides some originals, it also contains a reference, and it needs assignments of tiles to target mappings.  

• Migratable:  
  • Intent DevelopmentObject-translate
  • Tile only
• Migratable, but manual tile-target mapping assignment required:
  • Intent DevelopmentObject-connect: 1 tile matching 2 target mappings
  • Intent DevelopmentObject-map: 2 tiles matching 1 target mapping
• Reference, no need to migrate:  
  • Intent FLPBusinessCatalog-manageCrossClient

 Partial migration steps

1. Run transaction /UI2/MGR_TC, enter your technical catalog name (ZCL_MGR_EXAMPLE_02_TC here) and click on ‘Execute’:

Run transaction /UI2/MGR_TC

 NOTE: The selection screen of transaction /UI2/MGR_TC works as a filter to show only the technical catalogs that you want to work with. You can use ‘Z*’ (or your naming convention) to get an overview of your custom technical catalogs.

2. Select Migration Status as ‘1c Ready for Partial Migration’:

Status ‘Ready for Partial Migration”

3. Now you can see the technical catalog ZCL_MGR_EXAMPLE_02_TC, along with a list of statuses for each tile / target mapping.

 4. Select the technical catalog (in this case ZCL_MGR_EXAMPLE_02_TC) and click ‘Start Partial Migration‘.

Start Partial Migration

 5. Here, we have selected to create a new technical catalog ZCL_MGR_EXAMPLE_02_MIGRATED_TC. Choose an existing catalog or create a new one and click on the green tick.

NOTE: Please follow your naming conventions for technical catalogs, you do not need to use a keyword like ‘MIGRATED’, it is used here purely for illustration purposes.

Select technical catalog6. Depending on the content of the catalog, you see a screen for pairing tiles and target mappings. Normally there is one tile matching to one target mapping with the same semantic object / action and parameters, in this case the tile and target mapping assignment screen is skipped.

If there is more than one tile matching a target mapping or vice versa, like for our example catalog, user interaction is required.

What you see:

• A list of intents (on the left) that needs assignment or are missing a default tile
• Only intents with unclear tile-to-target-mapping connections are shown by default. Click ‘Show All Intents’ in the toolbar to include intents that could be resolved automatically.

 Key difference from before migration and after migration:

• Before (in the Fiori Launchpad Designer): Tiles and target mappings are loosely connected via matching intents.
• After (in Launchpad App Manager): Tiles and target mappings are coupled entities with the target mapping taking the lead.

 Steps you need to complete:

            a) Process all intents marked Assignment Needed (marked with a red ‘X’ in the status column below). See Step 6.1

            b) Assign each tile to a matching target mapping. See Step 6.2

            c) If multiple tiles match one target mapping, select which tile is the default. (Any additional tiles will be labelled as “Additional Tiles”.).See Step 6.3

             d) Click Start Partial Migration. See Step 6.4

6.1 Click on the first intent in error (in the example, it’s DevelopmentObject-connect, with 2 target mappings matching 1 tile) The status text of the tile tells you to ‘Assign to target mapping’, so select the correct target mapping and click on Assign to Target Mapping.

 6.2. Now you see a green tick for both the intent and for the tile: tile and target mapping have been paired, and all uncertainties have been resolved.

 6.3 Now select the remaining intent, DevelopmentObject-map (1 target mapping matching 2 tiles) and the status text of the target mapping tells you to ‘Set default tile’. Select the correct tile and click on Set as Default Tile.

6.4 Now you can see that all intents have the green tick and that a Default Tile has been chosen. Click on Start Partial Migration:

7. When prompted, enter a suitable development package and select a transport (if required). In this example, we are saving the new standard technical catalog as a Local Object (Package = $TMP).

 8. Now you can see the migration of the technical catalog to ZCL_MGR_EXAMPLE_02_MIGRATED_TC has been completed successfully. It is displayed in the list of catalogs with status ‘4 Migration Finished’. Select the technical catalog and click on Open SAP Fiori Launchpad App Manager.

 9. Your newly created technical catalog ZCL_MGR_EXAMPLE_02_MIGRATED_TC is displayed in SAP Fiori Launchpad App Manager, where you can view the corresponding LADIs.

10.  The old Fiori Launchpad Designer Catalog ZCL_MGR_EXAMPLE_02_TC is now in status ‘Not Relevant for Migration’. It is now a business catalog that contains only references. Below you can see this in both the migration tool (transaction /UI2/MGR_TC) and the Fiori Launchpad Designer:

Consider the deletion of the old Fiori Launchpad Designer technical catalog if you are sure that it is not used anymore. 

11. For the end user, the Fiori launchpad will look the same, before and after migration. Below, you can see a sample screenshot of how this new technical catalog ZCL_MGR_EXAMPLE_02_MIGRATED_TC looks in the SAP Fiori Launchpad:

6. When To Migrate

If you’re already on release SAP S/4HANA 2025, it’s easy: migrate as soon as possible.

 If you’re on release SAP S/4HANA 2023 FPS01+, it depends on your content. Run transaction /UI2/MGR_TC to check if any catalogs need special attention and what issues need to be resolved:

• Are all catalogs in status ‘Ready for Migration’, or ‘Ready for Migration – Assignment Required’? Great. Migrate on SAP S/4HANA 2023 FPS01.
• Are some of your catalogs in status ‘Not Ready for Migration’? Check the list of migration issues to see how much manual rework would be required. You can minimize the effort by upgrading first and running the migration on SAP S/4HANA 2025.
• Do you need to rename your technical catalogs? This is only possible with the partial migration in release SAP S/4HANA 2025. Upgrade first and run the migration on SAP S/4HANA 2025.

 7. Frequently Asked Questions

Question: Can I migrate client-specific catalogs?

– Answer: Yes. Note that migration will transform them into cross-client catalogs, for better reuse and because the resulting launchpad app descriptor items are cross-client workbench objects.

Question: Does the technical catalog migration provide any options for moving cross-client catalogs to the client-specific layer?

– Answer: No. Cross-client and client-specific technical catalogs are always moved to cross-client. This is because LADIs are always cross-client.

Question: Do I have to change my authorizations after upgrade?

– Answer: No authorization changes are required. References and links in your business catalogs stay intact, no rework is required

Question: Can admins see the new technical catalog in the old Fiori Launchpad Designer after migration?

– Answer: Yes, admins can see the new technical catalog in the old Fiori Launchpad Designer, but only as read-only (they can view it but not change it). To edit the technical catalog, administrators must use Launchpad App Manager tool instead.

Question: What object directory entries are involved?

Answer:

• Technical catalogs created in the Fiori Launchpad Designer – Object Directory Entry R3TR / UIAC
• Technical catalogs that have been migrated have Object Directory Entry R3TR / UIAD

After migration, SAP recommends using the following tools:

• Launchpad App Manager – for technical catalogs
• Launchpad Content Manager – for business catalogs

8. Prerequisites & Limitations

 Question: Are there any prerequisites, or any limitations concerning the content that can be migrated with release SAP S/4HANA 2025?

• Check SAP 3397026 – SAP Fiori Launchpad – Technical Catalog Migration – Content Cleanup Risks for prerequisites.
• Apps with system aliases other than LOCAL are not supported in Launchpad App Manager yet.

Recommendation: Keep target mappings with other system aliases (plus tiles with the matching intent) in the deprecated Fiori Launchpad Designer.

• Custom tiles are in maintenance mode. They are not supported in Launchpad App Manager, only by the deprecated Fiori Launchpad Designer.

Recommendation: Consider replacing your custom tiles with standard tiles. If that is not possible, keep your custom tiles in the deprecated Fiori Launchpad Designer. Even if some tiles and target mappings need to stay in the deprecated Fiori Launchpad Designer, SAP recommends that you migrate the rest of the catalog using partial migration.

 Resources worth knowing:

• SAP Fiori for SAP S/4HANA – Technical Catalog Migration – Why and Getting Ready for Migration​
• SAP Fiori for SAP S/4HANA – Technical Catalog Migration – How the migration process works​
• What’s New in ABAP Platform 2025 FPS00 – Migration of technical catalogs
• What’s New in ABAP Platform 2023 FPS01 – Migration of technical catalogs
• SAP Note: 3170196 – Tools for Setting Up Launchpad Content
• SAP Note: 3397026 – SAP Fiori Launchpad – technical catalog Migration – Content Cleanup Risks

You’ll find much more on the community topic page for SAP Fiori for SAP S/4HANA

 Other helpful links in the SAP Community:

• Follow our tag S4HANA RIG – SAP Community for more from the SAP S/4HANA Customer Care and RIG
• See all questions and answers about SAP Fiori for SAP S/4HANA
• Follow SAP Fiori for SAP S/4HANA for more blogs and updates
• Ask a Question about SAP Fiori for SAP S/4HANA

Brought to you by the SAP S/4HANA Customer Care and RIG and the Fiori Launchpad ABAP Team.

 As UX specialists in the SAP S/4HANA Regional Implementation Group and the Fiori Launchpad ABAP team, we often get to work with customers keen to leverage the significant capabilities of SAP Fiori. Are you still using the Fiori Launchpad Designer to maintain your SAP Fiori content? If so, it’s time for some good news: migrating to modern tools just got a whole lot easier with SAP S/4HANA 2025. Why This Matters to YouIn recent years, SAP Fiori Launchpad Designer has been slowly deprecated and replaced with new tools. Refer to:Setting Up Technical Catalogs with the SAP Fiori Launchpad App ManagerSAP Fiori Launchpad Designer: Features DeprecatedWith technical catalog migration, you can make your SAP Fiori content future-proof, clean-core compliant – and benefit from improved tools. About this BlogThe tool for technical catalog migration – transaction /UI2/MGR_TC – is available from SAP S/4HANA 2023 FPS01 and is covered in these excellent blogs:SAP Fiori for SAP S/4HANA – Technical Catalog Migration – Why and Getting Ready for Migration​SAP Fiori for SAP S/4HANA – Technical Catalog Migration – How the migration process works​This blog builds on these earlier posts by sharing some exciting news: SAP S/4HANA 2025 brings new features that make technical catalog migration easier and more flexible than ever before. We cover the following:1. Recap of Technical Catalog Migration2. The Challenge: What Held Customers Back3. The Game changer: Partial Migration4. What Happens Behind the Scenes During a Partial Migration5. SAP S/4HANA 2025: Partial Migration – Example6. When To Migrate7. Frequently Asked Questions8. Prerequisites & LimitationsRefer to:What’s New in ABAP Platform 2025 FPS01 – Migration of Technical CatalogsWhat’s New in ABAP Platform 2023 FPS01 – Migration of Technical CatalogsSAP Note: 3170196 – Tools for Setting Up Launchpad Content1.    Recap of Technical Catalog MigrationIn our new launchpad content model, tiles and target mappings are still being used in technical catalogs, but the way of storing them has changed:Previously, tiles and target mappings were loosely coupled.Now, with Launchpad App Descriptor Items (LADIs), they are closely coupled as a pair.To make your launchpad content future-proof, technical catalogs created with the deprecated SAP Fiori Launchpad Designer must be migrated to the SAP Fiori Launchpad App Manager (transaction /UI2/FLPAM).Tiles and target mappings / LADIsTechnical catalogs created in the deprecated Fiori Launchpad Designer:           NOTE: Technical catalogs created in the Fiori Launchpad Designer are only are visible in App Manager, only after migration.Migrated technical catalogs and catalogs created in Launchpad App Manager:          Now the technical catalogs are maintained in App Manager. They are also visible (read-only) in the Fiori Launchpad Designer Migrated technical catalog 2.  The Challenge: What Held Customers BackUntil now, the migration tool required that your technical catalogs are perfect before migration. If a catalog had some apps that could be migrated and some that couldn’t, the entire catalog was marked as “Not Ready for Migration.” This meant you had to clean up everything before you could start the migration. The migration tool has always provided detailed error descriptions and suggested fixes, but fixing all errors could still be a time-consuming process.Here’s what could block migration:Tiles or target mappings with configuration errorsMixed catalogs, containing originals and referencesCatalog names outside the customer namespace for workbench objectsContent not following best practices 3. The Gamechanger: Partial MigrationWith SAP S/4HANA 2025, we have introduced a feature that makes your life easier: partial catalog migration.Now you can migrate the apps that are ready, while keeping the problematic ones in the old format temporarily. Affected catalogs have the status: “1c Ready for Partial Migration.” Additional bonus: if your old catalog name doesn’t meet current naming requirements, you can correct the name during migration. The tool automatically updates all references, so nothing breaks in the process.     Partial migration Note: The partial migration transfers all your translations automatically – as long as they’re in the same system. Maintaining translations separately? You have two options:                                                                                    Retranslate the content in the new Fiori Launchpad App Manager-based catalog after partial migration, or                         Clean up your technical catalogs first and use the full migration path available from SAP S/4HANA 2023 FPS01. What this meansYou’re no longer blocked! Migrate what you can today and handle the exceptions separately. Apps that can’t be migrated stay in the old catalog, while everything else moves to the modern tools where you can maintain them more easily.Already have clean catalogs that follow best practices? No problem! The ‘Full Migration’ option from SAP S/4HANA 2023 FPS01 is still fully supported in 2025. Refer to the blogs below:SAP Fiori for SAP S/4HANA – Technical Catalog Migration – Why and Getting Ready for Migration​SAP Fiori for SAP S/4HANA – Technical Catalog Migration – How the migration process works4. What Happens Behind the Scenes During a Partial MigrationBefore migration: Let’s look at a technical catalog Z_OLD_CATALOG_TC (created in the Fiori Launchpad Designer) that stores both original and reference tiles and target mappings (i.e. a mixed catalog).: During migration: This is shown below in steps 1 and 2.Step 1: Original tile and original target mapping are combined into a newly created LADI (launchpad app descriptor item) in an existing or new Launchpad App Manager based catalog Z_NEW_CATALOG_TC.Step 2: In the old catalog Z_OLD_CATALOG_TC, convert the Fiori Launchpad Designer based original tile and target mapping into references pointing towards the newly created LADI from step 1. This prevents the broken references in our launchpad content. (Note: The picture below shows a different catalog name, where special characters have been replaced with compliant characters according to naming conventions.)Before / after migration After the migration: The new catalog Z_NEW_CATALOG_TC can be seen in the SAP Fiori Launchpad Application ManagerAfter migrationThe Fiori Launchpad Designer based catalog Z_OLD_CATALOG still exists and may have the following statuses:- “Not Ready” – This happens if some tiles/target mappings in the catalog could not be migrated.Reference tiles and target mappings are the same as before the migration.Originals that could be migrated have become references.Original apps that do not conform to the requirements in  SAP Note: 3397026 – SAP Fiori Launchpad – Technical Catalog Migration – Content Cleanup Risks stay as originals. These cannot be migrated without manual cleanup activities. Check their status for detailed errors. If you still need these apps, clean them up and migrate them automatically. Alternative: if you recreate the apps manually in App Manager, make sure to adjust your Business Catalogs to point to the new apps.- “Not Relevant” – all originals have successfully been migrated and only references are left (known as Business Catalogs)Summary: You’re no longer blocked by unmovable apps. Migrate what you can and handle the rest separately! 5. SAP S/4HANA 2025: Partial Migration – ExampleLet’s look at a real-life catalog that is not perfect and requires partial migration, ZCL_MGR_EXAMPLE_02_TC. Besides some originals, it also contains a reference, and it needs assignments of tiles to target mappings.  Migratable:  Intent DevelopmentObject-translateTile onlyMigratable, but manual tile-target mapping assignment required:Intent DevelopmentObject-connect: 1 tile matching 2 target mappingsIntent DevelopmentObject-map: 2 tiles matching 1 target mappingReference, no need to migrate:  Intent FLPBusinessCatalog-manageCrossClient Partial migration steps1. Run transaction /UI2/MGR_TC, enter your technical catalog name (ZCL_MGR_EXAMPLE_02_TC here) and click on ‘Execute’:Run transaction /UI2/MGR_TC NOTE: The selection screen of transaction /UI2/MGR_TC works as a filter to show only the technical catalogs that you want to work with. You can use ‘Z*’ (or your naming convention) to get an overview of your custom technical catalogs.2. Select Migration Status as ‘1c Ready for Partial Migration’:Status ‘Ready for Partial Migration”3. Now you can see the technical catalog ZCL_MGR_EXAMPLE_02_TC, along with a list of statuses for each tile / target mapping. 4. Select the technical catalog (in this case ZCL_MGR_EXAMPLE_02_TC) and click ‘Start Partial Migration’.Start Partial Migration 5. Here, we have selected to create a new technical catalog ZCL_MGR_EXAMPLE_02_MIGRATED_TC. Choose an existing catalog or create a new one and click on the green tick.NOTE: Please follow your naming conventions for technical catalogs, you do not need to use a keyword like ‘MIGRATED’, it is used here purely for illustration purposes.Select technical catalog6. Depending on the content of the catalog, you see a screen for pairing tiles and target mappings. Normally there is one tile matching to one target mapping with the same semantic object / action and parameters, in this case the tile and target mapping assignment screen is skipped.If there is more than one tile matching a target mapping or vice versa, like for our example catalog, user interaction is required.What you see:A list of intents (on the left) that needs assignment or are missing a default tileOnly intents with unclear tile-to-target-mapping connections are shown by default. Click ‘Show All Intents’ in the toolbar to include intents that could be resolved automatically. Key difference from before migration and after migration:Before (in the Fiori Launchpad Designer): Tiles and target mappings are loosely connected via matching intents.After (in Launchpad App Manager): Tiles and target mappings are coupled entities with the target mapping taking the lead. Steps you need to complete:            a) Process all intents marked Assignment Needed (marked with a red ‘X’ in the status column below). See Step 6.1            b) Assign each tile to a matching target mapping. See Step 6.2            c) If multiple tiles match one target mapping, select which tile is the default. (Any additional tiles will be labelled as “Additional Tiles”.).See Step 6.3             d) Click Start Partial Migration. See Step 6.46.1 Click on the first intent in error (in the example, it’s DevelopmentObject-connect, with 2 target mappings matching 1 tile) The status text of the tile tells you to ‘Assign to target mapping’, so select the correct target mapping and click on Assign to Target Mapping. 6.2. Now you see a green tick for both the intent and for the tile: tile and target mapping have been paired, and all uncertainties have been resolved. 6.3 Now select the remaining intent, DevelopmentObject-map (1 target mapping matching 2 tiles) and the status text of the target mapping tells you to ‘Set default tile’. Select the correct tile and click on Set as Default Tile.6.4 Now you can see that all intents have the green tick and that a Default Tile has been chosen. Click on Start Partial Migration:7. When prompted, enter a suitable development package and select a transport (if required). In this example, we are saving the new standard technical catalog as a Local Object (Package = $TMP). 8. Now you can see the migration of the technical catalog to ZCL_MGR_EXAMPLE_02_MIGRATED_TC has been completed successfully. It is displayed in the list of catalogs with status ‘4 Migration Finished’. Select the technical catalog and click on Open SAP Fiori Launchpad App Manager. 9. Your newly created technical catalog ZCL_MGR_EXAMPLE_02_MIGRATED_TC is displayed in SAP Fiori Launchpad App Manager, where you can view the corresponding LADIs.10.  The old Fiori Launchpad Designer Catalog ZCL_MGR_EXAMPLE_02_TC is now in status ‘Not Relevant for Migration’. It is now a business catalog that contains only references. Below you can see this in both the migration tool (transaction /UI2/MGR_TC) and the Fiori Launchpad Designer: Consider the deletion of the old Fiori Launchpad Designer technical catalog if you are sure that it is not used anymore. 11. For the end user, the Fiori launchpad will look the same, before and after migration. Below, you can see a sample screenshot of how this new technical catalog ZCL_MGR_EXAMPLE_02_MIGRATED_TC looks in the SAP Fiori Launchpad:6. When To MigrateIf you’re already on release SAP S/4HANA 2025, it’s easy: migrate as soon as possible. If you’re on release SAP S/4HANA 2023 FPS01+, it depends on your content. Run transaction /UI2/MGR_TC to check if any catalogs need special attention and what issues need to be resolved:Are all catalogs in status ‘Ready for Migration’, or ‘Ready for Migration – Assignment Required’? Great. Migrate on SAP S/4HANA 2023 FPS01.Are some of your catalogs in status ‘Not Ready for Migration’? Check the list of migration issues to see how much manual rework would be required. You can minimize the effort by upgrading first and running the migration on SAP S/4HANA 2025.Do you need to rename your technical catalogs? This is only possible with the partial migration in release SAP S/4HANA 2025. Upgrade first and run the migration on SAP S/4HANA 2025. 7. Frequently Asked QuestionsQuestion: Can I migrate client-specific catalogs?- Answer: Yes. Note that migration will transform them into cross-client catalogs, for better reuse and because the resulting launchpad app descriptor items are cross-client workbench objects.Question: Does the technical catalog migration provide any options for moving cross-client catalogs to the client-specific layer?- Answer: No. Cross-client and client-specific technical catalogs are always moved to cross-client. This is because LADIs are always cross-client.Question: Do I have to change my authorizations after upgrade?- Answer: No authorization changes are required. References and links in your business catalogs stay intact, no rework is requiredQuestion: Can admins see the new technical catalog in the old Fiori Launchpad Designer after migration?- Answer: Yes, admins can see the new technical catalog in the old Fiori Launchpad Designer, but only as read-only (they can view it but not change it). To edit the technical catalog, administrators must use Launchpad App Manager tool instead.Question: What object directory entries are involved?Answer:Technical catalogs created in the Fiori Launchpad Designer – Object Directory Entry R3TR / UIACTechnical catalogs that have been migrated have Object Directory Entry R3TR / UIADAfter migration, SAP recommends using the following tools:Launchpad App Manager – for technical catalogsLaunchpad Content Manager – for business catalogs8. Prerequisites & Limitations Question: Are there any prerequisites, or any limitations concerning the content that can be migrated with release SAP S/4HANA 2025?Check SAP 3397026 – SAP Fiori Launchpad – Technical Catalog Migration – Content Cleanup Risks for prerequisites.Apps with system aliases other than LOCAL are not supported in Launchpad App Manager yet.Recommendation: Keep target mappings with other system aliases (plus tiles with the matching intent) in the deprecated Fiori Launchpad Designer.Custom tiles are in maintenance mode. They are not supported in Launchpad App Manager, only by the deprecated Fiori Launchpad Designer.Recommendation: Consider replacing your custom tiles with standard tiles. If that is not possible, keep your custom tiles in the deprecated Fiori Launchpad Designer. Even if some tiles and target mappings need to stay in the deprecated Fiori Launchpad Designer, SAP recommends that you migrate the rest of the catalog using partial migration. Resources worth knowing:SAP Fiori for SAP S/4HANA – Technical Catalog Migration – Why and Getting Ready for Migration​SAP Fiori for SAP S/4HANA – Technical Catalog Migration – How the migration process works​What’s New in ABAP Platform 2025 FPS00 – Migration of technical catalogsWhat’s New in ABAP Platform 2023 FPS01 – Migration of technical catalogsSAP Note: 3170196 – Tools for Setting Up Launchpad ContentSAP Note: 3397026 – SAP Fiori Launchpad – technical catalog Migration – Content Cleanup RisksYou’ll find much more on the community topic page for SAP Fiori for SAP S/4HANA Other helpful links in the SAP Community:Follow our tag S4HANA RIG – SAP Community for more from the SAP S/4HANA Customer Care and RIGSee all questions and answers about SAP Fiori for SAP S/4HANAFollow SAP Fiori for SAP S/4HANA for more blogs and updatesAsk a Question about SAP Fiori for SAP S/4HANABrought to you by the SAP S/4HANA Customer Care and RIG and the Fiori Launchpad ABAP Team.  Read More Technology Blog Posts by SAP articles 

#SAPCHANNEL