Migrate from Textedly to HubSpot

Phone is primary in Textedly; email is primary in HubSpot — deduplication logic must account for directionality

Textedly requires a mobile phone number for every subscriber but treats email as optional. HubSpot inverts this — email is the primary contact identifier and phone is secondary. When the migration runs, HubSpot's duplicate-detection rules use email as the match key by default, which means contacts with no email address in Textedly will not be assessed for duplicates and will land as new records even if a matching phone number exists. FlitStack AI resolves this by running phone-based deduplication as a pre-validation step: we group Textedly contacts by normalized phone number before writing to HubSpot, then write email-matched contacts normally and flag phone-only records for manual review or explicit HubSpot duplicate rules configuration before the full load commits.

Keyword opt-in records must be preserved as compliance evidence but have no native HubSpot equivalent

TCPA compliance requires knowing the exact keyword a subscriber used to opt into SMS messaging. Textedly stores this as a keyword field on the contact record. HubSpot has no native field for SMS keyword provenance — its contact creation tracking only records HubSpot-native paths like form submissions or list imports. If a subscriber's keyword history is not explicitly preserved in a custom field, the compliance record is broken when the data moves. FlitStack AI creates a Source_Keyword__c custom field on the Contact object and maps the exact keyword value from Textedly for every migrated subscriber. Opt-in source (web form, API, keyword) is stored separately in Opt_In_Source__c. Both fields are included in the pre-migration compliance audit.

Auto-responders and keyword-triggered sequences are not automation — they must be rebuilt from exported definitions

Textedly's auto-responders (keyword-triggered SMS replies, drip sequences, and time-based follow-ups) use a rule engine that has no structural equivalent in HubSpot. HubSpot workflows can replicate the same logic — triggering on contact property changes, enrolling on keyword match, and sending SMS via a connected integration — but the automation itself does not migrate. We export the complete auto-responder configuration from Textedly (trigger keywords, response messages, delay rules, and sequence order) as a structured reference document. Your HubSpot admin uses this to recreate the logic as workflows. Until rebuilt, subscribers who would have triggered a Textedly auto-responder will receive no automated response from HubSpot.

Textedly's tag model is flat; HubSpot's list membership requires active recreation post-migration

Textedly tags are a flat, multi-value property stored on each contact (e.g., 'VIP, Retail, Holiday2025'). HubSpot's equivalent data model is list membership — contacts belong to static or active lists, not a comma-separated text block. Migrating tags as a custom property (Tags__c) preserves the raw data but does not make those segments immediately actionable in HubSpot workflows or reports. FlitStack AI creates HubSpot static lists based on the top N tags (by frequency) as part of the migration deliverable, but ongoing tag-based segmentation requires rebuilding list logic or setting up HubSpot's active list criteria to re-evaluate tag values as contacts are updated.

Textedly subscriber exports do not include MMS media files — image attachments require separate extraction

If your Textedly account contains MMS messages with image attachments, those images are stored in Textedly's file storage and are not included in the standard subscriber export. HubSpot's file management and CMS capabilities require re-uploading these assets. FlitStack AI identifies any MMS records in the export and flags the associated image URLs for separate download and re-upload to HubSpot Files or the connected CMS. This step adds to the migration timeline for accounts with high MMS volume.