Best way to export and import recipient data including tracking data from one instance to another? | Community
Skip to main content
KotiSyamala
Level 5
September 3, 2020
Solved

Best way to export and import recipient data including tracking data from one instance to another?

  • September 3, 2020
  • 2 replies
  • 1918 views

Hi Team,

 

We are planning to export and import one Adobe Campaign classic recipients along with teacking records of the each recipient. Please help us the best practices to do the same?

 

Thanks,

Koti

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by ChristopheProtat

Hello Koti,

For recipients, perfect with file export imports

Depending on your needs, I would not recommend to inject tracking from Instance 1 to an instance 2 in the OOTB tracking table. By the way the id of the recipient will be different from both instance and you will have hard time to reconcile freshly imported recipients with tracking. Second importing tracking in nms tables is highly risky as you need to embed linked object (url, etc. ...) to guarantee the system to work as expected. 

 

For tracking I would then recommend to create a custom table like "historicalTrackingData", link it to recipient with proper type of link then store this information in this table. Then you can use it for targeting purpose. 

 

Hope it makes sense. 

Christophe

2 replies

Jonathon_wodnicki
Community Advisor
Community Advisor
September 3, 2020

Hi,

 

Simplest way is to use file export/import for both.

The tracking log is just a list of id's and timestamps, you'll probably need to collect peripheral metadata as well, and also recompute aggregations computed from the table.

 

Thanks,

-Jon

KotiSyamala
Level 5
September 4, 2020
Will there be any conflicts with existing recipient ID's if yes, how do we handle them?
ChristopheProtatAdobe EmployeeAccepted solution
Adobe Employee
October 11, 2020

Hello Koti,

For recipients, perfect with file export imports

Depending on your needs, I would not recommend to inject tracking from Instance 1 to an instance 2 in the OOTB tracking table. By the way the id of the recipient will be different from both instance and you will have hard time to reconcile freshly imported recipients with tracking. Second importing tracking in nms tables is highly risky as you need to embed linked object (url, etc. ...) to guarantee the system to work as expected. 

 

For tracking I would then recommend to create a custom table like "historicalTrackingData", link it to recipient with proper type of link then store this information in this table. Then you can use it for targeting purpose. 

 

Hope it makes sense. 

Christophe