Aweber to Salesforce migration
Moving from AWeber to Salesforce Sales Cloud puts your subscriber data into a full CRM — AWeber's subscribers, list memberships, tags, and custom fields become Salesforce Contacts, Campaigns, and custom fields. AWeber's automations and email sequences have no equivalent in Salesforce and must be rebuilt in Flow. FlitStack AI handles the data migration with field-level validation, owner resolution by email, and a 24–48 hour delta-pickup window that keeps your AWeber account in read-only mode during cutover.
FlitStack AI migrates contacts, leads, accounts, campaigns and campaignmembers from Aweber to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 24–72 hours for under 50,000 subscribers.

What moves from Aweber to Salesforce?
AWeber is an email service provider (ESP) — its data model centers on Subscribers, Lists, Tags, Custom Fields, Campaigns, and Automations.
Read the full summary
Salesforce Sales Cloud is a CRM with Contacts, Leads, Accounts, Opportunities, Campaigns, Tasks, and custom objects. This migration maps subscriber records to Salesforce Contacts or Leads, preserves list membership as Campaign Member records, and migrates custom fields as Salesforce custom fields on the Contact object. Engagement activity (opens, clicks, last-click date) is stored as custom fields for reporting continuity. AWeber automations — email sequences, wait-step campaigns, and behavioral triggers — have no direct Salesforce equivalent and must be rebuilt in Salesforce Flow. FlitStack AI sequences the migration using AWeber's REST API (120 requests per minute) or CSV export, resolves owners by email match, and delivers a sample migration with field-level diff before committing the full run. Custom field count, tag volume, and engagement-history depth are the primary cost drivers.
Subscriber → Contact
AWeber subscribers map 1:1 to Salesforce Contacts.
How it maps
Each subscriber record — including email, name, custom fields, and tags — becomes one Contact record. Owner resolution is performed by matching the subscriber's email (or designated owner field) against Salesforce User emails. Unmatched owners are flagged before migration runs and assigned to a configurable fallback user or queue.
Subscriber (unconverted / early-stage) → Lead
Subscribers who have not purchased or engaged beyond a threshold can route to Salesforce Leads instead of Contacts.
How it maps
Your team defines the split criteria (e.g., has_purchased flag, tag presence) before migration. Leads and Contacts share the same custom field schema for consistent reporting across both objects.
Company name (custom field or name field) → Account
AWeber does not have a native Company object — company data lives in a subscriber custom field.
How it maps
FlitStack extracts all unique company values, applies your chosen deduplication rules (case-insensitive, trimmed), creates Account records in batch, and then links each Contact to its Account via AccountId lookup after the Account batch completes.
List → Campaign
Each AWeber list becomes one Salesforce Campaign record.
How it maps
The Campaign Name maps from the AWeber list name. Campaign Type is set to 'Email' by default unless you specify a different type. List-level statistics (subscriber count, creation date) are stored as Campaign custom fields for pre- and post-migration reconciliation.
List membership → CampaignMember
AWeber's subscriber-to-list association maps to Salesforce CampaignMember records.
How it maps
Each membership creates one CampaignMember linking the Contact to the Campaign. Member Status values (e.g., 'Subscribed', 'Unsubscribed') are mapped to Salesforce's MemberStatus pick-list or a custom pick-list if your status values exceed Salesforce's default options.
Tag → Custom pick-list or multi-select field on Contact
Tags with fewer than 200 unique values map to a Contact custom pick-list field (Tag__c).
How it maps
Tags exceeding 1,000 unique values require a custom multi-select text field since Salesforce pick-lists cap at 1,000 values. Overflow tags are flagged before migration so your team can decide on grouping or collapse rules.
- SubscriberContact1:1
- SubscriberLeadsplit
- Company nameAccounttransformed
- ListCampaign1:1
- List membershipCampaignMember1:1
- TagCustom pick-list or multi-select field on Contacttransformed
+ 6 more in the mapping below
How Aweber and Salesforce differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Aweber | Salesforce |
|---|---|---|
| Primary data entity | AWeber: Subscriber — flat list record with optional company name in a custom field. No account hierarchy. | Salesforce: Contact + Account — Contact requires AccountId lookup. Companies must exist as separate Account records. |
| Field naming convention | AWeber: snake_case API names (e.g., custom_field, last_click). 25 custom fields max per subscriber. | Salesforce: TitleCase API names, 40-char limit, custom fields carry __c suffix. Unlimited custom fields with schema governance. |
| Segmentation model | AWeber: Tags (unlimited per subscriber) + static Lists (N:N subscriber-to-list). | Salesforce: Campaign Members with Member Status pick-list (max 1,000 values per pick-list). Overflow tags require custom multi-select fields. |
| Automation / sequences | AWeber: Visual automation builder with wait steps, conditions, and email sends. Full logic is platform-native. | Salesforce: No email-automation equivalent. Rebuild with Flow (SObject Change triggers, Scheduled Flows, Action Links). Complexity varies widely. |
| Engagement tracking | AWeber: Tracks open_count, click_count, last_open, last_click per subscriber. Stored in API response. | Salesforce: No native open/click tracking on Contact. Engagement data must be stored as custom Number or Date fields. |
| Pricing model | AWeber: Subscriber-tier pricing (scales with list size, not users). $15–$899/month. | Salesforce: Per-user license model ($25–$550/user/month depending on edition). Total cost driven by seat count. |
| API rate limit | AWeber: 120 requests per minute per account. No daily cap. Exports are throttled. | Salesforce: 100,000 daily API calls + 1,000 calls per user license (Enterprise+). Bulk API available for large batches. |
Aweber to Salesforce field mapping
The 30 most-used fields of 30 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.
-
emailSubscriberEmailContact -
nameSubscriberFirstNameContact -
nameSubscriberLastNameContact -
phoneSubscriberPhoneContact -
citySubscriberMailingCityContact
| Aweber field | Salesforce field | Mapping | Note |
|---|---|---|---|
Subscriber.email | Contact.Email | direct | |
Subscriber.name | Contact.FirstName | direct | |
Subscriber.name | Contact.LastName | direct | |
Subscriber.phone | Contact.Phone | direct | |
Subscriber.city | Contact.MailingCity | direct | |
Subscriber.state | Contact.MailingState | direct | |
Subscriber.zip | Contact.MailingPostalCode | direct | |
Subscriber.country | Contact.MailingCountry | direct | |
Subscriber.ip_address_signup | Contact.Aweber_IP_Signup__c | custom_field_required | AWeber tracks signup IP address. Stored as a custom text field on Contact for compliance reference. |
Subscriber.ad_tracking | Contact.Aweber_Ad_Tracking__c | custom_field_required | AWeber's ad_tracking field maps to a custom text field capturing UTM or tracking source. |
Subscriber.last_click | Contact.Aweber_Last_Click__c | custom_field_required | AWeber's last_click timestamp becomes a custom Date field. Used to preserve engagement recency reporting. |
Subscriber.last_open | Contact.Aweber_Last_Open__c | custom_field_required | AWeber's last_open timestamp becomes a custom Date field. |
Subscriber.click_count | Contact.Aweber_Click_Count__c | custom_field_required | AWeber's total click count becomes a custom Number field on Contact. |
Subscriber.open_count | Contact.Aweber_Open_Count__c | custom_field_required | AWeber's total open count becomes a custom Number field on Contact. |
Subscriber.unsubscribed | Contact.HasOptedOutOfEmail | transformed | AWeber's unsubscribed boolean maps to Salesforce's HasOptedOutOfEmail field. Respects global opt-out on the Contact record. |
Subscriber.id | Contact.Aweber_Subscriber_ID__c | custom_field_required | AWeber's internal subscriber ID is preserved as a custom text field. Anchor for delta-run de-duplication. |
Subscriber.company | Contact.Account.Name | transformed | Company name from AWeber resolves to Account.Name. Account records are created from unique company values before contacts are loaded. |
Subscriber.subscribed_at | Contact.Aweber_Subscribed_At__c | custom_field_required | AWeber's subscribed_at timestamp is preserved as a custom datetime field. Salesforce CreatedDate reflects migration time, not original subscribe date. |
Subscriber.tag | Contact.Tag__c | value_mapping | AWeber tags map to a Contact custom pick-list (Tag__c) or custom multi-select field if tag values exceed 1,000 unique values. |
Subscriber.list | CampaignMember.CampaignId | transformed | List membership is not a Contact field — it becomes a CampaignMember record linking Contact to a Campaign record created from the AWeber list. |
List.name | Campaign.Name | direct | |
List.id | Campaign.Aweber_List_ID__c | custom_field_required | AWeber list ID preserved as a custom field on the Salesforce Campaign record. |
List.subscriber_count | Campaign.Aweber_Subscriber_Count__c | custom_field_required | List subscriber count stored as a custom Number field on Campaign for pre-migration reconciliation. |
CampaignMember.status | CampaignMember.MemberStatus | value_mapping | AWeber list status values (subscribed, unsubscribed, complaints) map to Salesforce MemberStatus pick-list values per campaign. |
Campaign.sent | Campaign.Aweber_Send_Count__c | custom_field_required | AWeber campaign send count stored as a custom Number field on Campaign for engagement reporting reference. |
Custom Field.(varies — up to 25) | Contact.(custom __c field) | custom_field_required | Each AWeber custom field on a subscriber becomes a Salesforce Contact custom field. Field type is preserved (text→Text, number→Number, date→Date, dropdown→Picklist). A custom field mapping plan is delivered before migration. |
Subscriber.latitude | Contact.Geolocation__c | custom_field_required | AWeber latitude/longitude coordinates map to Salesforce Geolocation custom field on Contact. |
Subscriber.longitude | Contact.Geolocation__c | custom_field_required | AWeber longitude maps to the same Salesforce Geolocation field as latitude for contact location data. |
Subscriber.source | Contact.LeadSource | direct | |
Subscriber.referred_by | Contact.Aweber_Referred_By__c | custom_field_required | AWeber's referred_by field migrates as a custom text field on Contact for referral tracking. |
What to watch for in a Aweber to Salesforce migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
AWeber's 120 req/min API rate limit constrains migration speed
AWeber enforces 120 API requests per minute per account, with no daily or monthly cap.
How we handle it
For migrations exceeding 50,000 subscribers, throttling becomes the dominant time variable. FlitStack parallelizes where possible but cannot exceed this limit. If your AWeber account is part of a multi-account integration, each account receives its own 120 req/min allocation. Large migrations may need to run in batches over multiple days, which extends the delta-pickup window and requires coordination with your AWeber account's active send schedule to avoid rate-limit collisions during peak marketing hours.
AWeber has no native Company object — Account records must be synthesized
AWeber stores company data as an optional text custom field on the Subscriber record, not as a separate entity.
How we handle it
Salesforce Contacts require an AccountId lookup, and Accounts are separate objects with their own field sets. This means FlitStack must extract every unique company value from your subscriber records, deduplicate the list, create Account records first, then resolve each Contact's AccountId before inserting the contact batch. If your company-field data is inconsistent (e.g., 'Acme Corp', 'ACME CORP', 'Acme'), deduplication rules must be agreed upon before migration. Circular references (subscribers who name each other as employer) are flagged and resolved by the most-recently-modified rule.
Tag count can exceed Salesforce pick-list capacity
AWeber allows unlimited tags per subscriber with no tag-value cap.
How we handle it
Salesforce pick-list fields cap at 1,000 active values. If your AWeber account uses more than 1,000 distinct tag values across all subscribers, the standard Tag__c pick-list migration fails. FlitStack surfaces the full tag inventory before migration and proposes one of three resolution paths: (1) collapse low-frequency tags under an 'Other' umbrella, (2) migrate the top 999 tags as a pick-list and store the rest as a custom multi-select text field, or (3) create a custom junction object for tag assignment if your use case requires granular tag-to-reporting mapping. Each path requires your team to choose the collapse or grouping logic before migration runs.
AWeber automations do not migrate — they must be rebuilt in Salesforce Flow
AWeber's automation builder stores sequences of triggers, conditions, wait steps, and email sends in a platform-specific format that has no export or Salesforce equivalent.
How we handle it
This is the most commonly underestimated scope in an AWeber-to-Salesforce migration. FlitStack exports your automation definitions as a structured reference document (trigger logic, step order, conditions, wait durations, email template references) so your Salesforce admin or FlitStack's Flow team can rebuild them in Salesforce Flow. A typical 10-step AWeber automation rebuilds as 3–6 Flow elements, but complex behavioral triggers with multiple branch conditions can require significantly more. Budget for Flow rebuild as a separate line item.
Email engagement data lives outside standard CRM objects
AWeber tracks per-subscriber open_count, click_count, last_open, and last_click as native fields.
How we handle it
Salesforce has no standard Contact fields for email engagement history — these must be stored as custom Number and Date fields on the Contact object. This means your Salesforce reporting on engagement requires custom reports or Einstein Analytics dashboards built on these custom fields. If your team relies on AWeber's engagement scoring to prioritize outreach, that logic needs to be replicated as a Salesforce Flow formula or a separate scoring tool. The custom fields are created during migration, but the reporting layer requires a separate build.
How the migration runs
Extract AWeber subscriber data via REST API
FlitStack connects to your AWeber account using OAuth2 and pulls all subscriber records via the /accounts/{id}/subscribers endpoint.
What this step covers
Each record is retrieved with its custom field values, tag list, and engagement metrics (open_count, click_count, last_open, last_click). Lists are pulled as separate collections. AWeber's 120 requests per minute rate limit is respected throughout extraction — large accounts use a paginated batch approach. Subscribers are exported in JSON format for field-level mapping before transformation.
Design Salesforce schema and custom fields
Before any data is loaded, FlitStack delivers a Salesforce schema setup plan based on your AWeber data inventory.
What this step covers
This includes: (1) custom fields on Contact for engagement metrics and source-system IDs, (2) a Tag__c pick-list or multi-select field, (3) Campaign records to be created from your AWeber lists, and (4) a company-deduplication and Account creation plan. Your Salesforce admin creates these fields (or FlitStack creates them in a sandbox first). No data loads until the schema is confirmed.
Resolve owners and company relationships
AWeber has no owner concept — Salesforce Contacts require an OwnerId.
What this step covers
FlitStack resolves each subscriber's owner by matching the subscriber's email (or a designated owner email field) against Salesforce User emails. Unmatched owners are flagged before migration and assigned to a configurable fallback user or queue. Company values are extracted, deduplicated using your chosen normalization rule (case-insensitive, trimmed), and Account records are created in batch before contacts are linked via AccountId.
Run sample migration with field-level diff
A representative slice of 100–500 subscriber records migrates first — covering multiple AWeber lists, a range of custom field types, and a sample of tagged and untagged records.
What this step covers
FlitStack generates a field-level diff comparing source (AWeber JSON) against destination (Salesforce Contact fields) so you can verify engagement metric mapping, tag-to-pick-list resolution, company-to-Account linkage, and owner resolution. You approve the sample before the full run commits. Any field mapping corrections are applied to the full migration plan.
Full migration with delta-pickup window
The full subscriber batch is loaded into Salesforce using the Bulk API for high-volume runs or the REST API for smaller accounts.
What this step covers
Lists are created as Campaign records and subscriber-to-list membership is inserted as CampaignMember records. A delta-pickup window (24–48 hours) runs after the initial batch, capturing any subscribers who were added or modified in AWeber during the migration window. AWeber remains in read-only access during this period — no sends are affected. FlitStack provides an audit log of every record inserted, updated, or skipped, plus a de-duplication report if any subscriber IDs conflict.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
AWeber-to-Salesforce migration pricing scales primarily with subscriber count, custom field volume, and tag complexity. Tag-to-pick-list flattening adds schema-planning time when your tag count approaches Salesforce's 1,000-value pick-list ceiling and requires coordination with your team to define collapse rules. Engagement-history migration (open_count, click_count, last_open, last_click) requires four custom fields per subscriber and is priced accordingly based on per-subscriber record creation overhead. Automations export is a documentation task at low cost — FlitStack produces a structured reference document of trigger logic, step order, and conditions. Salesforce Flow rebuild is a separate engagement quoted by your Salesforce admin or FlitStack's Flow services team. Delta-pickup window duration and any required re-verification steps are included in the standard scope for migrations exceeding 50,000 subscribers. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Aweber to Salesforce →Why teams move from Aweber to Salesforce
- AWeber caps out as a contact list manager — it has no opportunity tracking, account hierarchy, or deal pipeline. Teams that need to manage customer accounts, forecast revenue, and assign territories need a CRM. Salesforce Sales Cloud provides those capabilities natively without requiring a second platform.
- When subscriber count grows past the SMB tier, AWeber's per-subscriber pricing becomes comparable to Salesforce per-seat pricing. At that scale, the upgrade to a full CRM with reporting, forecasting, and territory management delivers more value than continued investment in email-only tooling.
- AWeber's automation builder handles basic nurture sequences but lacks the conditional depth, multi-object triggers, and approval routing that Salesforce Flow provides. Teams with complex go-to-market motions, multi-step approval chains, and cross-object field updates need Flow's trigger model to automate business processes at scale.
- M&A activity frequently consolidates acquired companies onto Salesforce as the parent org's CRM of record. Subscriber data from the acquired company's AWeber account migrates to Salesforce Contacts under the parent org's schema, with marketing operations rebuilt in the parent org's tool of choice or aligned with its existing Salesforce Flow infrastructure.
- AWeber offers no native reporting on contact lifecycle or revenue attribution. Salesforce's reporting suite, Einstein Analytics, and native CRM objects give sales and marketing leadership a unified view of pipeline health, campaign attribution, and deal progression without exporting to a separate BI tool or maintaining parallel reporting systems.
Questions, answered
Aweber to Salesforce migration questions
How long does an AWeber to Salesforce Sales Cloud migration take?
Most AWeber-to-Salesforce migrations complete in 24–48 hours for under 25,000 subscribers. AWeber's 120 requests per minute API rate limit is the dominant constraint for large exports — accounts over 100,000 subscribers may need multi-day extraction with a longer delta-pickup window. FlitStack sequences the migration in batches and runs the delta pickup in parallel with your AWeber account remaining in read-only mode. Salesforce schema setup (custom fields, pick-lists) runs before data extraction and does not add to the migration timeline.
Will my AWeber automations and email sequences migrate to Salesforce?
No. AWeber automations — sequences with triggers, conditions, wait steps, and email sends — have no Salesforce equivalent and do not migrate. They must be rebuilt in Salesforce Flow. FlitStack exports your automation definitions as a structured reference document that your Salesforce admin or FlitStack's Flow services team can use to rebuild each sequence. A typical 10-step AWeber automation rebuilds as 3–6 Flow elements, but complex behavioral branches require more. Budget for Flow rebuild as a separate engagement.
What happens to AWeber's tags in Salesforce?
Tags migrate to a custom pick-list field (Tag__c) on the Salesforce Contact object. If your AWeber account uses more than 1,000 distinct tag values, Salesforce's pick-list ceiling is exceeded — in that case, the top 999 tags become a pick-list and remaining tags are stored in a custom multi-select text field or a custom junction object. FlitStack surfaces the full tag inventory before migration so your team can choose the grouping or collapse rule before data loads.
Can I migrate AWeber custom fields to Salesforce custom fields?
Yes. AWeber supports up to 25 custom fields per subscriber — each one maps to a Salesforce Contact custom field with the __c suffix. Field type is preserved where possible (text to Text, number to Number, date to Date, dropdown to Picklist). FlitStack delivers a custom field mapping plan before migration so your Salesforce admin can create the corresponding fields. Engagement metrics (open_count, click_count, last_open, last_click) are included as custom fields since Salesforce has no native equivalent for email engagement data on Contact records.
How does AWeber list membership appear in Salesforce?
Each AWeber list becomes a Salesforce Campaign record. Subscriber membership in that list appears as CampaignMember records linking each Contact to the Campaign. Campaign Member Status values (Subscribed, Unsubscribed) map from AWeber's list-level status field. Campaign records also carry custom fields for the original AWeber list ID and subscriber count for pre-migration reconciliation. If you use multiple AWeber lists per subscriber, each list generates a separate CampaignMember record on the same Contact.
Does the migration affect my AWeber account during the cutover?
No. FlitStack uses read-only API access on your AWeber account throughout the migration process — your team continues sending campaigns and managing subscribers normally. A delta-pickup window (24–48 hours after the initial batch load) captures any new subscribers or status changes that occurred during the migration window. No AWeber data is modified, deleted, or restricted during the process. Your active sends and subscriber management remain fully operational without interruption.
What happens to my AWeber email engagement data (open count, click count)?
AWeber's per-subscriber open_count, click_count, last_open, and last_click metrics are preserved as custom Number and Date fields on each Salesforce Contact record (e.g., Aweber_Open_Count__c, Aweber_Last_Click__c). Salesforce has no native CRM fields for email engagement data, so these custom fields are created as part of the migration schema setup. Custom reports or Einstein Analytics dashboards built on these fields are needed to replicate AWeber-style engagement reporting — the data migrates, but the reporting layer requires a separate configuration step.
What does FlitStack not migrate from AWeber, and how do I rebuild those pieces?
FlitStack migrates subscriber data, custom fields, tags, list membership, and engagement metrics. Not migrated: AWeber automations and sequences (rebuild in Salesforce Flow), email templates (exported as HTML files for re-upload to Salesforce Files or your email tool), landing pages and sign-up forms (rebuild using Salesforce Web-to-Lead or a third-party form tool), and integrations or third-party connections (must be re-established in Salesforce). FlitStack delivers documentation packages for each of these areas — automations as a rebuild reference, templates as exported files, and integrations as a connection audit checklist.
Related migrations
Salesforce implementation
Set up Salesforce and migrate into it as one engagement.
See the service → Dynamics 365 to SalesforceMapping · history · rollbackSnovio to SalesforceMapping · history · rollbackClio to SalesforceMapping · history · rollbackLeadSimple to SalesforceMapping · history · rollbackServiceTitan to SalesforceMapping · history · rollbackInsightly CRM to SalesforceMapping · history · rollback Aweber to Odoo CRMMapping · history · rollbackAweber to HubSpotMapping · history · rollbackAweber to Zoho CRMMapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
- Sandboxes — Staging Environments for Customizing and Testing
- Case Comment STRING_TOO_LONG — Salesforce Stack Exchange
- Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV
- Salesforce Duplicate Management — Salesforce Stack Exchange
Get a quote
Moving from Aweber to Salesforce?
Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.
Get a quote