Migrate from Ayna to Pipedrive

Ayna Contacts map to Pipedrive Person records. Standard fields (name, email, phone, company association) migrate directly. Custom properties on Ayna Contacts extract to Pipedrive custom fields during discovery; we map field names and data types to Pipedrive's field type options (text, number, date, dropdown, checkbox). Owner assignment migrates via email match against Pipedrive Users. Records with no owner go to a reconciliation queue for admin assignment.

Ayna Company records (representing brands or businesses) map to Pipedrive Organization. Company metadata and association links to Contacts are preserved during migration. We use the Organization name as the dedupe key and set the Website field from the Ayna domain record where available. Organization is created before any Person import so that the Organization ID Lookup is satisfied at Person insert.

Ayna Deals map to Pipedrive Deals. Pipeline and stage from Ayna map to Pipedrive pipeline_id and stage_id. We configure the Pipedrive pipeline before migration using the stage names and order from Ayna. Deal value, currency, expected close date, and owner assignment migrate directly. If Ayna stores lost/open reason in custom fields, we map those to Pipedrive's Lost Reason field on the Deal.

Ayna Channels (communication and social platforms connected to the brand) have no direct Pipedrive equivalent. We document all active versus archived Channels during discovery and deliver a written record for manual rebuild in Pipedrive. Active Channels that require social posting or monitoring can be reconnected via Pipedrive's social integration marketplace tools post-migration. This is a configuration handoff, not a data migration.

Ayna Social Account connections (for brand monitoring) require re-authentication in Pipedrive because OAuth tokens do not transfer across platforms. We document the current connection list (platform, account handle, permissions) during discovery and flag which accounts need re-linkage in Pipedrive or third-party social management tools. The social account data itself does not migrate as a live connection.

Ayna Website Domains tied to brand protection and website synchronization migrate as Pipedrive custom fields on Organization (domain_name, registrar, ownership_expiry). We extract the domain ownership metadata during discovery and map it to the destination field schema. Domain monitoring workflows do not migrate; we document the workflow configuration for manual rebuild in Pipedrive Automation or the customer's preferred monitoring tool.

Ayna custom fields on Contacts and Companies use Ayna-specific naming conventions. We extract the field schema during discovery, map each field to an equivalent Pipedrive custom field (matching the data type: text, number, date, single-select, multi-select), and create the custom fields in Pipedrive before migration. Custom fields on Pipedrive apply per Person, Organization, or Deal, not org-wide by default.

Ayna Users map to Pipedrive Users by email address. We export Ayna user records including name, email, and role assignment and resolve each by email match against the Pipedrive User table. Any Ayna user without a matching Pipedrive User is flagged for manual provisioning before record migration begins. Owner assignment on migrated records depends on this resolution step completing first.

Attachments to Ayna records (screenshots, legal documents, brand assets) are exported as file references. Actual file migration depends on Pipedrive's attachment limits by plan (file attachments are supported on all plans but with size limits). We document the attachment inventory and flag any files that exceed Pipedrive's size thresholds for manual transfer or cloud storage re-linkage.

Ayna engagement records (calls, emails, meetings, tasks) associated with Contacts map to Pipedrive Activity records linked to the corresponding Person. Call disposition, duration, and timestamp migrate to Activity type, title, and due date fields. Meeting details (date, location, attendees) map to Activities of type Meeting. We resolve the Person ID on each Activity import so the timeline links correctly.