Migrate from Aweber to Twenty CRM

AWeber API rate limit (120 req/min) governs migration throughput

AWeber's API enforces a hard ceiling of 120 requests per minute per account. During a migration, FlitStack AI throttles all export calls to respect this limit, which extends the migration clock for large subscriber bases. For example, exporting a 50,000-subscriber account at 120 req/min with page sizes of 100 records per call takes approximately 7 hours just for the raw export. We use response caching and conditional requests to minimize redundant calls, but the AWeber-side rate limit is the primary throughput bottleneck — not Twenty's API, which allows 200 calls per minute.

AWeber automations and sequences cannot be migrated to Twenty workflow engine

AWeber Automations (time-triggered email sequences, tag-on-action triggers, broadcast triggers) are stored as a workflow definition inside AWeber's engine and have no structural equivalent in Twenty CRM. Twenty's workflow builder operates on record-change triggers (create, field-update, assignment) and does not support time-based email sequences or ESP-style drip campaigns natively. FlitStack AI exports each AWeber automation as a JSON reference document listing the trigger, each step's delay, and the action. Your Twenty admin uses this document to rebuild equivalent flows — but the automation logic must be redesigned, not ported. This is a significant post-migration effort that should be scoped before migration day.

AWeber campaign performance data has no native landing in Twenty

AWeber tracks per-subscriber open rates, click rates, and unsubscribes tied to individual campaigns. Twenty CRM has no native campaign-tracking object and no email send history on People records by default. FlitStack AI surfaces this data as structured Note text on each People record — but this is a historical record, not live tracking. If your team relies on AWeber's campaign analytics for reporting, those reports must be rebuilt in a BI tool or kept accessible in AWeber's reporting export after migration. Continuing to log email activity in Twenty requires a custom integration or a separate email service provider.

Per-list custom fields require schema provisioning in Twenty before import

AWeber allows different custom fields per list — List A might have a 'Lead_Source' text field while List B has 'Purchase_Intent' dropdown. Twenty CRM custom fields on the People object are workspace-wide, not per-record-type. Before import, FlitStack AI audits every custom field defined across all AWeber lists, de-duplicates by name and type, and provisions matching custom fields in Twenty's metadata API. Fields with the same name but different types across lists (e.g., 'Score' as text in one list and number in another) require business-rule decisions before provisioning — we surface these conflicts in the pre-migration audit.

Tag cardinality explosion can exceed Twenty's multi-select field option limits

AWeber tags are freeform strings with no cardinality constraint — a subscriber can have 50 tags. Twenty CRM's multi-select fields store options as a defined pick-list. If your AWeber account uses thousands of unique tag values (common in high-volume or long-running accounts), a single multi-select field in Twenty cannot accommodate all of them. FlitStack AI caps tag migration by frequency threshold: tags appearing on fewer than 50 records are consolidated into a JSON text blob on the People record rather than added as individual multi-select options. Tags meeting the frequency threshold are provisioned as multi-select options.