You have an audience you have built over time: learners, people who asked about a programme, newsletter readers and people who no longer want marketing. When you change systems, those differences need to survive. A file containing every email address can look complete while losing the reason you may—or may not—contact each person.
For your Leeds training business, the immediate job is not to make the new audience count match a headline. It is to give your assistant a clear specification and a reliable check before the next programme announcement. Labels can explain an interest; they cannot supply missing permission.
Use this as an export specification, not instructions for a complete one-click migration. Gbeya’s current subscriber download does not establish the full combined permission, restriction and label record described here. The contact import path also needs a safer subscription default before it can be relied on for this purpose. Keep the existing audience system authoritative until the handover checks pass.
Can your assistant explain one imported record?
Use representative test records, not an unprotected copy of the live audience.
- Identify the purpose and channel of the intended communication.
- Find the source status and the evidence supporting it.
- Check every restriction, label and relevant timestamp against the mapping.
- Re-import a conflicting older row and verify that restrictions are not silently removed.
- Reconcile a preference change made after the first export before activation.
Any unexplained status change keeps the affected records out of the marketing cutover until resolved.
A technical mapping check does not determine the legal basis for every contact or certify the entire campaign.
Step 1
70 · Supported newsletter permission
Retain purpose, channel and supporting evidence.
Step 2
20 · Opted out
Preserve the restriction when records move.
Step 3
10 · Evidence needs review
Keep uncertainty visible rather than defaulting to subscribed.
Step 4
100 · Matching total
A matching record count does not prove the choices survived.
These are assumed example counts. The same total with every record subscribed would silently change thirty records; campaign eligibility remains a separate decision.
1. Give status, labels and evidence different fields
Start by separating three questions: who is this person, what do your labels mean, and what supports the proposed communication? A label such as leadership-course-interest helps organise the audience. It does not establish that the person agreed to every future programme announcement.
For UK electronic marketing, the applicable rules depend on the message and recipient type. Consent is not the only possible route in every circumstance, and a customer record is not a universal permission slip. Record the actual basis used for the intended communication and obtain appropriate advice where that basis is unclear. This guide is operational documentation, not legal advice.
- Why this matters
- Separate fields prevent a useful business category from being mistaken for a communication permission. When a source has no evidence, preserve the unknown rather than filling it with a favourable default.
- Work through the example
- A person may be a paid learner, tagged for a management programme and unsubscribed from promotional email. Preserve all three facts. A course-access message and a new sales campaign require their own purpose checks.
- When the approach changes
- If a person specifically requested a particular reply, that is a different situation from adding them to an ongoing promotional sequence. Do not flatten both into the same marketing flag.
- Your decision
- Keep the intended channel, purpose, status and evidence separate. Neither purchase history nor an interest label should silently change a marketing choice.
2. Preserve what the person was told, not just a yes value
Where you rely on consent, retain the evidence that explains it: the person or identifier, when and how they acted, the relevant wording and the organisation and purpose covered. A date when a row was created is not automatically the date of consent. An export date tells you when the copy was made, not when the choice happened.
Use a stable reference to the wording shown at the time, with its version or dated copy. Your assistant should be able to follow the reference without guessing which current form replaced the original. Keep sensitive supporting material in an appropriately restricted location rather than placing unnecessary detail in a widely shared sheet.
- Why this matters
- Provenance is the history that gives a status meaning. A destination can store a status accurately while still losing the evidence needed to explain why it was set.
- Work through the example
- Suppose the source contains a newsletter opt-in timestamp and a form version. Export both, together with the channel and purpose. If the original wording is missing, record that evidence gap; do not substitute the new website’s wording as though the person saw it.
- When the approach changes
- Some lawful marketing arrangements are not consent-based. Do not manufacture consent records to force those contacts into a consent-only schema. Record the actual basis and review its scope.
- Your decision
- Reconcile the status and its supporting evidence independently. Unknown wording, time or scope must remain visibly unknown until resolved.
3. Move the no-contact information as carefully as the active audience
An export that only carries active subscribers may leave the destination unable to recognise someone who opted out. Preserve the restrictions needed to avoid reintroducing them through an old spreadsheet, form import or duplicate record. A suppression record is a restriction used to prevent contact; it is not a fresh marketing audience.
Keep different reasons distinguishable where the source provides them. A withdrawal, a delivery failure and a manual restriction are not the same event. You do not need to collect extra information to make the file look thorough; retain what is necessary for the restriction and the agreed retention purpose.
- Why this matters
- A restriction must survive identity matching and later imports. Otherwise the same person can return through another source row and appear newly contactable.
- Work through the example
- Your source has an unsubscribed learner with a course-interest tag. In the test destination, import the record and then import an older row for the same identifier. The later import must not silently remove the restriction merely because its file is newer.
- When the approach changes
- A genuine later permission change can need a different result, but it requires its own valid evidence and handling. A newer export timestamp alone does not establish a new choice.
- Your decision
- Preserve restrictions before enabling marketing. Treat conflicting evidence as a review case, not an instruction to choose whichever status produces the larger audience.
4. Test what the destination actually reads
A file can contain the right columns while the importer ignores them. Write a source-to-destination map before applying it: each source field, its meaning, destination field, conversion rule and what happens when it is blank. Test labels with commas and multiple values so they do not become accidental extra columns or merged categories.
Gbeya’s subscriber export currently provides email, name, source, confirmation status, unsubscribe time and record-creation time. That is not the complete permission-and-label record this move needs. The contact import path reviewed on 30 October 2026 marks new contacts as subscribed, so do not use it for a consent-preserving migration until that default and the field mapping have been corrected and demonstrated.
- Why this matters
- Mapping determines which source facts survive. An unmapped restriction is lost even when every row imports successfully. A favourable default can also create a status the source never supplied.
- Work through the example
- Use a safe test file with a permitted subscriber, an opted-out person, an unknown status and a duplicate with conflicting history. Confirm the resulting fields and eligibility one by one. A successful import summary is not enough.
- When the approach changes
- A basic contact import can be useful for non-marketing administration, but that does not justify activating marketing status for unknown records. Purpose and safe defaults still matter.
- Your decision
- Hold the marketing cutover until the exact import path preserves restrictions and unknowns. Keep the current system authoritative while missing controls are built.
5. Reconcile changes before you resume campaigns
Compare more than total rows. Count status groups, restrictions, unknowns and duplicates, then inspect representative records without exposing unnecessary personal information. Keep a dated export receipt, the mapping version and the test results so another authorised person can understand the decision.
Preferences may change while you prepare the move. Decide how late opt-outs and corrections will reach the destination before campaigns resume. Recheck the relevant restrictions at the point the new workflow uses them; a clean file from last week is not evidence of today’s preferences.
- Why this matters
- A cutover changes which system is responsible for the current state. Reconciliation identifies missing or changed meanings, while a final change check covers the gap between the export and activation.
- Work through the example
- Suppose someone opts out after the first export. The final check should identify that change, update the destination and prove that the planned campaign excludes the person. Use a controlled test environment; do not send a real campaign just to discover whether the rule works.
- When the approach changes
- For a read-only archive with no intended sending, activation checks differ. You still need appropriate access, retention and reliable interpretation of the saved records.
- Your decision
- Resume only after the responsible owner can explain the remaining discrepancies and the current restriction state. An import count is a transfer receipt, not proof of permission or delivery readiness.
Fields to agree before export
Proposed specification; not a claim that the current Gbeya download contains every field
- Stable source identifier
- Match the same record without relying on display names.
- Channel and intended purpose
- Keep email, other channels and purposes separate.
- Status and restriction reason
- Preserve opted-out, suppressed and unknown states.
- Choice timestamp and source
- Distinguish the original event from row creation and export time.
- Evidence reference and wording version
- Retain a restricted, retrievable record of what supports the status.
- Labels with defined meanings
- Preserve categories without treating them as permission.
- Export and mapping version
- Identify the copy and transformation used for reconciliation.
Keep the relationship intact through the move
For your Leeds business, we would prioritise the meaning of the record over the size of the imported audience. Clear restrictions and unknowns are useful information, not clutter to clean away.
There is a practical tension between keeping enough evidence to explain a choice and copying unnecessary personal information into more places. Use a minimal operational export with appropriately restricted supporting evidence, and decide who can access each part.
The export and import gaps described above give the handover a concrete specification. Keep current communication choices intact while those gaps are corrected. A smaller, explainable audience is more useful than a matching total whose meaning has changed.
Medium confidence in this export planning specification. Product limits describe the 30 October 2026 review and require rechecking after changes.
UK guidance is context-dependent; consent guidance is under review following legislative changes. This is not legal advice or proof of complete platform compliance. No live audience was exported, imported or contacted.
Reconciliation using stated assumptions
The same total can hide changed choices
Suppose your source contains one hundred unique records: seventy with supported newsletter permission, twenty with an opt-out and ten whose evidence needs review. The destination also shows one hundred records. If all one hundred become subscribed, the total matches but thirty records have not retained their source meaning. Your first check is seventy, twenty and ten in the corresponding reviewed categories, followed by field-level tests. Suppose two hours of review are allocated at an internal £40 per hour: that is £80 of planned time value, not a supplier fee, measured saving or additional cash loss.
70 + 20 + 10 = 100 records; 20 + 10 = 30 records that must not become subscribed by default.
Those seventy records are not automatically eligible for every future message. Channel, purpose, current preferences and the applicable rules still need to match the proposed campaign.
Reconcile meaning before totals, and keep the permission decision separate from import success.
Assumptions worth checking
If the total record count matches, the migration is complete.
A matching count can hide changed choices. Compare permission, restrictions, unknowns and supporting evidence before accepting the handover.
My experienced team can use the latest spreadsheet as the final truth.
The newest file can still contain older preferences. Compare the original choice time and evidence; an export timestamp must not overwrite an opt-out.
An interest label gives us permission to send the next programme announcement.
It describes an interest. Review the intended message, channel, actual basis and current restrictions separately.
Your next 30 days
Days 1–7
Inventory the evidence
Identify the actual source fields, status definitions and missing permission evidence.
Ready for the next step: Unknown values are listed without invented replacements.
Days 8–14
Agree the mapping
Define safe defaults, restriction precedence and authorised access; keep campaigns on the existing authoritative system.
Ready for the next step: Every exported field has a destination or an explicit retained evidence location.
Days 15–21
Rehearse the edge cases
Test duplicates, opt-outs, unknowns, labels and post-export changes in a safe environment.
Ready for the next step: Counts and individual states reconcile; failures are corrected before activation.
Days 22–30
Decide the cutover
Apply the final change check and review the proposed campaign separately before switching responsibility.
Ready for the next step: The owner can explain the current state and unresolved exclusions. Thirty days is a review window, not a compulsory send date.
Questions before you proceed
Does a label prove permission to market?
No. A label describes a category. Keep the actual communication basis and supporting evidence separate.
Is the export timestamp the consent timestamp?
No. It records when the copy was created. Preserve the original choice time where it is known; do not replace a missing value.
Should opted-out contacts be omitted from every file?
Not necessarily. Appropriate restriction records can help prevent accidental reintroduction. Keep them restricted and purpose-limited, rather than treating them as an active audience.
Does the current Gbeya subscriber export include everything described here?
No complete combined export was verified. The subscriber download covers six basic fields; labels, restrictions and the full evidence behind permission require additional work.
Can I use the contact importer for this migration now?
Do not rely on it for preserving marketing choices yet. The path reviewed on 30 October 2026 marks new contacts as subscribed. Its defaults and field mapping need correction and testing for this purpose.
Does a successful import mean I can send a campaign?
No. Import success, the basis for a message, current preferences and delivery readiness are separate checks.
Sources and further reading
Prepared by Gbeya · Sources reviewed 30 October 2026.