A contact file is not yet a campaign segment
An example Lublin business may hold addresses from a newsletter form, order system and previous mailing tool. This is a data-preparation scenario, not a claim about an identified local customer list. Each source needs field descriptions, its export date and an explanation of how statuses are maintained.
Purchase information and communication settings are kept separate. An entry in a CRM or an earlier order does not automatically define campaign rules. The owner confirms which messages each group should receive and which information supports that distinction. Initial discussions only need a column structure without real addresses.
Carry statuses and exclusions alongside the records
Mailchimp distinguishes contact statuses including subscribed, unsubscribed and non-subscribed, and documents suppression lists. Before import, we map the equivalents in the current and destination tools rather than assume identically named fields mean the same thing.
The plan defines duplicate identification and how conflicting information from two sources is handled. A record needing clarification is marked for a decision rather than immediately entering a send. We retain a reconciliation of incoming, skipped, combined and unresolved records.
Test the rules on a sample before a larger batch
The test includes a record for each status, a duplicate and a missing important value. We inspect field mappings, segments and whether an excluded contact entered the proposed campaign group. Tests use agreed sample data or a specifically approved process.
Acceptance compares the rules with import results, not just a completion notice. Campaign content, automation, migration and sending follow separately agreed requirements and pricing. Preparing an audience does not automatically start messages to every record.
Local context and sources
GUS recorded 56,912 REGON entities in Lublin city for 2025. These registration data do not establish demand, mailing audience size or future customers for this service.
Entities registered in REGON
56912 · 2025 · Lublin — city
City-only REGON information, not a measurement of search demand or a source of campaign recipients.
Check the sourceQuestions before starting
Must a Lublin business provide its full audience for a quotation?
No. Start with data sources, field names, approximate record counts and the tool in use. Data-access arrangements are agreed separately.
Will unsubscribed addresses return to campaigns after import?
The rules should preserve statuses and exclusions. Their mapping is tested on a sample; presence in a file is not a reason to change them all.
Does moving contacts include a new message sequence?
Only when it is part of the agreed project. Audience preparation, tool migration and campaign creation may have separate scopes.
Related services and locations
Other services for this city
Discuss your email marketing
Describe your email platform and the messages you want to prepare.
Discuss your email marketing