If you store your V2 data locally, such as your contacts, email campaigns, and contact lists and you want to migrate your integration to V3, you need to get the object that contains the new V3 cross reference ids that correspond to to your exist V2 ids.
Click the FAQ title to expand or collapse FAQ details.
How do I….
Migrate V2 contact data to V3?
Use the GET /contacts/contact_id_xrefs
endpoint and sequence_ids
query parameter to get the contact cross references used by the V3 API. When you send your comma delimited list of V2 id
values, you get the new V3 cross references in the response body as key-value pairs; sequence_id
(the same value as the V2 id
) and the new UUID formatted contact_id
. For details, see Contacts V3 Changes and Migration.
Migrate V2 campaign data to V3?
Use the GET /emails/campaign_id_xrefs
endpoint and v2_email_campaign_ids
query parameter to get the new V3 campaign data identifiers used to cross reference your existing V2 campaign data. When you send your comma delimited list of V2 campaiginId
values, you get the new V3 cross reference ids in the response body; v2_email_campaign_id
(the same value as the V2 campaignId
), and the new UUID formatted campaign_id
and campaign_activity_id
. For details, see Email Campaigns V3 Changes and Migration for more information.
Migrate V2 contact lists data to V3?
Use the GET /contacts/contact_lists/list_id_xrefs
endpoint and sequence_ids
query parameter to get the new V3 contact list identifiers used to cross reference your existing V2 contacts list data. When you send your comma delimited list of V2 id
values, you get the new V3 cross references in the response body as key-value pairs; sequence_id
(the same value as the V2 id
) and the new UUID formatted list_id
. For details, see Lists V3 Changes and Migration for more information.