Are you Migration-Ready?
There are a few things you should consider before moving your APSIS Pro data into APSIS One. It is very important for us that you have the best experience migrating data. At the same time, we would like to encourage you to perform a close inspection of the data you have in store today. You will save time and resources and will end up having a more satisfactory experience migrating to APSIS One overall.
In this article
APSIS Pro Mailing Lists
Let's take a look at your Pro account. As you review your APSIS Pro lists, ask yourself these questions:
Which of these lists are worth transferring into APSIS One?
When was the last time you used these lists, and do you see them as something you will use time and time again?
Proceed to separate those lists that you use most often and that best represent your customer base. You may choose multiple lists.
Another important step is to review your data formats. In order for your data to migrate effectively into APSIS One, make sure your data's in the right format. Read more about the supported data formats in this article...
If you currently dont use the SMS service in APSIS Pro, you will have to import phone numbers separately through our File Import Wizard.
Your mailing lists will be converted into Topics inside Consent lists in APSIS One.
APSIS One Consent lists & Topics
Consent lists are a group of Topics, and Topics are the level in which subscribers provide consent. A Topic is the equivalent of a mailing list in APSIS Pro. Inside a Topic, Profiles will be created. A Profile in APSIS One is the equivalent of a subscriber in APSIS Pro, yet it has a bigger potential for storing valuable information.
Take a look at these examples:
Company A Example
Company A operates within two different markets, the clothing market and the furniture market. They have a total of 7 lists in APSIS Pro.
3 mailing lists are only used to communicate to their subscribers that are interested in furniture.
4 mailing lists are only used to communicate with the subscribers that are interested in clothing.
Because the company would never direct a sending towards both the furniture and clothing lists at the same time, they decided to create two Consent lists.
One Consent list for the clothing market, with 4 Topics for each list that they had in Pro, and a second Consent list for the furniture market, with three Topics for each list in Pro.
Company B Example
Company B has five mailing lists in APSIS Pro and sometimes sends a newsletter to all of their lists at the same time. Therefore, they created one Consent list in APSIS One, with 5 Topics that they matched with each corresponding list in APSIS Pro.
Company C Example
Company C offers services within 3 different service sectors: legal advice, financial counselling and business ethics.
In the companys APSIS Pro account they have a total of 6 different lists, with each service sector having two lists each.
Since they sometimes do one sending directed towards both the legal advice sector and the business ethics sector, they decide to organise them as 4 Topics into one consent list called "Legal Advice and Business Ethics". However, they never combine the lists of the financial counselling sector with any of the other lists when doing a sending. Therefore, they create a second Consent list named "Financial Counselling", with its respective two Topics.
Legal Advice & Business Ethics
APSIS Pro Demographic Data
Demographic data is migrated into APSIS One in the shape of Attributes inside a Profile. Attributes are the essential information that Profiles have provided with their consent. Just like in APSIS Pro, they can be a first or last name, country, address, etc.
Which demographic data fields do you want to migrate as Attributes? The two factors to consider are whether they are useful, and if they're consistent.
A good rule here is to only choose the ones that you have the intention of using in APSIS One. Are they useful for personalization purposes in email or SMS campaigns? Are they useful for creating segments in APSIS One? Demographic data fields like first name, last name, country and gender are generally very useful.
Check the consistency of values for each demographic data field you want to migrate. Do all of your subscribers have a value for those demographic data fields? For instance, if you notice that only 30 of your 10000 subscribers in APSIS Pro have a postal code, you might want to consider leaving it out. A potential segment based on a postal code condition will only include a very small amount of Profiles.
When you're in the Migration Wizard, simply skip mapping the demographic data fields that you don't intend to migrate.
Campaign Response Data
Campaign response data is migrated into APSIS One in the shape of Events a Profile has performed. Events reflect the Profile's engagement and activity in relation to your brand. In APSIS Pro you may only gather Events from email and SMS campaigns. But APSIS One includes a wider range of interactions: like website clicks, filling sign-up bars, cookie consent, etc.
For now, we can only migrate email response data. We will notify you when migrating SMS response data becomes available.
Which email Events do you want to transfer, and what are the most valuable for your business? Consider clicks, opens and bounces, for example. You may use Event data to create segments to target Profiles who have interacted with your brand via Pro sendings before.
You must also think about the date that your subscribers performed these actions on. In your database, you may have campaign response data from a long time ago. Most likely you only need to keep the Events from the last two years.
Decide on a date range for the Events you want to transfer before the migration. You will have to make a choice later, in the Migration Wizard.