Migrate from XMPie to Freshsales

XMPie user accounts map 1:1 to Freshsales Users. Email address is the join key for owner resolution — unmatched XMPie owners are flagged before migration so the team can either invite them to Freshsales or assign records to a fallback user.

XMPie product catalog (from uStore) migrates as Freshsales Products. Name, SKU, description, and status map directly. MSRP, cost, and unit-of-measure migrate as custom fields on the Product object since Freshsales does not have native MSRP or unit_cost fields. Additionally, any pricing tier information is stored in custom fields, and the product status values are aligned via value mapping to match Freshsales' active/inactive labels.

XMPie contacts map to Freshsales Leads with standard field alignment for name, email, phone, and address fields. XMPie contact_type maps to Freshsales' lead_status via value mapping: 'Customer' routes to 'Contacted', 'Prospect' to 'New', and 'Partner' to 'Qualified'. Custom properties (Twitter, LinkedIn, lifecycle stage) migrate as custom Lead fields.

XMPie company records map to Freshsales Accounts. Name, website, industry, number of employees, and annual revenue map directly. Social handles (Twitter, LinkedIn) have no Freshsales equivalent — stored as custom Account fields. XMPie company hierarchy maps to Freshsales Parent Account lookup.

XMPie deals map to Freshsales Opportunities. Deal name, amount, close date, owner, and description map directly. Deal probability migrates as a custom Opportunity field. Pipeline stage values map to Freshsales Opportunity Stage via value mapping. Product name and quantity on the XMPie deal do not map natively — stored as custom Opportunity fields.

Freshsales has no native Orders object. XMPie order records (order ID, order date, status, shipping address, line items, quantity) are migrated as a custom object with a lookup to the Account. The Opportunity that represents the associated deal links to the order custom object for reference.

XMPie email activities map to Freshsales Tasks with Type='Email'. Subject maps to Task Subject; body maps to Task Description. Original timestamp and owner are preserved. Tasks are linked to the parent Lead or Contact record by email address match. If multiple contacts share the same email address, the system selects the most recently updated Lead or Contact to ensure consistent linkage.

XMPie notes map to Freshsales Tasks with Type='Note'. Note title maps to Task Subject; note body maps to Task Description. Whether the note had attachments is preserved as a custom flag field since Freshsales Tasks support file attachments but do not track attachment presence as a separate attribute.

XMPie campaign definitions (name, status, type, start date, end date, target audience) have no native Freshsales equivalent. We create a custom Campaign object and store campaign metadata as custom fields. Campaign status values (Active, Paused, Completed, Draft) map via value mapping to Freshsales-compatible status labels.

XMPie audience membership is a property on each contact record (segment name, segment ID, audience size). We create custom pick-list and text fields on the Lead and Contact objects to store segment membership. The full audience definition (segment rules and logic) cannot be preserved in Freshsales since it has no native segmentation engine — those rules must be rebuilt in Freshsales workflows or Freshmarketer.

XMPie workflows, email personalization rules, audience triggers, print job automations, and campaign logic have no Freshsales CRM equivalent. These are explicitly excluded from the migration scope. We export XMPie workflow definitions as a reference document for the team to use when rebuilding automation in Freshsales or a separate marketing platform.

XMPie document templates, InDesign-linked designs, XLIM packages, and personalization assets are tied to the XMPie/InDesign composition engine and cannot run inside Freshsales. File assets (PDFs, images uploaded to XMPie) can be exported and re-hosted in Freshsales Files if the team has a file storage plan.