How long does a Smokeball to Mailchimp migration take?

Migration timelines for Smokeball-to-Mailchimp transfers vary based on contact volume and pre-migration preparation. Smaller datasets with fewer than 10,000 contacts typically complete within 48–72 hours after the initial export begins. Larger audiences containing 10,000–50,000 contacts require additional time for merge field configuration and extended data validation, extending the full migration to 3–5 days. The Smokeball API partner enrollment process, which is mandatory before FlitStack can access the export, adds 5–10 business days to the overall project timeline — this runs in parallel with planning activities. Merge field creation in Mailchimp and thorough contact-list cleanup represent the longest pre-import preparation steps.

Will my Smokeball workflows migrate to Mailchimp Customer Journeys?

No. FlitStack migrates data only — Smokeball workflows, automated task series, and Archie AI-assisted document workflows do not move. Mailchimp's Customer Journey builder uses different concepts (tag triggers, segment conditions, campaign send actions) than Smokeball's matter-triggered task workflows. We export your Smokeball workflow definitions as a written rebuild reference so your Mailchimp admin can recreate the logic in Customer Journeys after contacts land.

What happens to my Smokeball matters and billing data in Mailchimp?

Smokeball matters, documents, billing records, time entries, trust accounting, and staff assignments have no Mailchimp equivalent and are not migrated. Mailchimp's contact model is flat — it stores subscriber contact details and engagement data, not legal-case relationships or financial records. We preserve the primary matter ID as a merge field on each contact for traceability, but the matter data itself stays in Smokeball or must be archived separately.

Can I migrate Smokeball contact tags to Mailchimp segments?

Contact tags from Smokeball migrate as Mailchimp tags on each contact record. Tags are additive — a contact can hold multiple tags. Mailchimp segments are built by filtering on tag presence, merge field values, or engagement data. After migration, you can create segments from Smokeball-derived tags (e.g., all contacts tagged 'PI-Client') to target campaigns. Note that Mailchimp segments are dynamic or static — tags work as segment conditions but do not auto-update on existing contacts when a new tag is added.

Does the migration affect my Smokeball account during cutover?

No. FlitStack uses scoped read access via the Smokeball API — your team continues working in Smokeball during the migration. A 24–48 hour delta-pickup window captures contacts created or modified during the cutover period. No records are written back to Smokeball. After the delta pickup completes, you can close the Smokeball account or retain it for archived matter access depending on your firm's decision.

What happens to contacts without an email address in Smokeball?

Contacts without a valid email address cannot import to Mailchimp because Mailchimp requires an email address as the unique identifier for every audience member. FlitStack flags these records in a separate 'no-email' report and excludes them from the Mailchimp import. If the firm needs these contacts in Mailchimp, they must add an email address to the Smokeball contact record before the migration snapshot date. FlitStack can re-import these records in a follow-on run once email addresses are added.

How do Smokeball custom contact properties map to Mailchimp merge fields?

Smokeball custom contact properties (practice area, client type, referring attorney, etc.) migrate as Mailchimp merge fields. Each merge field must be pre-created in the Mailchimp audience before import with the correct type — TEXT for names and descriptions, NUMBER for numeric values, PHONE for telephone data. FlitStack delivers a merge-field creation spec listing all properties, recommended types, and max-lengths. Merge fields exceeding Mailchimp's character limits are truncated and flagged for review after import.

Will Mailchimp count migrated contacts toward my plan limit even if they are unsubscribed?

Yes. Mailchimp's current pricing counts all contacts in an audience — subscribed, unsubscribed, and cleaned — toward the plan limit. If your Smokeball export includes contacts who are inactive or marked as deleted, importing them as unsubscribed will still consume Mailchimp seats. FlitStack recommends auditing your Smokeball contact list before migration to exclude genuinely inactive or duplicate records, which reduces both the Mailchimp plan cost and the risk of campaign deliverability issues from mailing a list with high bounce rates.

Smokeball to Mailchimp Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Smokeball is a legal practice management platform built around matters, contacts, documents, billing, and staff workflows — the core objects are Contacts, Matters, Documents, Activities, and Staff. Mailchimp is an email marketing platform built around Audiences, Contacts, Tags, Segments, and Campaigns — its contact schema is flat, centered on subscriber email and merge-field custom properties. FlitStack AI maps Smokeball contacts directly to Mailchimp audience members, preserving firstname, lastname, email, phone, jobtitle, and any active contact tags. Smokeball's legal-specific objects — matters, documents, billing records, time entries, staff assignments — have no Mailchimp equivalent and cannot migrate; those are surfaced in the migration audit as out-of-scope. Custom contact properties in Smokeball (such as practice-area flags, referring-attorney fields, or client-type designations) map to Mailchimp merge fields, which must exist in the destination audience before import. FlitStack sequences the migration as an API-driven export from Smokeball's contacts endpoint followed by a Mailchimp bulk import, with a delta-pickup window capturing any contacts added or edited during the cutover window. A sample-import diff verifies merge field values, tag assignments, and suppression-list hygiene before the full run commits.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Smokeball

What's pushing teams away

Billing issues appear in 22+ G2 reviews, with users reporting disorganization in invoicing, problems with payment routing, and hard/soft cost misalignments between Smokeball and integrated accounting software like Xero or MYOB.
Missing features frustrate users, particularly poor search functionality across documents and the absence of auto-save, which leads to lost work and wasted time re-entering data.
Software bugs cause real operational pain—duplicate documents appearing in containers, slow performance under load, and files failing to load after upload, each cited 14+ times on review platforms.
Collaboration limitations and cumbersome document import processes are cited as missing features, making it difficult for multi-attorney firms to share and organize files efficiently.
Integration issues with third-party software, particularly after major updates, cause connectivity failures with Outlook, LawPay, and accounting tools that disrupt billing workflows.

Choosing

Mailchimp

What's pulling them in

Generous free tier with up to 500 contacts allows small teams to validate email marketing before committing to a paid plan.
Intuitive drag-and-drop email builder and 130+ templates let non-technical users produce professional campaigns without HTML or CSS knowledge.
300+ native integrations, especially Canva and Shopify, make it easy to connect existing tools without custom development work.
Detailed open-rate, click-through, and campaign analytics give small businesses actionable insights without a dedicated marketing team.
One-platform consolidation of email campaigns, automations, landing pages, and ads reduces tool sprawl for lean marketing teams.

Object mapping

How Smokeball objects map to Mailchimp

Each row shows how a Smokeball object lands in Mailchimp, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Smokeball

Contact

maps to

Mailchimp

Audience Member

1:1

Fully supported

Smokeball contacts migrate as Mailchimp audience members. The email address is the unique identifier — contacts without a valid email address cannot import to Mailchimp and are flagged separately as skipped records. FlitStack generates a dedicated report listing all contacts excluded from migration due to missing or invalid email addresses, allowing the firm to address these gaps before a follow-on import run.

Smokeball

Contact (custom properties)

maps to

Mailchimp

Merge Field

1:1

Fully supported

Smokeball custom contact properties (practice_area, client_type, referring_attorney, etc.) map to Mailchimp merge fields. Each merge field must be pre-created in the Mailchimp audience with the correct type (TEXT, NUMBER, PHONE, etc.) before import — FlitStack delivers a merge-field creation spec as part of the migration plan.

Smokeball

Contact Tags

maps to

Mailchimp

Tag

1:1

Fully supported

Smokeball contact tags (e.g., 'PI-Client', 'Newsletter-Subscriber') migrate as Mailchimp tags on the contact record. Tags are additive — a contact can hold multiple tags. Value-by-value mapping is not required since tags are free-form strings in both platforms. FlitStack preserves tag names exactly as they appear in Smokeball, applying them to the corresponding Mailchimp contact record during the batch import operation.

Smokeball

Contact Notes

maps to

Mailchimp

Contact Note / Tag annotation

1:1

Fully supported

Smokeball contact notes (free-text annotations) have no direct Mailchimp equivalent — Mailchimp contacts support a single 'note' field. FlitStack appends the most recent note as the Mailchimp contact note and flags older notes for manual review or tagging with a 'has-history-notes' tag.

Smokeball

Matter

maps to

Mailchimp

No equivalent

1:1

Fully supported

Smokeball matters (legal cases) have no Mailchimp analogue. Matter number, description, type, status, responsible attorney, open balance, and other side fields do not map. FlitStack exports a matter reference ID as a merge field (Matter_ID__c) on the contact record for traceability, but the matter data itself is out of scope.

Smokeball

Document

maps to

Mailchimp

No equivalent

1:1

Fully supported

Smokeball documents (letters, briefs, court filings stored in Matter containers) cannot migrate to Mailchimp. Mailchimp has no document management or file storage capability — it handles contact data and email campaigns only. All Smokeball documents must remain in Smokeball or be exported separately to a dedicated document management system or cloud storage platform for long-term retention.

Smokeball

Activity (email, call, meeting, task)

maps to

Mailchimp

Campaign Activity (opens, clicks)

1:1

Fully supported

Smokeball activities (billable events, emails logged against matters, calls, meetings) have no Mailchimp equivalent. Mailchimp records engagement events (opens, clicks, unsubscribes) tied to specific campaigns — these are destination-side events, not migrated from Smokeball. The communications history in Smokeball stays in Smokeball.

Smokeball

Staff

maps to

Mailchimp

No equivalent (Mailchimp User is workspace-level, not a contact)

1:1

Fully supported

Smokeball staff records (attorneys, paralegals, assistants) with email addresses can be optionally included as Mailchimp audience members if the firm wants to market to its own employees — but Smokeball staff are not matter contacts and must be explicitly included in migration scope. Staff without contact email are skipped.

Smokeball

Billing / Invoicing

maps to

Mailchimp

No equivalent

1:1

Fully supported

Smokeball invoices, time entries, trust accounting records, and payment history represent legal-financial objects with no Mailchimp equivalent. Mailchimp's billing model operates at the platform level based on audience list size, not on a per-contact basis. These financial and accounting records are explicitly excluded from migration scope and must be retained in Smokeball or exported separately for archival purposes.

Smokeball

Workflow

maps to

Mailchimp

Customer Journey

1:1

Fully supported

Smokeball workflows (automated task series tied to matter types) do not migrate. They must be rebuilt in Mailchimp's Customer Journey builder using contact tags and segment triggers as the automation foundation. FlitStack exports workflow definitions as a reference document for the Mailchimp-side rebuild.

Smokeball

Contact Address

maps to

Mailchimp

ADDRESS Merge Field group

1:1

Fully supported

Smokeball stores contact addresses as structured fields (street, city, state, zip, country). Mailchimp requires a dedicated ADDRESS merge field type with separate addr1, addr2, city, state, zip, and country components. FlitStack splits the Smokeball address into Mailchimp's address field structure during import.

Smokeball

hs_object_id (internal Smokeball ID)

maps to

Mailchimp

Source_System_ID__c merge field

1:1

Fully supported

The internal Smokeball contact GUID is preserved as a custom merge field (Source_System_ID__c) on each Mailchimp contact record. This enables traceability between the source and destination systems and supports future delta-run de-duplication by allowing FlitStack to match Mailchimp contacts back to their original Smokeball records on subsequent migration runs.

Smokeball	Mailchimp	Compatibility
Contact	Audience Member1:1	Fully supported
Contact (custom properties)	Merge Field1:1	Fully supported
Contact Tags	Tag1:1	Fully supported
Contact Notes	Contact Note / Tag annotation1:1	Fully supported
Matter	No equivalent1:1	Fully supported
Document	No equivalent1:1	Fully supported
Activity (email, call, meeting, task)	Campaign Activity (opens, clicks)1:1	Fully supported
Staff	No equivalent (Mailchimp User is workspace-level, not a contact)1:1	Fully supported
Billing / Invoicing	No equivalent1:1	Fully supported
Workflow	Customer Journey1:1	Fully supported
Contact Address	ADDRESS Merge Field group1:1	Fully supported
hs_object_id (internal Smokeball ID)	Source_System_ID__c merge field1:1	Fully supported

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Smokeball gotchas

High

Document upload may not finish before Go Live

High

Data entry must halt during final LIVE migration cutover

Medium

Duplicate contacts are not detected during import

Medium

Closed and archived matters migrate after Go Live

Medium

Lower pricing tiers strip PDF functionality and auto time

Mailchimp gotchas

High

Contact count includes unsubscribed and non-subscribed records

High

Automation workflows cannot be exported

Medium

Account suspensions trigger silently during migration

Medium

Template HTML is Mailchimp-specific and may not render in other platforms

Medium

E-commerce data requires active store connection

Smokeball gotchas		Mailchimp gotchas
Severity	Issue	Severity	Issue
High	Document upload may not finish before Go Live	High	Contact count includes unsubscribed and non-subscribed records
High	Data entry must halt during final LIVE migration cutover	High	Automation workflows cannot be exported
Medium	Duplicate contacts are not detected during import	Medium	Account suspensions trigger silently during migration
Medium	Closed and archived matters migrate after Go Live	Medium	Template HTML is Mailchimp-specific and may not render in other platforms
Medium	Lower pricing tiers strip PDF functionality and auto time	Medium	E-commerce data requires active store connection

Pair-specific challenges

Matters and legal-financial data have no Mailchimp equivalent

Smokeball's core value is the Matter object — it holds the case number, type, responsible attorney, opposing counsel, billing ledger, and document container. Mailchimp has no object that models a legal matter. FlitStack cannot migrate matter records, billing balances, time entries, or trust accounting data. Firms must decide whether to retain Smokeball access for legal records, export matter data as a PDF or spreadsheet, or archive matters in a separate system. This is not a data-loss risk — it is a scope limitation that must be explicitly acknowledged in the migration plan before migration day.
Mailchimp's ADDRESS merge field requires a 6-component split

Smokeball stores contact addresses as a single structured or free-text field depending on how the firm entered it. Mailchimp's ADDRESS merge field type requires exactly six sub-components: addr1, addr2, city, state, zip, and country. If Smokeball stores the address as free-text (e.g., '123 Main St, Suite 100, Chicago IL 60601'), FlitStack must parse it into components — and parsing is unreliable when addresses lack consistent formatting. Firms with free-text addresses should clean addresses in Smokeball before the migration snapshot date, or accept that unparseable addresses will land in addr1 and require post-migration correction in Mailchimp.
Smokeball API requires partner enrollment — export is not self-serve

The Smokeball API is not publicly accessible. Integrators must apply through the Smokeball partner program, receive a client_id and client_secret, and implement OAuth 2.0 (client credentials for server-to-server or authorization code for user-delegated). Additionally, Smokeball's API has no documented webhooks — change detection relies on polling, and rate limits are not publicly documented. FlitStack manages the partner enrollment and polling strategy as part of the migration, but the firm's Smokeball account must be in good standing and the partner enrollment process must complete before FlitStack can begin the export. This adds 5–10 business days to the project timeline that are not counted in the migration itself.
Mailchimp counts unsubscribed and cleaned contacts toward audience size

Mailchimp's pricing is audience-size based, and as of 2025 updates, the platform counts all contacts in an audience — including unsubscribed and cleaned records — toward the plan limit. If the Smokeball export includes a high proportion of inactive contacts that cannot be suppressed before import, they will consume Mailchimp audience seats. FlitStack flags contacts with invalid email addresses (hard bounces) and contacts marked as deleted in Smokeball before import, but the firm should audit its Smokeball contact list for genuinely inactive records and exclude them from the export scope to avoid post-migration billing surprises on the Mailchimp side.
Smokeball contact-to-matter N:N associations collapse to a single matter reference

Smokeball allows a single contact to be associated with multiple matters — a client can be the plaintiff in one matter and a witness in another. Mailchimp contacts have no relationship model; the contact record cannot express N:N associations. FlitStack migrates the primary (most-recently-modified) matter as a merge field on the contact and tags the contact with a 'multi-matter-client' tag if multiple matter associations exist, but the secondary matter links are not preserved. Firms that rely on contact-to-matter associations for segmentation (e.g., 'contact is a plaintiff in any active matter') must rebuild that logic using Mailchimp tags post-migration.

Migration approach

Six steps for a successful Smokeball to Mailchimp data migration

Enroll as Smokeball API partner and establish export credentials

FlitStack initiates the Smokeball partner enrollment on the firm's behalf. The firm authorizes FlitStack as an API integrator, and FlitStack receives OAuth 2.0 credentials. With credentials in hand, FlitStack connects to the Smokeball API, pulls a full contact export (including custom properties, tags, addresses, and status fields), and validates the contact count and field coverage against the firm's expected migration scope. This step typically takes 5–10 business days for partner approval and 1–2 days for the initial export.
Audit Smokeball contacts and design Mailchimp audience schema

FlitStack analyzes the Smokeball contact export to identify custom properties, tag values, address formats, and records with missing or invalid email addresses. The team produces a Mailchimp audience schema document: a list of merge fields to pre-create (with type and max-length), tags to pre-configure, and a list of contacts flagged as undeliverable or inactive for the firm's decision on exclusion. The firm creates the Mailchimp audience and merge fields before the migration import runs. Any address fields that need parsing are flagged for Smokeball-side cleanup.
Run sample migration with field-level diff

A representative slice — typically 100–500 contacts spanning different tags, custom property values, and address formats — is imported into the Mailchimp audience. FlitStack generates a field-level diff report comparing the Smokeball source values against the Mailchimp imported values. The firm reviews merge field values, tag assignments, address parsing accuracy, and unsubscribed-contact flags. Any mapping corrections are applied before the full run. This step validates the transformation logic and catches edge cases (long notes, unusual characters, missing addresses) before large-volume import.
Execute full migration with delta-pickup window

The full Smokeball contact export is imported into Mailchimp using Mailchimp's batch member-addition endpoint. FlitStack applies tags in a batch-tag operation after contacts are created. A delta-pickup window of 24–48 hours captures contacts added or edited in Smokeball during the cutover period. FlitStack generates a final audit log listing all imported contacts, skipped contacts (no email), merged duplicates, and applied tags. One-click rollback is available — contacts can be removed from the Mailchimp audience in a single operation if reconciliation reveals issues. After rollback is confirmed, the firm can request a re-run with corrected logic.
Export Smokeball workflow definitions as rebuild reference

FlitStack exports the definitions of Smokeball workflows — task series auto-assigned to matter types — as a written reference document describing each workflow's trigger conditions, task sequence, and assignee logic. This document is handed to the firm's Mailchimp admin as a rebuild guide for Customer Journeys. FlitStack does not implement Mailchimp automations, but the reference document maps Smokeball workflow concepts (matter type, task stage, responsible staff) to Mailchimp Customer Journey concepts (tag trigger, segment condition, email send). The firm rebuilds automations in Mailchimp using this reference, or engages FlitStack for a separate automation-setup engagement.

Platform deep dives

Context on both ends of the pair

Smokeball

Source

Strengths

Automatic time tracking via AutoTime captures billable activity without manual entry, directly improving firm collection rates.
Comprehensive document automation with Smokeball Toolbar in Microsoft Word enables rapid generation of standardized legal precedents and letters.
Built-in trust accounting and reporting satisfy law firm regulatory requirements out of the box.
Exceptional customer support with dedicated Client Success Managers and UK-based telephone support keeps small firms operational.
AI assistant Archie and Outlook integration reduce context switching for attorneys managing client communications.

Weaknesses

Billing issues appear frequently in reviews, with payment routing and cost allocation problems requiring manual intervention.
Search functionality across documents and matters is a known pain point, making it difficult to locate historical files efficiently.
Auto-save is not available, risking data loss if attorneys forget to save manually during document work.
Collaboration features are limited, making Smokeball less suitable for large multi-office or multi-attorney firms requiring real-time co-authoring.
Price increases have been reported by existing customers, and lower tiers strip critical features like PDF functionality and automatic time tracking.

Mailchimp

Destination

Strengths

Free plan up to 500 contacts makes it the lowest-friction entry point for new email marketers.
Drag-and-drop builder and template library produce polished emails without design or coding skills.
Strong deliverability reputation backed by years of email infrastructure expertise.
300+ native integrations cover the most common marketing stack combinations out of the box.
Consolidated platform for email, automation, landing pages, and ads reduces the number of tools small teams must manage.

Weaknesses

Contact-based pricing model charges for unsubscribed and non-subscribed records, inflating costs relative to competitors.
Five-step automation limit on Standard tier forces upgrades for basic customer journeys, a frequently cited frustration.
Template HTML is Mailchimp-specific and does not export cleanly for use in other email platforms.
Post-Intuit roadmap uncertainty means customers cannot confidently plan long-term platform investments.
Account suspension risk without clear pre-warning disrupts campaign scheduling for affected businesses.

	Smokeball Source	Mailchimp Destination
Strengths	Automatic time tracking via AutoTime captures billable activity without manual entry, directly improving firm collection rates. Comprehensive document automation with Smokeball Toolbar in Microsoft Word enables rapid generation of standardized legal precedents and letters. Built-in trust accounting and reporting satisfy law firm regulatory requirements out of the box. Exceptional customer support with dedicated Client Success Managers and UK-based telephone support keeps small firms operational. AI assistant Archie and Outlook integration reduce context switching for attorneys managing client communications.	Free plan up to 500 contacts makes it the lowest-friction entry point for new email marketers. Drag-and-drop builder and template library produce polished emails without design or coding skills. Strong deliverability reputation backed by years of email infrastructure expertise. 300+ native integrations cover the most common marketing stack combinations out of the box. Consolidated platform for email, automation, landing pages, and ads reduces the number of tools small teams must manage.
Weaknesses	Billing issues appear frequently in reviews, with payment routing and cost allocation problems requiring manual intervention. Search functionality across documents and matters is a known pain point, making it difficult to locate historical files efficiently. Auto-save is not available, risking data loss if attorneys forget to save manually during document work. Collaboration features are limited, making Smokeball less suitable for large multi-office or multi-attorney firms requiring real-time co-authoring. Price increases have been reported by existing customers, and lower tiers strip critical features like PDF functionality and automatic time tracking.	Contact-based pricing model charges for unsubscribed and non-subscribed records, inflating costs relative to competitors. Five-step automation limit on Standard tier forces upgrades for basic customer journeys, a frequently cited frustration. Template HTML is Mailchimp-specific and does not export cleanly for use in other email platforms. Post-Intuit roadmap uncertainty means customers cannot confidently plan long-term platform investments. Account suspension risk without clear pre-warning disrupts campaign scheduling for affected businesses.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from Smokeball to Mailchimp

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Smokeball

Mailchimp

How Smokeball objects map to Mailchimp

What specifically takes care here

Six steps for a successful Smokeball to Mailchimp data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Smokeball to Mailchimp migration cost

What are you migrating?

Frequently asked questions about Smokeball to Mailchimp data migrations

Can't find your answer?

Related migrations to explore

Move from Smokeball.
Land in Mailchimp, intact.

Migrate from Smokeball to Mailchimp

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Smokeball

Mailchimp

How Smokeball objects map to Mailchimp

What specifically takes care here

Six steps for a successful Smokeball to Mailchimp data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Smokeball to Mailchimp migration cost

Frequently asked questions about Smokeball to Mailchimp data migrations

Can't find your answer?

How long does a Smokeball to Mailchimp migration take?

Will my Smokeball workflows migrate to Mailchimp Customer Journeys?

What happens to my Smokeball matters and billing data in Mailchimp?

Can I migrate Smokeball contact tags to Mailchimp segments?

Does the migration affect my Smokeball account during cutover?

What happens to contacts without an email address in Smokeball?

How do Smokeball custom contact properties map to Mailchimp merge fields?

Will Mailchimp count migrated contacts toward my plan limit even if they are unsubscribed?

Related migrations to explore

Move from Smokeball. Land in Mailchimp, intact.

Move from Smokeball.
Land in Mailchimp, intact.