Skip to Content

Hello all,

ín this blog I will provide some hints when working with the Excel Template, downloaded from the SAP S/4HANA Migration Cockpit.

The migration template is an Microsoft Excel XML Spreadsheet 2003 that is an XML file and not a normal Excel workbook. It consists of different sheets to specify the data that belongs to different data structures. Some sheets are mandatory, and some are optional.


  • Always download and fill the original template of the SAP S/4HANA release you want to upload your data to.
  • Use sheet FIELD LIST to gain information which sheets are mandatory.
  • The wildcard character (*) indicates that a field is mandatory.
  • Maintain all mandatory fields in a mandatory sheet
  • Mandatory fields in an optional sheet don´t need to be filled.


  • Do not use a template from previous release.
  • Never change the structure and don’t make any changes on the format.
  • Don’t delete, rename, or reorder any sheet in the XML file.
  • Don’t change the cell formatting, don’t use formulas, and don’t hide, remove, or reorder any column in the XML file
  • Don’t change data by Find and Replace function. If you change data by Find and Replace  you may also accidentally change the field names and corrupt the XML structure.
  • Avoid empty lines in the XML (otherwise error message “… contains records with duplicate keys….” can arise).

A modified Migration Template will cause errors when trying to load into the migration cockpit or will cause errors during the data migration process


Formatting issues – Copying values

1. Within a migration template us Paste Option VALUES (V)


2. From somewhere else to the migration template use Past Option PASTE SPECIAL.. and then choose TEXT

3. From Notepad to the migration template use Past Option KEEP TEXT ONLY (T)

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Nitish Dhingra

    Hi Sybille


    Great article, definitely serves as a handy instruction set for core-team members for filling out the templates.


    Thanks for this.

  2. R. Auer

    Hi Sybille,

    Thanks for the detailed info. I’ve just started trying out tcode LTMC and creation of materials. However, when it comes to updating a material master field (for example material group) nothing is changed. Does the Migration Cockpit support the update of previously created objects? If so, is there also a no data sign/value?


    1. Sybille Lackermeier Post author


      Hi R. Auer,

      please check in detail the documentation for each migration object where it is explained what is the puprose of the object. Check the BAPI if there is an update possible.

      For 1709 e.g. we deliver a new migration object called “Material – extend existing record by new org levels” – this is to extend an already existing object.



Leave a Reply