Migrate from Actito to Freshsales

Actito Profiles are the central record type and map to Freshsales Contacts or Leads depending on lifecycle status. We use a routing rule during scoping: Prospects with no purchase history route to Lead; Profiles with a deal association or past campaign interaction route to Contact. Subscription preferences, custom profile attributes, and GDPR compliance flags preserve as custom fields on the target record.

Actito Custom Tables linked to Profiles map to Freshsales custom fields on the equivalent object. We inspect the table schema during discovery, map field types (string to text, numeric to number/currency, date to date, multi-value to multi-select picklist), and pre-create all custom fields before data import. Lookup relationships between Custom Tables resolve via composite custom field pairs in Freshsales.

Actito Entities partition all resources (data structures, campaigns, scenarios) within a licence. Freshsales does not have native entity partitioning. We map Actito Entity names to Freshsales Territory assignments, or tag records with the originating entity name for audit and segmentation. The customer chooses the approach during scoping.

Actito Profiles linked to a company association map to Freshsales Account. The company name becomes Account.Name, and the Profile link establishes the Account-Contact relationship. Company attributes from any linked Custom Table migrate as Account custom fields.

Actito Deal records (when used as a campaign-linked transactional record or subscription tracker) map to Freshsales Deal. Deal stage maps to Freshsales Deal Stage, and the owner assignment resolves via Owner-User email matching. Note that Actito's deal concept differs from Freshsales Deals in that Actito Deals often track subscription or campaign financials rather than sales pipeline progress.

Profile-level opt-in, consent flags, channel preferences, and GDPR compliance attributes migrate as custom fields on Contact or Lead. Double opt-in status, channel-level consent flags, and subscription start dates preserve verbatim. We map the Actito preference tree to flat key-value fields in Freshsales.

Actito scenario-triggered call events and campaign call interactions map to Freshsales Task records with Call subtype. Call duration, disposition, and recording reference migrate to Freshsales Task custom fields. Activity date preserves the original timestamp for timeline ordering.

Actito email engagement records (sent, delivered, opened, clicked) map to Freshsales Task records representing the email activity. Email subject, body content, and timestamp migrate. Interaction events (opens, clicks) do not transfer as separate records; the parent email activity migrates as a single Task.

Actito scenario-triggered or campaign-linked meeting events map to Freshsales Task records. If the destination plan includes Event support, meetings migrate as Event records with start/end datetime, location, and attendee references.

Actito profile notes migrate as Freshsales Note records linked via ContentDocumentLink to the parent Contact, Lead, Account, or Deal. Rich text content preserves with attachments migrated as separate ContentDocument records.

Actito Scenarios (event-triggered automation workflows) do not migrate as code. We map the Scenario structure including trigger conditions, branching rules, action steps, and channel references to a written inventory document. The customer's Freshsales admin rebuilds equivalent Workflows in Freshsales Workflows. Complex Scenarios with API-call or webhook actions may require Freshsales custom development or a workflow automation tool.