Migrate from iPresso to Freshsales

iPresso Contact records map to Freshsales Contact. The HubSpot-analogous lifecycle stage in iPresso (if used) migrates to a custom picklist field lifecycle_stage__c on Contact for audit continuity. Behavioral event counts (opens, clicks, form submissions) migrate as numeric custom fields so the sales team retains visibility into contact engagement history without requiring a marketing automation platform to access the data.

iPresso Company records map directly to Freshsales Account. Company name becomes the Account Name field. Industry classification, annual revenue, and employee count from iPresso custom fields map to Freshsales standard fields or custom equivalents. Account is created before any Contact import so that the Account Lookup is satisfied at the moment of Contact insert.

iPresso marketing campaigns with revenue attribution or pipeline associations map to Freshsales Deals. Multi-channel campaign structures (Email, SMS, Web Push) do not have a direct Freshsales equivalent because Freshsales does not manage outbound marketing campaigns as structured objects. We extract campaign name, target audience size, and any associated revenue data as Deal records with a custom campaign_name__c field for reference. Full campaign rebuild documentation is delivered separately.

Contact segmentation tags migrate directly as Freshsales Tags. Tag names and memberships transfer as straightforward label associations without complex transformation. Tags used for behavioral segmentation (e.g., campaign_id tags) migrate as Tags and additionally as a custom multi-select picklist field behavioral_segments__c on Contact.

iPresso multi-step automation sequences do not migrate to Freshsales as code. Workflows reference contacts, tags, channels, and custom fields by internal identifiers that change at migration. We deliver a written inventory of every active iPresso workflow with its trigger conditions, action steps, time delays, and channel assignments, plus recommended Freshsales Workflow equivalents. The customer's admin rebuilds them post-migration.

iPresso custom contact properties (beyond standard name, email, phone) require explicit mapping to Freshsales custom fields. We define field types during scoping (text, number, date, picklist, multi-select, checkbox) and pre-create the schema in Freshsales before any data import. Field validation rules and picklist values transfer to maintain data integrity.

iPresso custom company properties map to Freshsales Account custom fields. Industry-specific configurations from iPresso Enterprise (FMCG, Finance, Travel, Education verticals) map to custom fields appropriate for the customer's business context.

iPresso email creative assets with HTML content migrate to Freshsales Email Templates. Dynamic personalization tokens referencing iPresso contact properties require field reference updates to point to Freshsales Contact fields. Static HTML content transfers without modification.

iPresso channel configurations (sender settings, SMS provider credentials, Web Push credentials) do not transfer between platforms because they are platform-specific integrations. We document the channel configuration settings (sender domains, SMS sender IDs, Web Push service accounts) so the customer's admin can reconfigure them in Freshsales or the appropriate Freshsales Suite channel product.