The migration process is irreversible.
Please read the document carefully before starting the migration of your SDK V4 mobile application to Adobe Experience Platform SDK.
Adobe Campaign Standard processes mobile applications using SDK V4 as separate applications from those using Adobe Experience Platform SDK.
After upgrading the Adobe SDK version from v4 to Adobe Experience Platform, mobile applications need to continue using existing application subscriber data and campaigns: a migration is therefore needed.
This page documents the migration of a SDK v4 mobile application to a newly created Adobe Experience Platform SDK application. Your SDK v4 mobile applications will not be merged with an Adobe Experience Platform SDK mobile application with a Configured Property status.
|What will not change after the migration|
|There will be no effect on existing deliveries and campaigns using the migrated SDK V4 application.|
|The name of the mobile application will remain same.|
|The platform credentials for iOS and Android will be retained.|
|All the subscribers of the application and their data will be retained.|
|The existing SDK v4 mobile application will continue to send data (PII data, Subscriber & token information) to Adobe Campaign Standard.|
|The Organizational unit of the mobile application will remain same.|
|What will change after the migration|
|The mobile application will be available in Administration > Channels > Mobile app (Adobe Experience Platform SDK). Before migration, it was available in Administration > Channels > Mobile app (SDK V4).|
|The Collect PII Endpoint of the application will change. The older Collect PII Endpoint will continue to work, sent data will not be lost.|
|The application will be tied to a tag Mobile Property. It will be processed as a newly created mobile application.|
|The original Adobe Experience Platform SDK application used in the migration will not exist as a separate application. Only the migrated SDK v4 application will be available.|
Before migrating, you should take into account the following recommendations:
Create a new Mobile property in the Data Collection UI. For more information on this, refer to the documentation.
In Adobe Campaign Standard, from the advanced menu, select Administration > Application Settings > Workflows and open the syncWithLaunch workflow. Check if the workflow has ended without error.
After workflow completion, from the Administration > Channels > Mobile app (Adobe Experience Platform SDK) menu, check if the mobile application is available in Adobe Campaign Standard and is in Ready to Configure state.
In Administration > Channels > Mobile app (SDK V4), select the SDK V4 application you want to migrate.
Select the Mobile application migration to AEP SDK tab.
From the Select AEP SDK mobile application to merge current application with drop-down, select the Adobe Experience Platform SDK mobile application previously created.
From the Migration application window, click Ok.
The successful completion window appears, click Go to Adobe Experience Platform SDK Channel list.
From the Adobe Experience Platform SDK channel list page, check that your previous V4 mobile application is set to Ready To Configure.
Select your mobile application and click Save to complete the migration.
After this migration, subscribers collected by the V4 version of the mobile application and new subscribers collected by the AEP version of the mobile application will be available in the migrated application.
To distinguish the two different types of subscribers, you can add a new custom field of Text type when extending the custom resource Subscriptions to an application (appSubscriptionRcp) as
appVersion for example. For more information on how to extend a custom resource, refer to this page.
You will then need to configure the associated tag Mobile property to send this custom field value in the Collect PII call and change your mobile application configuration accordingly.
A: From the advanced menu Administration > Application Settings > Options, check the value of the Enable migration of mobile app from SDK v4 to Adobe Experience Platform SDK option option. It should be set to 1 and enabled by default. Administrator may have disabled it manually.
A: Only eligible application of your Organizational unit is shown in the list. Please make sure you have the correct Adobe Experience Platform application for the migration. The Property Status of your Adobe Experience Platform application should be set to Ready to Configure and the Mobile app migration status set to Not Migrated.
A: Migration process retains the SDK v4 subscribers and attributes. It only keeps the tag related information from Adobe Experience Platform SDK application. Subscribers and other data from the Adobe Experience Platform SDK application will be lost. To avoid any data loss, only Adobe Experience Platform SDK applications with the Ready to Configure Property Status are eligible for migration.
A: The mobile application after migration will be visible from the advanced menu Administration > Channels > Mobile app (Adobe Experience Platform SDK).
A: The newly created Adobe Experience Platform SDK application used for the migration will not exist as a separate application. Only the migrated SDK v4 application will be available.
A: Administrators of the Organizational unit ALL will have the rights to manage both mobile applications and will be in charge of the migration.
A: Adobe Experience Platform SDK application being the asset of a sibling Organizational unit, the mobile application will not be visible to users of the Organizational unit A. The mobile application will be available to the Administrators of the Organizational unit ALL but we do not recommend these administrators to migrate the mobile application.
In this case, you should move your mobile applications in the same Organizational unit or in an Organizational unit with a parent link.
For more information on Organizational unit, please refer to this section.
A: The system does not store this information when the SDK V4 mobile application is created. When migrating your SDK V4 mobile application to an Adobe Experience Platform SDK mobile application, your migrated mobile application will not have this kind of information either. As soon as a user will upload a new iOS certificate or Android key, the different details of the key or certificate will be stored and displayed correctly under the Push channel settings drop-down.