Migrate from Adobe Campaign to HighLevel

Adobe Campaign's nms:recipient schema maps to GoHighLevel Contact. Standard fields (email, first name, last name, format preference, address) migrate directly. Custom fields added via schema extension land as GoHighLevel custom fields with equivalent data types. We inspect the schema XML to derive SQL table column types before mapping. Recipient status (enabled, blocked, quarantine) maps to GoHighLevel contact status and an opt-out flag.

Adobe Campaign campaign metadata (labels, dates, type, status) migrates as GoHighLevel Opportunities if the customer uses a sales pipeline model, or as a named tag group for organisation if the model is purely marketing. Campaign type codes map to GoHighLevel pipeline stage names that we configure during scoping. Folders and program hierarchy do not migrate structurally; they become naming conventions or tags on the migrated records.

Adobe Campaign BroadLog records (sent, open, click, bounce, error by channel) are aggregated and migrated as GoHighLevel Task records with custom fields capturing send timestamp, channel, and outcome status. Aggregate open and click rates recalculate in GoHighLevel from the activity records; we preserve the original timestamps for historical continuity. Delivery-level logs map to a GoHighLevel custom object linked to the Contact if the volume justifies a separate table.

Tracking logs (open, click, URL click-through) migrate as custom fields on the GoHighLevel Contact: last_opened_at, last_clicked_at, and a click_history JSON blob or multiple custom date fields depending on GoHighLevel's custom field capacity. Aggregate open/click rates recalculate at the destination. Exact click-through URLs migrate as a tag or custom text field for reporting continuity.

Adobe Campaign opt-in subscriptions link Recipients to named Services. Subscription status and subscription date migrate to GoHighLevel as Tags on the Contact (e.g., tag_name: Newsletter_Q3_2024) and a custom date field for subscription_date. Double-opt-in confirmation flags may need value-mapping if the destination requires explicit status encoding rather than tag presence.

Adobe Campaign programs are hierarchical containers for campaigns. Program labels migrate as GoHighLevel folder names or as a tag group (Program Name) applied to Opportunities. Program-specific permissions do not migrate and must be reconfigured in GoHighLevel's team access settings.

Custom tables created via nms:ext: namespace or FDA connectors require custom extraction logic. We inspect the schema XML to derive the underlying SQL table structure, map column types to GoHighLevel custom field types, and pre-create the destination fields before import. FDA-linked external schemas migrate as standard imports from the exported flat files with schema-derived field mapping.

Adobe Campaign delivery definitions (email content, SMS text, routing parameters) migrate as GoHighLevel Email Templates and SMS Templates. Personalisation tokens resolve against the imported Contact schema. Static asset references (images hosted on Adobe's SFTP) require URL rewriting to the customer's new asset hosting location. HTML email content migrates verbatim where possible; complex dynamic content blocks require rebuild in GoHighLevel's template editor.

Enumerations defined in Adobe Campaign schema XML (deliveryStatus, gender, country codes) map to GoHighLevel custom dropdown fields. We maintain a value-mapping table keyed by enumeration name and apply it during import. Values without a GoHighLevel dropdown match route to a catch-all value and the original text moves to a secondary custom text field for audit.

Adobe Campaign targeting workflows, campaign workflows, and technical workflows export as XML packages. Dynamic content blocks and queryDef expressions break across platform migrations. We do not migrate workflows as code. We deliver a written inventory of every active Adobe Campaign workflow with its trigger, conditions, actions, and a recommended GoHighLevel Automation equivalent. The customer's team rebuilds in GoHighLevel's visual automation builder post-migration.