Migrate from Apptivo to Freshsales

Apptivo Contacts map to Freshsales Contacts with standard fields (name, email, phone, address) mapped 1:1. Per-app custom attributes from the Apptivo Contacts app migrate to Freshsales custom fields, prefixed by the source app name to avoid namespace collisions with attributes from other Apptivo apps. We enumerate every custom attribute in the Contacts app during discovery and build a typed mapping table (text, number, date, dropdown) before import.

Apptivo Leads map to Freshsales Leads with lead score, source tracking, and lifecycle stage preserved as typed properties. The lead scoring value from Apptivo migrates to Freshsales custom field or Freddy AI score field depending on the destination tier. Owner assignment migrates by email match against Freshsales Users.

Apptivo Customer records (B2B account records with associated contacts and addresses) map to Freshsales Accounts. The Apptivo company-level data including billing address and industry classification migrate to Freshsales Account fields. Existing contacts associated with the Customer record in Apptivo link via the Account lookup after both objects import.

Apptivo Opportunity records map to Freshsales Deals. Pipeline stage names from Apptivo map to Freshsales pipeline stages, which we configure in Freshsales before migration. Deal amounts, expected close dates, ownership, and associated Contacts and Accounts resolve at migration time through lookup tables. Closed-won and closed-lost reasons from Apptivo custom fields migrate to Freshsales deal loss reasons.

Apptivo Case records migrate to Freshsales Cases. Case status, priority, owner, and conversation threads migrate with the parent Customer resolved to the Freshsales Account lookup. Customer Portal access levels do not transfer; these require Freshdesk or a manual Freshsales portal configuration post-migration. Large case histories with extensive conversation threads chunk through the Freshsales API in batches of 200 records.

Apptivo Items (product and service catalog entries with pricing and custom attributes) map to Freshsales Products. Item pricing, SKU (mapped to Product Code), and custom attributes migrate as typed Freshsales custom fields. Products must exist before any Deals referencing them are imported, so we run Products first in the dependency order.

Apptivo Invoices map to Freshsales Deals with invoice header data and line item totals preserved. Historical partial payment records migrate as custom deal fields rather than native Freshsales objects (Freshsales does not include a full invoicing module). We recommend reviewing invoice line item detail in Apptivo after migration and rebuilding recurring invoice logic in Freshsales or a dedicated billing tool.

Each Apptivo app maintains its own Master Layout with independent custom attribute sets. We enumerate all custom attributes across all active apps during discovery and build a disambiguation prefixing scheme: attributes from the Contacts app become contact_customappname_attribute, from Cases become case_customappname_attribute. This prevents a field called Region in Contacts from colliding with Region in Cases. The prefixing scheme is documented in the field mapping table and applied consistently across all imports.

File attachments on Apptivo records migrate to Freshsales attachments linked to the parent record. Large attachments above Apptivo's export size threshold chunk through the API with resume capability. We preserve the original filename, MIME type, and upload timestamp from the Apptivo attachment record.