Migrate from Acumen to Freshsales

Acumen contacts migrate directly to Freshsales contacts. Email address serves as the unique identifier for deduplication. Records without email land with a pending verification flag for manual review. This approach ensures data integrity and prevents duplicate records from entering your Freshsales environment during migration.

Acumen contacts with status='prospect' and no closed deal route to Freshsales Lead. The Acumen prospect_status value maps to Freshsales Lead status pick-list. Contacts with closed-won deals in Acumen route to Contact in Freshsales. This routing logic ensures that your sales pipeline maintains proper lead lifecycle management in the new system.

Acumen companies become Freshsales accounts. Company name maps to Account Name. Website domain maps to Website field. Parent-company hierarchies in Acumen translate to Parent Account lookups in Freshsales. This maintains your organizational structure and account relationships in the new CRM platform.

Acumen deals migrate as Freshsales Opportunities. Deal name maps to Opportunity Name, amount maps to Amount, close date maps to Close Date. Pipeline association determines which Freshsales sales pipeline the opportunity belongs to. This ensures accurate deal tracking and pipeline management in your new system.

Acumen deal stage names map value-by-value to Freshsales Opportunity Stage values per pipeline. Each Acumen pipeline requires a corresponding Freshsales pipeline to scope stage values correctly. Probability and forecast category re-applied from Freshsales side. This mapping preserves your sales process stages and forecasting logic in the new platform.

Acumen activity records (calls, emails, meetings) migrate as Freshsales Sales Activities. Activity type maps to Freshsales Activity Type field. Original timestamp, duration, and owner preserved. Subject line derived from activity type and related record. This preserves your complete activity history for comprehensive customer engagement tracking.

Acumen notes migrate as Freshsales notes attached to the corresponding Contact, Account, or Opportunity. Rich-text formatting preserved where supported. Notes without a parent record attach to the primary contact record. This ensures all important information and context is preserved and accessible in your new CRM system.

Acumen contact-level custom properties require Freshsales custom fields created before migration. Field type determined by Acumen property type: text strings become text fields, numbers become number fields, dates become date fields, and pick-list values become picklist fields with value mapping.

Deal-level custom properties in Acumen map to Freshsales Opportunity custom fields. Acumen deal priority, probability override, and custom currency fields require custom field creation and type-aware transformation in Freshsales. This preserves all deal-specific custom data and ensures accurate reporting in your new system.

Acumen user records resolve to Freshsales users by email match. Unmatched owners receive a fallback assignment (default user or queue) and are flagged in the migration report for admin review and user invitation. This ensures proper ownership assignment and allows your admin to resolve any user mapping issues before go-live.

Acumen file attachments re-upload to Freshsales Files and attach to the corresponding record. File size limits enforced (Freshsales default 25MB per file). Inline images in notes downloaded and rehosted as Freshsales file attachments. This preserves all your important documents and media files in the new system.

Acumen workflows, automation rules, and triggered actions do not transfer to Freshsales. We export workflow definitions as a reference JSON document for your Freshsales admin to rebuild using Freshsales Workflows after migration completes. This documentation serves as a blueprint for recreating your automation logic in the new platform.