Migrate from Altcraft to Freshsales

Altcraft Profiles map to Freshsales Contacts with the Account resolved from the Profile's company association. If the Profile includes company data, we create the corresponding Account first, then link the Contact. Behavioral event history (channel opens, clicks, purchases) is preserved as a structured note attached to the Contact and as custom fields for key metrics like total_order_count and last_purchase_date. Altcraft custom profile fields map to Freshsales custom contact fields, with type conversion (date fields, number fields, picklist fields) handled during the transform phase.

Static segments in Altcraft (fixed lists of Profile IDs) map directly to Freshsales Lists. We export the segment as a list of Profile IDs, resolve each to the migrated Freshsales Contact, and import the Contact IDs into the corresponding Freshsales List. Segment membership dates are preserved as custom fields on the List membership.

Dynamic segments in Altcraft use real-time behavioral criteria (last_action_date, channel_consent, purchase_value range) that do not have a direct Freshsales equivalent without Freshmarketer. We export the segment definition as structured criteria documentation and recommend either rebuilding the logic as Freshsales Contact filters or licensing Freshmarketer for dynamic journey-based segmentation. The customer chooses the approach during scoping.

Altcraft message templates export in standard formats (HTML with merge tags). We import them into Freshsales as Email Templates with the appropriate merge field syntax converted from Altcraft's format to Freshsales' {{contact.field_name}} syntax. A/B test variants transfer as separate template records with a naming convention noting the variant label.

Altcraft campaigns (send history, open/click analytics, channel assignment) have no single Freshsales equivalent because Freshsales does not have a native Campaign object in the core CRM tier. We map campaign metadata to a Freshsales Deal record for financial tracking and to Tasks or Events for engagement analytics. Channel attribution data is preserved as custom fields on the Deal. Marketing attribution reporting requires Freshmarketer.

Altcraft Control Groups are holdout groups for comparative campaign analytics tied to Profile IDs. Freshsales does not have a native Control Group object. We preserve Control Group membership as an explicit custom field (e.g., control_group_id__c) on the migrated Contact record and document the Control Group structure (name, size, assignment logic) so the customer's admin can recreate comparative analysis using Freshsales Reports or Freshmarketer.

Altcraft Products transfer as Freshsales Product2 records. ProductCode, name, description, and pricing (standard price) migrate directly. Product images do not transfer automatically; we recommend re-uploading product imagery post-migration or using a CDN-linked image URL in the product description field.

Altcraft order records link to the Profile and Product at migration time. We create a Freshsales Deal for each order with the Contact (from the Profile mapping) as the primary relationship and the Product as a line item. Order total, order date, and order status transfer as Deal fields. If Altcraft order data includes loyalty points or promo codes, those transfer as custom fields on the Deal.

Altcraft loyalty tiers (Bronze, Silver, Gold, etc.) tied to customer Profiles have no native Freshsales equivalent. We preserve the loyalty tier as a custom picklist field on the migrated Contact record. The tier history (promotions, redemptions) transfers as a structured note attached to the Contact.

Altcraft promo code pools with rules (discount type, minimum order value, validity period) export as structured data tied to the order or Profile. We map active promo codes to a custom field on the Freshsales Deal and document the full promo rule set for the customer's admin to re-implement using Freshsales' deal customization or a third-party CPQ tool if complex pricing logic is required.