Migrate from APSIS One to Freshsales

APSIS One Profiles map directly to Freshsales Contacts. The Profile email address becomes the Contact email and serves as the dedupe key during import. First name and Last name from APSIS One default Attributes map to the standard Freshsales First Name and Last Name fields. Any Profile without an email address is held in a reconciliation queue since Freshsales Contacts require an email for most standard functions. We preserve the original APSIS One profile ID in a custom field apsis_profile_id__c for audit trail and cross-reference.

APSIS One default Attributes (First name, Last name, Email, Mobile, Birth date, CRM-ID) map to Freshsales standard Contact fields with matching types. Mobile phone numbers migrate to the Freshsales Phone field with country code formatting preserved per MSISDN format. Birth date maps to Freshsales Date of Birth. We validate field types before mapping to prevent import errors from type mismatches.

Custom Attributes from APSIS One (created in the Section Data Model) map to Freshsales custom Contact fields. We create the destination schema in Freshsales before import, matching attribute names and selecting appropriate field types (text, number, date, picklist, checkbox). Attributes with multiple values (arrays) map to Freshsales multi-select picklists or text fields depending on the data shape. We deduplicate attribute names across Sections and flag any that would conflict with Freshsales reserved field names.

APSIS One Tags are flat string labels stored as a list per Profile. We preserve the tag set exactly and recreate tag associations in Freshsales as contact tags on each Contact record. Tags with spaces or special characters are sanitised to Freshsales tag format. If a Profile carries more than 20 tags, we review the tag distribution with the customer and collapse low-frequency tags into a single Notes entry rather than creating a tag explosion in Freshsales.

Behavioural Events logged against an APSIS One Profile (email opened, page viewed, link clicked, custom event types) have no direct Freshsales equivalent as a native event model. We transform Events into Freshsales Task records with a custom event_type__c field storing the original APSIS One event name, a custom event_payload__c field storing the JSON payload, and ActivityDate set to the original event timestamp. This preserves the sequence and timing of events against the Contact record in the activity timeline. We chunk large event sets to respect APSIS One's 100 kB request body ceiling during export.

APSIS One Segments (dynamic rule-based and static list-based) do not have a direct API export mechanism. We export the Profiles in each Segment via the Profiles in Segment Report endpoint and create corresponding Contact Lists in Freshsales. Dynamic Segment logic (rule-based criteria) cannot be replicated automatically in Freshsales Lists; we document the original Segment criteria and recommend manual recreation in Freshsales' filter-based List builder. Static Segments map 1:1 as named Contact Lists.

APSIS One Consent 2.0 stores consent flags and timestamps per channel (email, SMS) as Profile Attributes. We preserve consent records exactly on each Contact by creating Freshsales custom fields (email_consent__c, sms_consent__c as checkboxes) and mapping the original consent timestamps to date fields. This avoids re-permissioning campaigns post-migration and satisfies GDPR obligations for ongoing communication.

Marketing Automation Flows in APSIS One have no public API for export. We cannot migrate them as code. During discovery, we capture flow screenshots, trigger conditions, step sequence, and branching logic from the Marketing Automation Canvas. We deliver a written Flow Inventory document listing every active Flow with its trigger, conditions, actions, delays, and A/B branches, mapped to a recommended Freshsales Workflow equivalent. The customer's admin rebuilds each Flow in Freshsales' visual workflow builder. Complex multi-branch flows should be prioritised in this rebuild sequence.

APSIS One bidirectionally syncs with SuperOffice, Efficy Enterprise, Microsoft Dynamics 365, and Lime CRM, mapping CRM Contacts, Accounts, and Deals to APSIS Profiles. This sync state is not accessible via the public API. We export the current Profile data and the integration configuration (which CRM is connected, field mapping), then deliver a re-integration checklist for the customer to re-pair the CRM with Freshsales after cutover. Freshsales has no native APSIS One connector; if bidirectional sync with the original CRM is required, the customer must configure a Freshsales integration or use a middleware connector (Zapier, Workato, or the native Freshsales AppMarketplace connector for Dynamics).