Migrate from Adobe Campaign to Freshsales

Adobe Campaign's primary profile table maps to Freshsales Contact. Standard fields (email, first name, last name, format preference) migrate directly. Custom fields added via schema extension land as Freshsales Custom Fields on Contact. We detect extended schema fields during pre-migration audit and pre-create equivalent custom fields in Freshsales before import begins.

Adobe Campaign BroadLog records track every message sent across channels. Send timestamp, campaign label, delivery status, and error reason migrate as Freshsales Activity records (email type) linked to the target Contact. We preserve the campaign attribution label in the Activity subject for reporting continuity. v8 FFDA records require cross-referencing both local and cloud database tables before merging into a single import set.

Open, click, and bounce events from Adobe Campaign tracking logs migrate as Freshsales Activity records with subtype indicating event type (email_opened, link_clicked, bounce). Click-through URLs preserve in a custom activity field for audit. Aggregate open/click rates recalculate in Freshsales reports post-migration.

Adobe Campaign campaign metadata (labels, dates, type, status) can be stored as a Freshsales Custom Object for reference, or linked to Deal records if the customer uses Deals to track campaign-attributed revenue. We recommend the Custom Object approach for historical campaign catalog and the Deal approach for revenue attribution. Customer chooses during scoping.

Adobe Campaign opt-in subscription records link Recipients to Services. Subscription status and subscription date map to Freshsales Contact Lifecycle Stage (Lead, Marketing Qualified, Sales Qualified Lead, Opportunity, Customer). Double-opt-in confirmation flags from Adobe Campaign map to Freshsales email consent fields. Unsubscribed records in Adobe Campaign land as unsubscribed in Freshsales.

Adobe Campaign Standard and v8 Programs are hierarchical containers for Campaigns. Folder structure and program labels migrate as Freshsales folder organization on Contacts and Accounts. Program-specific permissions do not carry over and must be reconfigured as Freshsales team or role assignments post-migration.

Adobe Campaign custom tables created via nms:ext: namespace or FDA-linked external schemas require custom extraction logic. We inspect the schema XML to derive the underlying SQL table structure, then map to Freshsales Custom Objects with equivalent field types. Lookup relationships between custom schemas map to Freshsales Custom Object Lookup Fields.

Adobe Campaign technical operators (including IMS-migrated server-to-server accounts) map to Freshsales Users resolved by email match. Any Adobe Campaign operator without a matching Freshsales User is held in a reconciliation queue for the customer admin to provision before record import resumes.