Migrate from Ayna to Freshsales

Ayna Contact records map directly to Freshsales Contact. Standard fields (name, email, phone, company association) migrate straightforwardly. We resolve the company association by matching Ayna's company_id to the Freshsales Account record created in the prior phase. Custom fields on Ayna Contacts extract to Freshsales custom fields created during schema setup, preserving data types where possible.

Ayna Company records represent the brands or businesses being protected and map to Freshsales Account. The company name becomes the Account Name field. Website and domain metadata from Ayna maps to the Account Website field. Account is created before any Contact import so that the company association Lookup is satisfied at Contact insert time.

Ayna Channels represent communication and social platforms connected to the brand. Freshsales has no native Channel object, so we map active channels to a multi-select picklist field or separate text fields on the Account record (e.g., channel_facebook, channel_twitter, channel_linkedin). We flag archived channels separately during discovery so they do not clutter the destination data.

Ayna Website Domains tied to brand protection and synchronization map to the Account Website field and a custom domain tracking field on Account. Multiple domains associated with a single brand map to a comma-separated custom field or a related custom object if the customer has Growth tier or above.

Social account connections for brand monitoring require re-authentication in Freshsales since OAuth tokens do not transfer between platforms. We document the current social account connections (platform, handle, link URL) during discovery and create corresponding custom fields on Account so the customer can re-link after migration.

Ayna User records with email, name, and role assignment export via available API or manual dump. We resolve owners by email match against Freshsales User records. Any Ayna User without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Ayna custom fields on Contacts and Companies may use brand-specific naming conventions that do not exist in Freshsales. We extract the field schema during discovery, create equivalent custom fields in Freshsales during schema setup, and map field values during import. Data type mismatches (e.g., Ayna date stored as text) are flagged and cleaned in the transform step before import.

Attachments to Ayna brand protection records (screenshots, legal documents, brand assets) may not transfer as file objects since Freshsales file storage behaves differently. We export file references and URL paths where available, map them to Freshsales Document records or URL custom fields, and flag the customer to re-upload critical brand assets post-migration if the file objects do not migrate cleanly.