Migrate from APTANIA CRM to Salesforce Sales Cloud

APTANIA Contact records with a B2C flag map to Salesforce Contact; those with a B2B flag map to Salesforce Contact attached to an Account. APTANIA Contacts that are early-stage prospects (no associated deal history) are treated as Salesforce Leads at migration time. The original APTANIA B2C/B2B flag is preserved in a custom field aptania_contact_type__c on both Lead and Contact for reporting continuity. We apply the split logic during the staging transform phase before inserting into Salesforce.

APTANIA Company records map directly to Salesforce Account. Company name is the primary dedupe key during import. Account is created before any Contact import so that the AccountId lookup is satisfied at the moment of Contact insert. The APTANIA company ID is stored in a custom field aptania_company_id__c for reconciliation.

APTANIA Deals map to Salesforce Opportunity. The deal monetary value maps to Amount, close date to CloseDate, and stage name to StageName. We infer the Salesforce Opportunity Record Type from APTANIA's pipeline assignment during scoping. Deals without an associated Company record in APTANIA create Opportunities without an AccountId and are flagged for manual Account assignment post-migration.

APTANIA deal stage names are mapped to Salesforce StageName values. We create a Salesforce Sales Process and corresponding stage values that match the APTANIA stage names as closely as possible, preserving stage probability percentages from APTANIA in the Salesforce StageProbability field. The customer reviews and approves the stage mapping before production migration.

APTANIA activity logs migrate to Salesforce Task and Event objects. Email activities become Task records with IsTask=false and EmailMessage child records; call activities become Task with TaskSubtype=Call; notes migrate as Salesforce Note records linked via ContentDocumentLink to the parent Contact, Account, or Opportunity. The ActivityDate on each record preserves the original APTANIA timestamp for timeline ordering. Activity schema inference is required because APTANIA's export schema is not publicly documented; we extract what is available and flag any unmapped activity types in the data map.

APTANIA pipeline definitions map to Salesforce Record Types on Opportunity. Each APTANIA pipeline becomes a Salesforce Record Type with its own Sales Process that whitelists the relevant stage values. Page Layout assignments are configured per Record Type so that sales reps see the correct fields for each business line. This configuration happens in a Salesforce Sandbox before production migration.

APTANIA custom field values and names are exported and recreated as Salesforce custom fields (with __c suffix) on the corresponding standard object. Field data types are inferred from the exported values (text to Text, numeric to Number, date to Date). The original APTANIA field name is documented in the custom field description for admin reference. Any custom property that cannot be typed from the export (e.g., complex nested objects) is flagged for the customer's admin to design in Salesforce before migration.

APTANIA user records map to Salesforce User by email address match. The customer provisions Salesforce Users before migration; we reconcile the APTANIA user list against the Salesforce User table and flag any APTANIA owner references that do not have a matching Salesforce User. Unmatched owners are held in a reconciliation queue for admin provisioning before record import resumes.

APTANIA's B2C/B2B classification does not map to a standard Salesforce field. We preserve it as a custom picklist field aptania_contact_type__c on both Lead and Contact. Customers running mixed B2C/B2B operations use this field to segment reports, build list views, and configure sharing rules post-migration.

APTANIA's channel attribution data (referrer, UTM parameters, landing page history) is stored in APTANIA's internal tracking system and is not accessible via export. We do not migrate web tracking data. This gap is documented in the data map and disclosed to the customer before migration. We recommend configuring fresh web tracking in Salesforce via an AppExchange tracking app or a third-party attribution tool (e.g., HubSpot tracking pixel, Google Analytics integration) before go-live to preserve future attribution data.

APTANIA's trigger-based email automation rules do not export. All automation logic is lost at migration time. We provide a pre-migration checklist that includes screenshot documentation of every active automation rule, trigger condition, and associated contact list. The customer's admin uses this as a reference guide to rebuild automation logic in Salesforce Flow or a sales engagement platform (Salesloft, Outreach, or Sales Cloud Engagement) post-migration.

APTANIA lifecycle stage values migrate to a custom picklist field aptania_lifecycle_stage__c on Lead and Contact. This preserves the original stage history for reporting continuity even though Salesforce does not have a native lifecycle stage concept. The field is available for segmentation, list views, and Flow triggers in Salesforce.