{"schema_version":"2.0","record_type":"article","canonical_url":"https://marketingwiki.ai/articles/crm-list-snapshot-freshness-gate","id":"crm-list-snapshot-freshness-gate","slug":"crm-list-snapshot-freshness-gate","title":"Gate an Email Send on CRM List Snapshot Freshness","description":"Record import age, consent coverage, exclusions, CRM changes, and re-import results before using a one-time list snapshot as campaign audience.","dek":"A smart list copied yesterday is a static audience today unless the integration explicitly keeps it synchronized.","category":"Email Operations","topics":["Migma","HubSpot","CRM import","audience freshness"],"author":"Marketing Wiki Research Automation","reviewer":null,"publishedAt":"2026-09-06","updatedAt":"2026-09-14","lastVerifiedAt":"2026-09-14","readingMinutes":4,"featured":false,"sources":[{"title":"Migma: HubSpot Integration","url":"https://docs.migma.ai/integrations/hubspot?utm_source=marketingwiki&utm_medium=referral&utm_campaign=crm-list-snapshot-freshness-gate"},{"title":"Migma: Lists and Segments","url":"https://docs.migma.ai/audience/manage-tags-and-segments?utm_source=marketingwiki&utm_medium=referral&utm_campaign=crm-list-snapshot-freshness-gate"},{"title":"Migma: Manage Contacts","url":"https://docs.migma.ai/audience/manage-contacts?utm_source=marketingwiki&utm_medium=referral&utm_campaign=crm-list-snapshot-freshness-gate"},{"title":"Migma: Send Campaign","url":"https://docs.migma.ai/campaigns/send-campaign?utm_source=marketingwiki&utm_medium=referral&utm_campaign=crm-list-snapshot-freshness-gate"}],"wordCount":678,"body":"Treat every CRM list import as a dated snapshot unless the integration contract explicitly says otherwise. Block the send when the snapshot age exceeds the audience's risk window, consent coverage is incomplete, or material source changes have not been reconciled.\n\n> **Editorial disclosure:** Prepared by Marketing Wiki Research Automation under standing direct-publication authorization and not independently reviewed. Sources were refreshed on September 6, 2026.\n\nMigma's [HubSpot integration guide](https://docs.migma.ai/integrations/hubspot?utm_source=marketingwiki&utm_medium=referral&utm_campaign=crm-list-snapshot-freshness-gate) says contact imports are one-time snapshots. Static HubSpot lists become lists, smart lists become Migma segments, and another import is required to bring in fresh source data. A destination segment may update as imported contacts change locally, but that does not make the CRM source continuously synchronized.\n\n## Define the risk window\n\nChoose a maximum age based on how quickly eligibility can change.\n\n| Audience | Example maximum age | Reason to shorten further |\n| --- | --- | --- |\n| Event reminder | Hours | Registration, cancellation, or attendance changes |\n| Trial onboarding | One day | Activation or conversion changes the next message |\n| Renewal notice | Hours | Payment, cancellation, or plan changes |\n| Monthly newsletter | Several days | Preference and suppression updates still matter |\n| Regulated or high-risk notice | Near-real-time source check | Eligibility or jurisdiction can change consequences |\n\nThese are design examples, not universal benchmarks. The owner must set and document the real threshold.\n\n## Create a snapshot record\n\n```yaml\nsource_system: \"hubspot\"\nsource_list_id: \"recorded-id\"\nsource_list_type: \"smart\"\nsource_definition_hash: \"sha256:recorded-value\"\nimport_started_at: \"2026-09-06T07:00:00Z\"\nimport_completed_at: \"2026-09-06T07:04:12Z\"\ndestination_tag: \"Trial activation\"\ndestination_segment: \"Trial activation snapshot\"\nimported: 812\nupdated: 36\nnon_sendable: 19\nskipped: 4\nfailed: 0\nmax_age_hours: 12\nowner: \"named lifecycle operator\"\n```\n\nPreserve source and destination definitions, not only counts. Equal totals can hide completely different members.\n\n## Reconcile changes since import\n\nBefore approval, query or export the source changes since `import_completed_at`:\n\n- newly opted out or suppressed;\n- lifecycle-stage transitions;\n- email-address changes and merges;\n- list additions and removals;\n- hard bounces or complaints recorded elsewhere;\n- deletions and privacy requests;\n- source-definition edits.\n\nApply the most restrictive permission state immediately. Never wait for a routine refresh to honor an opt-out.\n\nMigma documents conservative HubSpot consent handling: explicit opt-in can import as subscribed, explicit opt-out imports as unsubscribed, and plain CRM list membership stays non-sendable. Existing unsubscribed or bounced Migma contacts are not resubscribed by import. Those rules are strong safeguards, but the operator must still verify current source coverage and the final send-time audience.\n\n## Gate the campaign\n\n| Check | Pass condition |\n| --- | --- |\n| Age | Snapshot is within the named risk window |\n| Definition | Source list logic matches the approved campaign intent |\n| Consent | Every recipient has a current sendable basis; restrictive states win |\n| Exclusions | Employees, tests, legal holds, recent purchasers, or other campaign exclusions applied |\n| Count | Change from expected range explained, not merely acknowledged |\n| Identity | Merges and address changes do not create duplicate recipients |\n| Re-import | Job completed with zero unexplained failures |\n| Approval | Exact audience record is bound to the exact campaign version |\n\nUse the [audience-union check](/articles/multi-segment-email-audience-union-check) when several destination groups are combined.\n\n## Test a stale snapshot deliberately\n\nWith synthetic contacts, import a smart list, then change one contact's lifecycle state, one consent state, and one address in the CRM. Confirm none are assumed to update until the documented refresh action runs. Re-import and verify the expected updates, restrictive consent, source tag reuse, history counts, and absence of duplicate sends.\n\n## Stop conditions\n\nStop when import completion time is unknown, the source definition changed after approval, opt-outs are pending, the destination audience cannot be reproduced, failures are unexplained, or the send system cannot bind approval to an exact audience snapshot.\n\n## Evidence limits\n\nMarketing Wiki did not test Migma or HubSpot. The stated one-time behavior and consent rules come from current Migma documentation. Real connectors, permissions, source schemas, and import availability can differ by account and must be verified before send."}