Migrate from Apptivo to Salesforce Sales Cloud

Apptivo Contacts with assigned owner and active status map to Salesforce Contact; Apptivo Contacts that represent unqualified prospects with no associated Customer record map to Salesforce Lead. We use the Apptivo contacts app's ownership and status fields to determine the split. The original contact name, email, phone, and address fields map 1:1. Custom attributes on the Contacts app enumerate during discovery and map to typed Salesforce custom fields on Contact or Lead.

Apptivo Customers (B2B account records) map to Salesforce Account. Associated contact sub-records within the Customer object map to Salesforce Contact records linked to the Account via AccountId lookup. We resolve the Customer-to-Account mapping first because all downstream object imports (Opportunities, Cases) depend on AccountId being populated. Customer billing address becomes Account BillingAddress; shipping address becomes Account ShippingAddress.

Apptivo Lead object maps directly to Salesforce Lead. Lead scoring and lead source tracking properties from Apptivo map to custom fields on Salesforce Lead (apptivo_lead_score__c, apptivo_lead_source__c). Lead status values in Apptivo map to Salesforce Lead Status picklist values; we document any custom status values that require new picklist entries in Salesforce before migration.

Apptivo Opportunities map to Salesforce Opportunity. Deal amount maps to Amount, expected close date maps to CloseDate, and stage name maps to StageName. We map Apptivo pipeline stages to Salesforce Sales Processes via Record Type configuration. Deal owner resolves to Salesforce OwnerId via email match against User. Any Apptivo Opportunities with no associated Customer require a dummy Account or a Salesforce admin decision before migration.

Apptivo Cases map to Salesforce Case. Case status, priority, owner, and description map to CaseStatus, Priority, OwnerId, and Description respectively. Case conversation threads migrate to Salesforce CaseComment records or EmailMessage threads linked to the Case. We resolve the Case's associated Customer (Account) and Contact (Contact) via the Apptivo case-to-customer relationship during import. Tier-based ticket limits in Apptivo have no Salesforce equivalent; we flag any cases that would exceed the destination org's entitlement process limits.

Apptivo Items (product and service catalog) map to Salesforce Product2. Item name, SKU, price, and description map to Name, ProductCode, UnitPrice, and Description on Product2. Standard Pricebook entries are created during import to enable OpportunityLineItem association. Custom attributes on the Items app enumerate and map to custom fields on Product2.

Salesforce Sales Cloud does not include an Invoice object in the standard schema; Invoices from Apptivo map to a custom Invoice__c object with line items mapped to a related InvoiceLine__c custom object. Invoice status, invoice date, due date, and amounts become custom fields. Partial payment history is preserved in a custom status field. Customers with Salesforce Billing and Revenue Management use cases may require a separate billing platform integration post-migration.

Apptivo Projects map to a Salesforce custom Project__c object with project-level fields (name, status, start date, end date, owner). Associated tasks within the project map to Salesforce Task records linked via WhatId to the Project__c record. Project milestones map to Milestone__c custom records if the destination org includes Salesforce Field Service. Custom project fields enumerate and map to custom fields on Project__c.

Apptivo Employee records map to Salesforce Contact if used as a customer-facing contact, or to User if used for internal ownership assignments. We scope the mapping decision during discovery: if Employees are used primarily in project assignment and approval workflows, they may need a custom Employee__c object instead. Ownership assignments on migrated records prefer User mapping for active Apptivo employees; inactive employees map to Contact for historical record keeping.

Apptivo Master Layout custom attributes across all active apps enumerate into a per-app field mapping table. Each attribute's data type (text, number, date, dropdown, radio button) maps to the nearest Salesforce field type. Dropdown and radio button attributes from Apptivo map to Salesforce Picklist or Multi-Select Picklist depending on single vs. multi-select configuration. We pre-create all custom fields via Salesforce metadata API before record import begins.

Apptivo file attachments on Contacts, Customers, Cases, and Opportunities migrate to Salesforce ContentDocument records linked via ContentDocumentLink to the parent record. Large file attachments may exceed Apptivo export limits; we chunk large file batches and verify attachment count reconciliation during sandbox pass. PDF attachments on Invoices migrate as ContentVersion records linked to the parent Invoice__c record.

Apptivo record owners (owner_id on Contacts, Customers, Opportunities, Cases, and Projects) map to Salesforce User by email match. Any Apptivo owner without a matching Salesforce User enters a reconciliation queue; the customer's admin provisions the missing User record before record import resumes. Inactive Apptivo users map to an inactive Salesforce User or a dedicated system user for historical assignment preservation.