3271534 - Tips for handling migration of users/cases/systems when contracts are moved to a different customer number - SAP for Me

• Changed customer numbers due to acquisition
• Company migration to a new customer number
• Changes needed when switching to a new customer number
• Separate customer numbers merged into one best customer number
• Licenses and contracts were migrated to a different customer number
• Can cases be moved to a different customer number?
• Can we reassign cases to a different account?
• Can cases be reassigned?
• Transfer cases to a new customer number
• Do new S-user IDs need to be created when contracts are moved to a different customer number?
• Migrating systems from old customer number to new customer number
• Do new installation numbers need to be created when contracts are moved to a different customer number?
• Moved from an old customer number to a new customer number
• Reassigned systems and license keys from one customer number to another
• How to make sure that users can create support cases after migrating accounts
• How can I access the licenses under our old customer number
• How to make sure that users can create cases after migrating accounts

SAP for Me

support messages , migration of incidents , migrating incidents , move incidents , transfer incidents , Meldungen kopieren , copy history , Meldungstransfer , Meldungshistorie kopieren , change incident details , incorrect system , change incident , customer migration , migrating contracts , acquisition , merging customer numbers , transition , suser , cases , licensing , licenses , instances , move contracts , migrated , merged , transfer , transferred , transferring , copying , duplicating , duplicated , , KBA , XX-SER-FORME , SAP for Me , XX-SER-LIKEY , License keys for SAP systems , How To