Migrate from Aweber to Nutshell

AWeber subscribers map 1:1 to Nutshell People. Each subscriber's email address, name, phone, and address fields map to Nutshell's standard Person fields. Custom field values carried over as Nutshell custom fields. Source system ID stored in AWeber_Source_ID__c for delta-run tracking.

AWeber tags are flat labels with no hierarchy. Nutshell has no native tagging — we concatenate all subscriber tags into a pipe-delimited string stored in a custom text field. Saved searches in Nutshell can then filter on tag substrings. Teams needing granular tagging rebuild using Nutshell custom fields.

AWeber supports up to 25 custom fields per list. Nutshell allows custom fields on Person, Company, and Lead objects. We create a matching Nutshell custom field for each AWeber custom field, preserving field type (text, number, date, checkbox, dropdown). Dropdown-type fields require value-by-value mapping.

AWeber lists have no CRM equivalent in Nutshell. List membership is preserved as a custom text field (List_Name__c). Subscribers in multiple lists store all list names pipe-delimited. Nutshell's CRM model does not use list-scoped fields. This means list-based segmentation used in AWeber must be rebuilt in Nutshell using saved searches or custom field filters based on tag and list name values.

AWeber campaigns (broadcast sends, follow-up sequences) have no equivalent in Nutshell's data model. Campaign names and send timestamps are not carried into Nutshell records. We export campaign definitions as JSON for reference when rebuilding email sequences in Nutshell. This JSON documents each campaign's schedule, audience criteria, and content so your team can reconstruct the communication flow manually.

Per-subscriber open/click/bounce history attached to campaigns does not migrate. Nutshell tracks activities (calls, emails, meetings) but not email marketing engagement. Engagement data can be referenced via AWeber_Source_ID__c if AWeber is retained for sending. For teams sunsetting AWeber, engagement history remains accessible in exported AWeber reports independently.

AWeber's Campaigns and Workflows are automation constructs with no data-layer equivalent. The trigger conditions, wait periods, and action steps export as a JSON definition file for use in rebuilding Nutshell Workflows and email sequences manually. This export captures the full automation logic including conditional branches, time delays, and target audience filters so nothing is lost in translation.

AWeber email templates (up to 3 migrated by AWeber's own team) cannot be imported into Nutshell. Nutshell's email marketing uses its own template system. Templates are exported as HTML reference files. The exported HTML preserves styling, images, and layout so designers can rebuild templates in Nutshell's editor without starting from scratch. Note that AWeber's template migration service applies only to migrations moving TO AWeber, not FROM it.

AWeber landing pages and sign-up forms are web assets with no Nutshell equivalent. They must be rebuilt using Nutshell's landing page tools or a third-party form builder. Form field definitions export as a JSON reference. The JSON schema includes field names, types, required flags, and validation rules so matching forms can be constructed in Nutshell's form editor or an external tool.

AWeber accounts (the top-level subscriber organization) map to Nutshell Companies when subscriber records include company name data. Company name and domain extract from subscriber custom fields or the account-level name if available. For subscribers without company affiliation, Nutshell Person records are created standalone. Account-level metadata such as billing address and subscription tier does not have a dedicated field in Nutshell and is not migrated.

AWeber subscriber statuses (active, unsubscribed, bounced, complaint) migrate as a custom pick-list field Status_in_AWeber__c. Unsubscribe timestamp migrates as a custom datetime field if present. Bounce records flag as a custom checkbox. These status fields allow Nutshell users to filter and prioritize outreach based on a contact's prior subscription state without needing to reference AWeber data directly.

AWeber captures subscriber IP at opt-in and geolocation data is available per subscriber. Nutshell Person records do not have a native IP or geolocation field. These values can be stored as custom text fields if business justification exists, such as compliance requirements or regional targeting analysis. Without a specific use case, these fields are omitted to keep the Person record clean.