Migrate from Aweber to Salesforce Sales Cloud

AWeber subscribers map 1:1 to Salesforce Contacts. 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.

Subscribers who have not purchased or engaged beyond a threshold can route to Salesforce Leads instead of Contacts. 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.

AWeber does not have a native Company object — company data lives in a subscriber custom field. 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.

Each AWeber list becomes one Salesforce Campaign record. 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.

AWeber's subscriber-to-list association maps to Salesforce CampaignMember records. 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.

Tags with fewer than 200 unique values map to a Contact custom pick-list field (Tag__c). 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.

AWeber's per-subscriber custom fields (up to 25) map to Salesforce Contact custom fields with the __c suffix. Field type is preserved where possible: text to Text, number to Number, date to Date, dropdown to Picklist. A custom field mapping plan detailing each field pair is delivered before migration runs for Salesforce admin approval.

AWeber tracks engagement per subscriber but Salesforce has no native equivalent for email engagement data on Contact records. These four metrics are stored as custom Number or Date fields on Contact (e.g., Aweber_Last_Click__c, Aweber_Click_Count__c) for reporting continuity. Custom field creation and population are included in the migration scope.

AWeber's automation sequences, wait-step logic, and behavioral triggers have no Salesforce equivalent. FlitStack exports the full automation structure (trigger conditions, wait durations, email send actions) as a structured reference document. Rebuilding in Salesforce Flow is a separate scope quoted by your Salesforce admin or FlitStack's Flow services team.

AWeber HTML email templates are exported as files and re-uploaded to Salesforce Files. Salesforce does not have a native email template library for Contacts — templates are typically managed in Salesforce Content, Files, or your email integration tool (e.g., Salesforce Inbox, Gmail integration).

AWeber sign-up forms are platform-native and cannot be exported. FlitStack documents the form field mapping, conditional logic, and integration settings as a rebuild reference for Salesforce Web-to-Lead or a third-party form tool (FormAssembly, Typeform). Landing pages and form host pages require a separate rebuild in your chosen platform.

AWeber's internal subscriber ID is preserved as a custom text field (Aweber_Subscriber_ID__c) on the Contact record. This serves as the source-system anchor for delta-run de-duplication and for linking back to AWeber data during the delta-pickup window to ensure no subscribers are missed or duplicated.