Reactivation should not begin with "upload list, send campaign." It should begin with understanding, cleaning, verifying and segmenting the database first. This guide walks through the practical steps — duplicates, consent, opt-outs, contact sources, CSV imports and workflow testing — before any message is sent.
A business opens an old spreadsheet and finds 2,800 contacts. That number sounds impressive. But the list may contain duplicates, old email addresses, disconnected phone numbers, previous opt-outs, incomplete records, customers mixed with leads, contacts with no known source and records collected for completely different purposes.
The question is not "How many contacts do we have?" The better question is: "How many contacts do we actually understand well enough to use appropriately?"
Database size is not the same as database quality.
Potential benefits of cleaning first include:
Cleaning does not automatically increase revenue or conversion rates — it improves the reliability and appropriateness of what you send.
Before editing or importing anything, create a secure backup of the original data — for example a CRM export, CSV or a secure spreadsheet copy. Keep the original unchanged where practical.
If something is accidentally deleted, merged incorrectly, remapped or overwritten, the original source still exists. Do not store customer databases in insecure public folders.
Possible sources include:
Do not simply use "Database" as the source. Where possible preserve useful provenance such as original source, date added, original enquiry type and previous customer status.
Source helps determine context.
Do not treat every record identically. Useful broad categories might include:
Do not include employees, suppliers or unrelated contacts in a marketing campaign merely because they appear in CRM.
Common duplicates include:
Duplicate problems can cause repeated messages, conflicting stages, confusing reporting and separate conversation histories.
HighLevel currently provides contact deduplication controls. Its current documentation states matching during CSV updates or imports can use identifiers such as Contact ID, Email or Phone depending on configuration.
Do not merge two records unless you are confident they represent the same person.
Current HighLevel functionality includes Contact Deduplication Preferences. Businesses can configure whether duplicate contacts are allowed and which field is primarily used to identify existing contacts.
Depending on configuration this may include:
HighLevel can update existing contacts during imports rather than creating unnecessary duplicates when matches are identified. Review your deduplication settings before a major import.
Review fields such as:
Examples of poor data: JOHN SMITH, john smith, John, 0412 345-678, +61 412 345 678.
The objective is not cosmetic perfection — it is consistency that helps matching, segmentation, workflow logic and staff understanding. Do not overwrite useful original data without reason.
Potential issues:
An old phone number may eventually belong to someone else. Do not assume a phone record that was correct five years ago is still correct today. If data quality is uncertain, be conservative.
Potential problems:
Do not repeatedly send to addresses that are known to be invalid. Do not interpret a deliverable address as evidence of marketing consent.
Existing opt-out information should not be deleted simply to make the list larger. Preserve SMS opt-outs, email unsubscribes, Do Not Disturb status where applicable and relevant channel preferences.
An unsubscribe record is useful data — not clutter to remove.
Do not re-import opted-out contacts in a way designed to bypass suppression.
Before marketing communication, understand:
For Australian commercial SMS or email, current ACMA guidance requires appropriate consent, and the sender should be able to substantiate consent. Do not attempt to manufacture consent retrospectively. This is general information, not legal advice.
Useful CRM information may include, where genuinely available:
Do not fabricate consent dates or statuses because the old system did not record them. If consent is genuinely unknown, mark it as unknown.
Unknown is better than invented.
Examples:
Do not simply delete potentially important historical customer information without considering retention requirements and business needs. This article is about campaign preparation, not legal data-retention advice.
If a business cannot determine where the contact came from, why it was collected, the previous relationship or communication expectations, do not automatically place the record into the marketing segment.
A safer operational category might be: Source Unknown — Review Required. This keeps uncertain contacts separate.
Potential useful segments:
Do not create dozens of segments unless the business can actually use them.
Useful for labels or categories such as:
Useful for structured information such as:
HighLevel allows tags to be added during CSV imports and tags can also trigger workflows. But do not let adding an import tag accidentally launch a live marketing workflow before the database has been reviewed.
Suppose reactivation-ready starts an SMS workflow. If that tag is applied to 2,000 contacts during import, the workflow could potentially start for all qualifying contacts.
Therefore:
Do not accidentally combine database cleaning and live campaign activation.
Do not copy every historical column into the new CRM. Potential useful fields:
Potentially unnecessary:
Import useful context, not historical clutter.
When importing into HighLevel, review each CSV column. Example:
| CSV Column | CRM Field |
|---|---|
| First Name | First Name |
| Last Name | Last Name |
| Mobile | Phone |
| Email Address | |
| Service | Service Interest custom field |
| Source | Lead Source |
| Segment | Tag |
HighLevel's current documentation advises checking mappings carefully before finalising the import. Unneeded columns can remain unmapped.
Current HighLevel documentation states that contact imports use CSV. Do not upload .xlsx directly as the standard contact-import format. If the business has an Excel or Google Sheets file, convert or export the relevant sheet to CSV first.
Current HighLevel guidance also says to:
An old import might contain empty fields where the live CRM contains current information. Careless imports could potentially replace or interfere with useful information depending on settings and process. Review update behaviour carefully.
HighLevel currently offers import controls related to handling empty values. The principle:
New import does not automatically mean newer information.
Where appropriate retain:
This may help staff understand a reply. But do not import unlimited notes or sensitive history just because it exists — only retain information legitimately useful to the business.
After cleanup, create a deliberate group for review. For example:
Database → Cleaned → Source Known → No Existing Opt-Out → Relevant Segment → Consent / Communication Basis Reviewed → Reactivation Candidate
This should not automatically mean "send immediately." It means "ready for final review."
Answer:
If those questions cannot be answered clearly, the workflow is not ready.
Example:
Approved Segment → Message → Wait → Reply? YES → Stop workflow → Notify human. NO → Optional limited follow-up → End
Do not begin with a complicated 20-step automation. See our guide on practical business automation for the broader trigger-and-action model.
Stop when:
Every automated campaign needs an exit.
For Australian commercial SMS or email, ensure applicable requirements are addressed. Current ACMA guidance requires commercial messages to generally:
Current ACMA guidance says unsubscribe requests generally need to be actioned within 5 working days, and the unsubscribe method should remain functional for at least 30 days after the message is sent.
Before contacting actual customers, test the entire flow. Check:
Never assume a workflow is correct simply because it saved successfully.
Do not necessarily launch to the full eligible database immediately. A controlled initial segment can help expose:
Do not prescribe one universal batch size. The correct size depends on the business and its ability to respond.
This is critical. If a campaign produces conversations, someone needs to:
Do not launch outreach at a volume the business cannot reasonably service.
The campaign is not finished when someone replies. That's when the real conversation begins.
Potential operational signals:
Use what the campaign reveals to improve the database.
Campaign → New Information → Update CRM → Better Data → Better Future Segmentation
Examples:
CRM should become more accurate over time.
Old records may eventually stop being useful. Businesses should have sensible processes for reviewing, correcting, archiving and deleting where appropriate and lawful.
Do not prescribe universal retention periods. Different legal and business requirements may apply.
Be particularly cautious. Do not create marketing segments based unnecessarily on:
If a CRM contains sensitive information, businesses need to consider applicable privacy requirements carefully. For dental and health businesses especially, do not import clinical history into a generic marketing CRM merely to run a campaign. Use OAIC guidance where applicable.
A practical setup may connect:
Clean CRM Database → Approved Segment → SMS / Email Workflow → Reply → Human Follow-Up → CRM Pipeline
See our Reactivation & Follow-Up System for how this is built. No sales results are promised.
When assessing a business process, database health may reveal:
These are process and data-quality opportunities — not guaranteed revenue leaks. This may later support JMG Nitro's planned Free Local Growth Audit.
For the foundational concept, see our guide on what database reactivation is, our comparison of database reactivation vs cold outreach, our guide on what a CRM is and whether a small business needs one, and our guide on which small business tasks to automate. To explore a managed reactivation campaign, see our database reactivation service.
This article provides general information only. Businesses should review current ACMA and OAIC guidance and obtain professional advice where appropriate.
A reactivation campaign is only as reliable as the database behind it. See how JMG Nitro reviews, cleans and segments existing contacts before any message is sent — and how replies flow into a controlled follow-up process.
Other practical guides connected to this topic.
The foundational concept — reconnecting with suitable existing contacts where relevant and appropriate, not blasting an old list.
Read guideDatabase ReactivationHow reactivation (existing context) differs from cold outreach (new prospects) — and when each approach may suit a small business.
Read guideCRM, Automation & Follow-UpWhere existing contacts live — and how a CRM organises the records a reactivation campaign draws from.
Read guideBook a free demo to walk through how JMG Nitro's systems could fit around your existing business process.
0485 099 000
Back to Resources