Essential Information

Before you get started with the migration, you might want to know more details about APSIS One. Here's a few texts that will help you get acquainted with APSIS One's terminology and structure.

In this article

Your APSIS One Account

Your APSIS One account is where you will move your subscriber data from APSIS Pro into. Moving forward, this is also where you will set up and invite your team, manage permissions, and configure how you will gather and structure your customer data.

Sections and Domains

In Account Settings you manage your Sections and domains.

Organising your data and users into Sections is important for your work in APSIS One. Smaller businesses may not need to have more than one or two Sections. However, it depends on the structure and permissions you wish to have in the account and your subscribers' consent. If you dont have a master and a sub-account set up in APSIS Pro, it is likely that you will only need one Section.

If you plan on using APSIS One in a completely different way, we recommend that you reach out to us to discuss your Sections. In a nutshell, using Sections allows you to organise your data. It will also simplify the task of giving users access to different data.

This is one of the big benefits of using Sections: giving users Section permissions helps ensure that the right data is always in the right hands. What is more, to enable tracking website data, you must add your domain(s) into a Section. This is not part of your migration, and is a step you can return to after you have set up your migration.


Audience Data

Audience is the APSIS One pillar where you will have the possibility of creating and managing Subscriptions, visualizing your Profiles and their growth, and performing GDPR-related tasks.

A Subscription is a record or list of Profiles who have given their consent to receive communication from you. Profiles will be able to subscribe and unsubscribe to several different Subscriptions as they wish different communication from you.

To be able to communicate with your customers, members, or subscribers from APSIS One, they must be subscribed to a Subscription.

Consent is given and removed on Subscription level. Only create a Subscription if you want profiles to be able to unsubscribe from that Subscription.

Use the segment builder to bundle your profiles instead of creating too many Subscriptions, making it impossible for people to unsubscribe from communication and giving your subscribers a bad experience. Learn more here.

Profiles are the APSIS One equivalent of a subscriber in APSIS Pro, with a few exceptions. Essentially, a Profile represents an individual that has provided some type of consent. Profiles contain data from subscribers in the shape of Attributes. An Attribute can be a name, last name, mobile number, email, country, etc. Many things that you have in APSIS Pro today as demographic data can be transformed into Attributes in APSIS One in your migration.

A different data type linked to a Profile is Events, which reflect their activity in your domain and email or SMS campaigns (clicks, opens, etc.). In APSIS Pro, the equivalent is Campaign Response data. Attributes and Events will allow you to create Segments in order to target the right audience in your campaigns.

The number of Profiles your account may contain at once is also dependent on the APSIS One package you currently have. You will be able to create Segments, which allow you to group Profiles according to specific Segment conditions (Attributes and Events).


Time to dig deeper into the transference of data from your existing APSIS Pro accounts into APSIS One. We strongly recommend that you read the text above to make sure you grasp every concept.

Here we will be speaking strictly about how the Migration Wizard migrates your subscriber, subscription and campaign response data into APSIS One's Subscription and Profiles.

These are the equivalences:



Subscriber data

Profiles and their Attributes

Subscription data

Channel Consent in a Subscription

Demographic data

Profiles and their Attributes

Campaign Response data

Profiles and their Events

Opt-out all

Section Opt-out

The Migration Wizard first gathers your subscriber data and creates Profiles in APSIS One with their demographic data added as Attributes.

Then it allows you to create APSIS One Subscriptions where you will be matching your subscriptions so that your Profiles can have their consent registered as channel consent. If a subscriber has performed an opt-out or an opt-out all, their subscription status will be shown respectively in APSIS One: meaning that all Profiles will show their channel consent, including opt-outs.

Finally, the campaign response data is added to the Profiles that it corresponds with as Events.

It sounds simple, and it is, but there's much to understand about this process: it is your responsibility that the lists that you migrate into APSIS One are carefully matched with a relevant Subscription. After all, you will be working with nothing more than your valuable subscribers' consent. It is preferable that you have in mind a structure for your APSIS One account before you migrate. Migrating into APSIS One requires that you grasp its concepts in order to optimise your data management.

The advantage of having a Migration Wizard is being able to migrate all your APSIS Pro data as you switch to APSIS One. This way, you will not have to do it manually. Once a day, it will continue to migrate data during this transition period (optional). By migrating gradually, you get to keep your current APSIS Pro subscription forms, API integrations, opt-out management, etc. for as long as you need them.

Data migration is not a long-term solution, but a temporary transition solution. Not only do we encourage that you proceed to enjoy working with APSIS One, but also we recommend that you change and replace your data sources. Its best to feed data directly into APSIS One and Eventually disable the Migration Wizard. As a part of our APSIS Solutions, we offer a special package for those who are interested in a seamless migration experience.

Did this answer your question?