Skip to Content
Author's profile photo Marcus Echter

How to automatically synch ID mappings between migration and integration


You are performing migration of ECC customers and materials via the Migration Workbench (MWB) since you do not yet have integration setup. At a later point in time you would like to update these customers and materials via integration. Problem: As no ID mapping exists in C4C for these instances all customers and materials will be considered new and hence created as a duplicate. This is because the ID mapping written by the Migration Workbench in the “Value Conversion” step is stored in an internal migration table and cannot be consumed by our standard webservices.


There is a “hidden” automatic synchronization option of the internal MWB ID mapping into the standard ID mapping table. This synchronization can be enabled for customers and materials only. Furthermore it is only possible for ERP integration. You need to execute the following steps:

1) Before staring migration make sure customer and material integration are scoped in BC finetuning


2) Start the MWB and upload the file to be uploaded

3) After uploading the file into the staging area and before the actual migration open the file properties


4) In the following popup select the system instance which represents your ECC system. This is exactly the one you will create the Communication Arrangements for


5) start the migration

6) in the step “Value Conversion” you can now choose whether the old legacy numbers shall be kept (00002) or whether new numbers shall be taken by the migration service (00001). SAP proposal is 00002.


7) once migration has been successfully completed all ID mappings written in step “Value Conversion” will be also synched into the standard ID mapping table used by integration


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Kavya Krishnan
      Kavya Krishnan

      Dear Marcus,

      Great blog! I was looking for an answer to this problem 🙂



      Author's profile photo Former Member
      Former Member

      Great Information Marcus,

      Really helpful................. 🙂



      Author's profile photo Dedeepya Reddy
      Dedeepya Reddy

      Great Blog Marcus:) May be this could have solved the Employee Data Migration which we did manually, and can resolve the ID Mapping.

      Author's profile photo Marcus Echter
      Marcus Echter
      Blog Post Author

      Hi Dedeepya,

      thanks...Please note the ID mapping synch has only been implemented for accounts and products, no other objects.

      Regards, Marcus

      Author's profile photo Dedeepya Reddy
      Dedeepya Reddy

      Oh Ok Thanks Marcus for the clarification. Is there a roadmap for Employees/Org Units as well?

      Author's profile photo Marcus Echter
      Marcus Echter
      Blog Post Author

      No Dedeepya. There will not be any further investment in this. We are now recommending usage of IDOCs for initial load ...

      Author's profile photo Harish Choudhary
      Harish Choudhary

      Great Blog Marcus.. 🙂

      Author's profile photo Kendal Evans
      Kendal Evans

      Hi Marcus,

      Thanks for the info, great post

      Two questions -

      1. Does this work for BP contacts too? I assume yes as part of accounts?

      2. What do you do if you have already gone through the whole migration process and the customer is live and running? At the time of the initial project there was no scope for ERP integration. Integration to SAP ERP has now become a future phase for the client.