Can Site be copied/exported from origin system and import to target system

[savitaarora]

Hello Experts,

We have one requirement to merge two CDC environments into one environment. Both environments have their own sites. Can we export or copy site from one (original CDC system) to another CDC tenant?

Please suggest.

Thanks,

Savita

[igal_mi · Accepted solution]

Hi Savita,

There is no single click function of export/import entire site but it can still be achieved rather easily.

What you need to do is the following set of steps:

1. Create a new site in the target environment so you have a new apikey.

2. Transfer the configuration from the origin apikey to the new apikey. You can use the copy config tool for that:

https://help.sap.com/docs/SAP_CUSTOMER_DATA_CLOUD/8b8d6fffe113457094a17701f63e3d6a/414d097270b21014b...

3. Transfer the accounts using an IdentitySync job:

https://help.sap.com/docs/SAP_CUSTOMER_DATA_CLOUD/8b8d6fffe113457094a17701f63e3d6a/2b717202e42a4165a...

Hope this helps, reach out if you get stuck on one of the steps.

Igal

[savitaarora · Accepted solution]

Thanks Igal for the detailed information.

Savita.

[savitaarora · Accepted solution]

Hi Igal,

Please help to understand below queries:

- Will Copy Configuration work if CDC partner IDs are different.

- Two active sites along with data. If we create new site-group and adding active sites into newly created site-group then data of active site will be lost. How we can save that data?

Thanks,

Savita

[igal_mi · Accepted solution]

Hi Savita,

- Yes, as long as you have access to both apikeys, the partner ID that they belong to does not make a difference.

- Not sure I understand the question. If you are asking how to move the users of an active site to a new apikey, then I would take the following apprach:

1. Run an IdentitySync Dataflow to move all users from origin apikey into target apikey.

2. Update implementation (i.e. gigya.js) to look at the new apikey

3. Run an additional IdentitySync Dataflow to move all users that were lastUpdated > timestamp of step #2 into the new apikey.

Hope this answers the question

Igal