Migrate from Ayna to HighLevel

Ayna Contact records with name, email, phone, and company association map directly to GoHighLevel Contact. We resolve the company association using Ayna's company_id link to create the GoHighLevel Contact-Company relationship. Custom fields on Ayna Contacts (brand-specific attributes) map to GoHighLevel Contact custom fields, preserving data types where Ayna's schema is extractable. Owner assignment resolves by email match against GoHighLevel Users.

Ayna Company records represent brands or businesses being protected and map to GoHighLevel Account. Company metadata including domain, industry, and size attributes migrate as Account fields or custom fields. We use the company domain as a dedupe key during import to prevent duplicate Account creation. Accounts are created before Contacts so that the company lookup relationship resolves at Contact insert time.

Ayna Channel records represent communication and social platforms connected to the brand. GoHighLevel does not have a native Channel object, so we map Channel records as tags on the associated Contact record. Each active Channel type (email, social platform, messaging) becomes a Contact tag. Archived channels are excluded from migration to prevent importing stale platform references. The customer receives a Channel inventory document listing all active channels for re-authentication in GoHighLevel's integrations.

Ayna domain records tied to website synchronization and brand protection migrate as custom fields on the related Account record (domain_name__c) or as URL tracking entries in GoHighLevel's URL Tracking settings. We document the domain ownership metadata and which Accounts they are associated with. Domain ownership verification and DNS configuration for GoHighLevel's branded tracking domains require separate setup by the customer's admin post-migration.

Ayna User records with email, name, and role assignment map to GoHighLevel Users. We resolve owners by email match against the GoHighLevel destination account. Any Ayna Owner without a matching GoHighLevel User goes to a reconciliation queue for the customer's admin to provision before record import proceeds.

Ayna custom fields on Contacts and Companies may use Ayna-specific naming conventions tied to brand protection attributes. We extract the field schema during discovery (coordinating with Ayna's export where API access is limited), map each custom property to an equivalent GoHighLevel Contact custom field or Account custom field, and preserve data types. GoHighLevel Contact custom fields are created under Settings > Custom Fields before migration. Field names with Ayna-specific terminology are relabeled during mapping to align with GoHighLevel conventions.

Social account connections for brand monitoring require re-authentication in GoHighLevel's integrations. We document the current social account connections during discovery, identify which platforms are connected (LinkedIn, Facebook, Instagram, Twitter, etc.), and produce a re-link checklist for the customer's admin to complete post-migration. No social authentication tokens transfer because the OAuth tokens are platform-bound and cannot be imported into GoHighLevel.

Attachments to brand protection records including screenshots, legal documents, or brand assets migrate as GoHighLevel file attachments on the relevant Contact or Account record where supported by the destination tier. If Ayna's export produces file URLs rather than file binaries, we document the file locations and note that re-upload to GoHighLevel may be required. GoHighLevel's file storage limits vary by plan; we confirm storage capacity at the customer's tier before import.