SAP-CRM V7.13 (non-HANA): Divide data into 2 clients to support a carve out

[Schoki]

Currently one client (100) consists of data of 2 divisions. That should change: Every division should become an own client (Client 100 and 200 on the same system). I have the idea to simply create a second Client 200 and go through all datatables (Masterdata and transactions), starting with BUT000 and COMM_PRODUCT and simply change the Clientnumber to 200 for the data of the carved out division via SQL? It appears to be just a minor effort to cascade down from BUT000 and COMM_PRODUCT to related masterdatatables and transactiontables. The result would be that within our database-tables we would have data of the 2 clients. Are there any concerns of doing that? To me it appears the simplest way, just simple updates via DBACockpit, no deletes. I have the impression that consulting companies and also SAP are not recommending that and instead prefer downloads and uploads, sometime via Excel, which leads to serious issues getting the correct state of transactions and moving history data. I also see some challenges related to the datamodel, like CRMD_LINK... and the integration to ERP, but that is far less critical to me than any other approach. Does anyone have experience with that approach?   

[Schoki]

This would be similar to a “Clone and Migrate”-scenario. The idea is to clone client 100 into 200, adjust some customizing afterwards, like integration and connectivity. Then also cloning the orgmodel via SQL and some Business partners, like the org BuPas. These steps are also needed in a ”Clone and Migrate”-scenario. The point is how to get in the masterdata and transactional data most efficiently into the client 200 and I don’t see a reason why not simply changing the client ID for relevant records and running afterwards an update of LOGSYS to the linked ERP-client 200. Any experience or ideas about that?