Migrate from Ayna to Nutshell

Ayna Contact records map directly to Nutshell Person. The source contact ID is preserved in a migration reference field for reconciliation. Email, phone, name, and company association migrate to Nutshell's standard Person fields. Owner assignment from Ayna resolves by email match to a Nutshell User record; unresolved owners are flagged for manual assignment before record import begins.

Ayna Company records represent brands or businesses being tracked and map 1:1 to Nutshell Company. The Ayna company domain becomes the Company Website field and acts as a dedupe key during import. Companies are created before any Person import so that the Company-Person relationship is satisfied at the moment of Person insert.

Ayna Channels represent communication and social platforms connected to a brand. Active versus archived status is critical: we flag which Channels are active at cutover and map them to a custom multi-select picklist on the Nutshell Person record (or Company record depending on the customer's scoping choice). Archived channels are documented but not imported to prevent duplicate customer record noise. Brand workflow stage assignments on channels are preserved as text notes in a custom field for manual review.

Ayna Website Domains tied to brand protection are exported with domain ownership metadata. Nutshell does not have a native website domain object, so we create a custom text field on the Company record (e.g., protected_domains__c) to store domain URLs. This field is informational and does not trigger any synchronization in Nutshell.

Ayna custom fields on Contacts and Companies use Ayna-specific naming conventions that may not map directly to Nutshell. We extract the full field schema during discovery, preserve data types (text, date, currency, picklist) where possible, and create equivalent Nutshell custom fields on the People, Companies, or Leads object before migration. Any Ayna-specific picklist values are recreated in Nutshell's field configuration. Custom field creation happens in the pre-migration phase so that the destination schema is ready before any data moves.

Ayna User records including email, name, and role assignment are exported. We map source user IDs to Nutshell owner fields by email match. Any Ayna Owner without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Active versus inactive status is preserved in a custom field for reference.

Ayna social account connections for brand monitoring require re-authentication in the destination platform because OAuth tokens do not transfer between systems. We document the current social platform connections during discovery (LinkedIn, Twitter/X, Facebook, Instagram, etc.) and flag which require re-linkage after migration. Social handles and URLs migrate as custom text fields on the Person or Company record for reference, but the live connection must be re-established manually in Nutshell or via Nutshell's integrations.

Attachments to brand protection records may include screenshots, legal documents, or brand assets. We export file references and note the original file type. Nutshell attachments are associated to Person, Company, or other records via its native file handling. Actual file migration depends on Nutshell's file size limits (25 MB per file on standard plans) and the customer's willingness to re-upload large brand assets. We flag oversized files and attachments that require re-upload after cutover.