Migrate from APSIS One to Pipedrive

APSIS One Profiles map to Pipedrive Person records. The Profile's default Attributes (first_name, last_name, email, mobile, birth_date, crm_id) map to their Pipedrive Person field equivalents (name, email, phone, birthday). We use email as the dedupe key during import to prevent duplicate Person records. Any APSIS One Profile without an email address is held in a reconciliation queue for the customer to resolve before import completes, because Pipedrive Persons require at least a name or email.

Custom Attributes from APSIS One map to Pipedrive custom fields on Person. We infer field type from the Attribute's data: string attributes become text fields, numeric attributes become numeric fields, date attributes become date fields, and boolean attributes become checkbox fields. Multi-value list attributes from APSIS One become multi-select picklist fields in Pipedrive. We deduplicate attribute names across Sections and flag any that share a name but differ in type, requiring customer resolution before import.

APSIS One Tags are flat string labels applied to Profiles. Tags export as a list per Profile. We create the corresponding Label records in Pipedrive during schema setup and link them to the Person record at import time. Tag names with spaces are normalized to Pipedrive's label naming convention (underscores or title case). If the same tag is applied to fewer than five Profiles, we flag it as a low-frequency label that may not justify permanent Pipedrive label creation.

APSIS One Events are behavioral records with event type, timestamp, and optional payload. Pipedrive has no generic event log; behavioral history maps to Pipedrive Activity records. Email open and click events become Task-type activities with the event type as the subject and the timestamp preserved. Web behavioral events (page views, form submissions) become Note records linked to the Person, because they do not map cleanly to Pipedrive's structured activity types. We chunk high-volume event histories (over 5,000 events per Profile) into paginated batches to stay within Pipedrive's activity creation limits and the APSIS One 100 kB request body ceiling.

APSIS One Segments (dynamic or static) are audience groupings built from rule-based attribute conditions. We do not migrate Segments as a functional object because Pipedrive's Lists and Smart Lists use a different filter syntax. During discovery we capture the Segment definition (rule structure, operator logic, and member count), and we deliver a written Segment rebuild guide that maps each APSIS One rule condition to the equivalent Pipedrive Smart List filter. Static Segment members (fixed membership) are migrated as a Person filter save-as-list in Pipedrive.

APSIS One Marketing Automation Flows have no public API export. We capture the flow structure (triggers, conditions, branches, and actions) during discovery as a JSON schema document and as annotated screenshots, then deliver a written rebuild guide for Pipedrive's Workflow Automation builder. The guide maps each APSIS One flow node to its Pipedrive Workflow equivalent (trigger type, condition operator, action type). Complex multi-branch flows with conditional waits require the longest rebuild time; we prioritize them by business criticality during sequencing.

APSIS One bi-directionally syncs with webCRM, Efficy Enterprise, Microsoft Dynamics 365, and Lime CRM. The integration maps CRM Contacts to APSIS Profiles, CRM Accounts to Profiles with company attributes, and CRM Deals to Profiles with deal-related attributes. We export the current CRM-linked Profile data and re-establish sync post-migration by re-pairing the CRM integration in APSIS One and triggering a full resync, or by configuring Pipedrive's native CRM sync for the customer's target CRM. The APSIS One live sync state is not accessible via API, so sync history and last-sync timestamps are flagged as data that must be rebuilt from the CRM side.

Consent 2.0 in APSIS One stores consent flags and timestamps per channel (email, SMS) as Profile Attributes. We preserve consent records exactly in Pipedrive by mapping them to Person custom fields: email_consent (boolean), email_consent_date (date), sms_consent (boolean), sms_consent_date (date). We do not overwrite existing consent data in Pipedrive if the destination already has records. Consent records are migrated before any marketing activity to avoid re-permissioning campaigns from scratch.

APSIS One Sections are organizational units that hold Segments and Flows. We map Sections to Pipedrive Workspaces if the customer uses Pipedrive's multi-workspace setup, or to a named Person filter group if the account uses a single workspace. Section names become workspace names or filter group names in Pipedrive during schema setup.

APSIS One channel configurations (email sending limits, SMS capacity) are account-level settings, not per-Profile data. We capture the channel preference on each Profile as consent attributes (email_enabled, sms_enabled) and map them to Pipedrive Person custom fields. The account-level sending infrastructure does not migrate; Pipedrive's email sending is handled through Pipedrive's own mail servers or an integrated SMTP service.