Klaviyo Migration Service

Service Scope

Klaviyo Migration Service is a fixed-scope service for one business, one source email marketing platform or CRM, one destination Klaviyo account, and up to 25,000 email profiles.

The service reviews the source data, selects the appropriate migration method, transfers the approved profiles and properties, preserves available consent and suppression information, creates a practical list structure, recreates up to five foundational migration segments, and validates the resulting Klaviyo data.

This service migrates the email audience foundation. Email templates, forms, automations, campaigns, domain authentication, e-commerce integrations, and additional messaging channels require separate services.

Review the Source and Destination Accounts

We review both platforms to determine what information is available and how it should be represented inside Klaviyo.

The review may cover:

• Source platform and account status
• Available native Klaviyo integration
• Existing audiences, lists, groups, tags, and segments
• Active email subscribers
• Unsubscribed contacts
• Bounced or cleaned addresses
• Suppression records
• Profile and custom fields
• Available engagement history
• Existing signup sources
• Current automation entry points
• Active website forms
• E-commerce or CRM connections
• Existing sender domain
• Data export limitations

The review identifies the approved migration path and any information that cannot be transferred directly.

Prepare a Migration Plan

We prepare one practical migration plan before importing data.

The plan identifies:

• The source platform
• The destination Klaviyo account
• The migration method
• The files or integration required
• The profile quantities
• The fields to be mapped
• The destination lists
• The consent and suppression treatment
• Available engagement information
• The cutover sequence
• Known source-platform limitations
• Client decisions required before import

The client must approve the migration structure before data is transferred.

Use a Native Integration When Available

When Klaviyo provides a supported native connection to the source email platform, we may use that integration to synchronize the information it supports.

Native migration integrations may be available for platforms such as:

• Mailchimp
• Constant Contact
• Campaign Monitor
• Mad Mimi
• Other platforms available in Klaviyo’s current integration directory

Depending on the source platform, the native integration may transfer:

• Contacts
• Lists
• Unsubscribes
• Received-email activity
• Open activity
• Click activity
• Other supported historical information

Each integration transfers a different set of information and operates on its own synchronization schedule.

A native integration does not guarantee that every source property, audience structure, campaign, report, automation, template, or historical event will appear in Klaviyo.

Use a File-Based Migration When Required

If no supported native integration is available, we complete the migration using client-authorized exports and Klaviyo-compatible files.

The service includes preparation and processing of up to five migration files.

Files may contain:

• Active email subscribers
• Customer or lead profiles
• Profile properties
• Source-list membership
• Engagement classifications
• Unsubscribed contacts
• Bounced or cleaned addresses
• Other approved email suppression records

The client must provide access to export the source data or provide complete final exports.

Requests to a former platform’s support team, delayed vendor exports, account restrictions, or inaccessible data may extend the migration timeline.

Migrate Up to 25,000 Email Profiles

We transfer up to 25,000 approved email profiles into the destination Klaviyo account.

Profiles may include:

• Active email subscribers
• Customers without marketing consent
• Leads without confirmed consent
• Unsubscribed contacts
• Suppressed contacts
• Bounced or invalid addresses
• Other client-approved profile statuses

Importing a profile does not automatically mean that the person is eligible to receive marketing email.

Klaviyo may merge records sharing the same supported identifier. Invalid, incomplete, malformed, duplicated, restricted, or unsupported records may be skipped, merged, or imported without every original value.

Map Profile Properties

We map up to 20 approved source fields to Klaviyo profile properties.

These fields may include:

• Email address
• First name
• Last name
• Phone number
• Company
• Customer type
• Lead source
• Location
• Signup date
• Original signup source
• Customer status
• Product interest
• Loyalty status
• Last engagement date
• Other approved custom information

Source fields must be compatible with the destination Klaviyo property type.

Fields with conflicting formats, inconsistent naming, mixed data types, or undocumented values may require client clarification before they can be mapped.

Complex data normalization, enrichment, manual research, or database reconstruction is not included.

Create the Destination List Structure

We create or configure up to five Klaviyo lists for the approved migration structure.

The final lists may represent:

• Primary email subscribers
• A specific source audience
• Customer or lead categories
• Temporary migration classifications
• Engagement groups that cannot be transferred as native events
• Other approved static membership

Klaviyo lists are static collections of profiles. Dynamic source segments are not automatically recreated as Klaviyo lists or segments unless their rules and required data are available.

The migration avoids unnecessary duplicate lists where a cleaner profile-property or segment structure is appropriate.

Preserve Email Consent

The client must identify which contacts have documented permission to receive email marketing.

Where supported by the available source data, we preserve or assign the appropriate email marketing status.

The migration distinguishes between:

• Profiles with affirmative email consent
• Profiles without documented consent
• Unsubscribed profiles
• Suppressed profiles
• Bounced or invalid email addresses
• Customers who exist only because of a transaction or account record

KizilCo does not independently determine whether the source platform’s consent history satisfies a particular law, regulation, contract, or industry requirement.

Import Unsubscribes and Suppressions

We transfer the available historic email unsubscribes, bounces, cleaned addresses, and other approved suppression records.

When a native integration does not transfer every relevant status, an approved suppression file may be uploaded directly into Klaviyo.

Preserving these records is essential because previously opted-out or invalid contacts should not become marketable merely because the business changed email platforms.

Suppression records are reviewed separately from subscribed profiles because consent and suppression are distinct profile states inside Klaviyo.

Permanent profile deletion is not included.

Transfer Available Engagement Information

The amount and form of historical engagement data depends on the source platform.

When a native integration supports it, Klaviyo may receive historical events such as:

• Received email
• Opened email
• Clicked email
• Other supported campaign engagement

When native event history cannot be transferred, available source information may instead be mapped as profile properties or temporary migration groups.

Examples may include:

• Last opened date
• Last clicked date
• Engagement category
• Recent subscriber status
• Source-platform activity classification

Manually imported dates or classifications do not become native Klaviyo campaign events unless Klaviyo’s supported integration creates those events.

Historical reporting, attribution, revenue, and complete campaign analytics generally cannot be recreated through a standard contact import.

Build Foundational Migration Segments

We create up to five practical Klaviyo segments using the information available after migration.

Segments may include:

• Marketable email subscribers
• Recently engaged subscribers
• Recently added subscribers
• Customers with imported purchase properties
• Inactive or low-engagement profiles
• Profiles requiring further review
• Source-platform audience groups

The final segment definitions depend on the transferred fields and available historical events.

Advanced lifecycle, predictive, behavioral, product-interest, and personalization segmentation requires the separate Klaviyo Advanced Segmentation & Personalization Setup service.

Protect Existing Welcome Flows

Before importing profiles, we review visible list-triggered flows that could unintentionally send messages to migrated contacts.

Where necessary and authorized, an affected flow may be placed in draft or manual status during the import.

The service does not create, rebuild, edit, activate, or test automation content.

The client remains responsible for approving when any existing flow should return to live status.

Review List Quality Before Cutover

We perform a practical migration-level review of the available audience information before the first Klaviyo send.

The review may identify:

• Invalid formatting
• Missing identifiers
• Duplicate email addresses
• Old or inactive contacts
• Unclear consent statuses
• Missing suppression data
• Profiles without recent engagement
• Obvious high-risk source groups

Basic file formatting needed for the approved import is included.

Third-party email verification, deep database cleanup, manual duplicate resolution, engagement campaigns, sunset flows, and suppression strategy implementation require separate services.

Complete the Main Migration

After the structure and files are approved, we complete the primary data transfer into Klaviyo.

The migration may use:

• One supported native integration
• Up to five approved import files
• A combination of a native integration and supplemental suppression files

We review the available import or synchronization results and identify visible errors, skipped records, duplicate handling, and unresolved source-platform restrictions.

Complete a Final Synchronization

One final synchronization or correction import is included.

This may be used to:

• Capture subscribers added during the migration period
• Add recently created suppression records
• Correct an in-scope field-mapping issue
• Reprocess an approved formatting correction
• Validate the final source and destination counts

The source platform must remain accessible until final validation is complete.

Repeated incremental migrations, ongoing synchronization, or continued parallel operation are not included.

Prepare the Cutover

We prepare a controlled cutover checklist identifying what should happen before the former platform is discontinued.

The checklist may cover:

• Confirming final profile counts
• Confirming suppression counts
• Updating website forms
• Connecting checkout subscribers
• Recreating required automations
• Recreating required email templates
• Authenticating the sending domain
• Connecting the e-commerce platform
• Preparing engaged sending segments
• Planning domain or infrastructure warming
• Monitoring the former platform for new subscribers
• Preserving reports and campaign exports
• Confirming billing and cancellation dates

The checklist identifies required next steps but does not implement services outside the purchased migration scope.

Do Not Immediately Cancel the Source Platform

The client should keep the former platform active until:

• Required data has been exported
• The final synchronization is complete
• Website forms point to Klaviyo
• Checkout subscribers reach Klaviyo
• Required automations have been rebuilt
• Templates needed for launch are available
• The sending domain is authenticated
• The first Klaviyo sends are ready
• New subscribers are no longer appearing only in the former platform

KizilCo does not cancel the former platform or accept responsibility for its continuing subscription charges.

Deliverability and Warming Considerations

Moving to a new email service provider can require a controlled sending ramp or warming process.

Before sending at normal volume, the client may need:

• A branded sending domain
• DMARC alignment
• Engaged audience segments
• Suppression of invalid or unengaged profiles
• A gradual sending schedule
• Monitoring of bounces, complaints, and engagement

This service provides migration-level recommendations only.

Sending-domain configuration, deliverability repair, list-cleaning implementation, warming execution, and campaign scheduling are not included.

Migration Validation

After the final transfer, we review the destination Klaviyo account for:

• Imported profile count
• Primary email list count
• Available consent statuses
• Suppression count
• Field mapping
• Custom property availability
• Source-list representation
• Available engagement information
• Foundational segments
• Visible import errors
• Native integration status
• Remaining cutover requirements

The counts between platforms may not match exactly because the platforms may count profiles, contacts, duplicates, invalid addresses, unsubscribes, suppressions, and archived records differently.

Implementation Summary

The client receives a concise implementation summary identifying:

• The source platform
• The destination Klaviyo account
• The migration method used
• The profiles submitted
• The visible import results
• The properties mapped
• The lists created
• The consent and suppression treatment
• The available engagement information transferred
• The segments created
• The final synchronization status
• Unresolved records or limitations
• Required cutover actions
• Recommended next steps

The source account, Klaviyo account, contact data, files, lists, and associated business assets remain owned and controlled by the client.

Client Requirements

Before migration begins, the client must provide:

• Administrator or export access to the source platform
• Administrator access to the Klaviyo account
• One complete source-data set
• Access to all subscriber lists
• Access to unsubscribed and bounced contacts
• Documented consent status
• Explanations of custom fields
• Explanations of source contact statuses
• The required destination lists
• Approval of the field-mapping plan
• Approval of the suppression treatment
• Details of active website forms
• Details of active automations
• Details of connected e-commerce or CRM platforms
• Timely review and approval of the migration results

Delivery and Revisions

Standard delivery is 7–10 business days after all required access, exports, decisions, and approvals are received.

Source-platform export delays, native integration schedules, account restrictions, large files, unsupported data, vendor support requests, and final synchronization timing may extend completion.

One consolidated correction round is included when submitted within seven days of delivery and remains within the original quantities and approved migration structure.

A replacement source export, additional platform, materially different mapping plan, or additional migration phase is treated as separate work.

Important Scope Boundaries

The following are not included:

• Klaviyo or source-platform subscription fees
• More than one source platform or CRM
• More than one Klaviyo account
• More than 25,000 email profiles
• More than five migration files
• More than 20 profile properties
• More than five destination lists
• More than five foundational segments
• SMS, MMS, WhatsApp, or push-consent migration
• Phone-number porting
• Multiple brands or business units
• Custom API, webhook, SFTP, or data-warehouse development
• Database enrichment or manual research
• Third-party email verification
• Major database cleanup or reconstruction
• Manual duplicate resolution
• E-commerce platform integration
• CRM integration
• Signup form creation or website installation
• Email template migration or recreation
• Campaign migration or launch
• Automation flow recreation or activation
• Sending-domain authentication
• Dedicated click tracking
• Sender-reputation repair
• Domain or IP warming execution
• Legal or regulatory compliance review
• Source-platform cancellation
• Ongoing parallel synchronization
• Guaranteed transfer of every field, status, event, or record
• Guaranteed matching profile counts between platforms
• Guaranteed inbox placement, engagement, conversions, or revenue