Migrate from Wice CRM to Freshsales

Wice Contacts map directly to Freshsales Contacts. We use Wice's built-in CSV export for contacts, then transform the output to match Freshsales' import column headers. Email address serves as the unique dedupe key. The link to the parent Wice Organization resolves to a Freshsales Account ID after the Accounts phase completes.

Wice Organizations (separate company records that Contacts are linked to) map to Freshsales Accounts. We export Organizations first and import them before Contacts so that the Account relationship is satisfied at Contact insert time. The Wice Organization name becomes the Account Name; the website field carries over if populated.

Wice Deals map to Freshsales Deals. The Wice deal value, expected close date, and owner assignment carry over. Wice custom pipeline stages require an explicit stage-mapping table generated during discovery before Deals are written to Freshsales; a deal in Wice stage 'Proposal Sent' must map to the customer's actual Freshsales pipeline stage name. Freshsales requires that the target pipeline exists before Deals are imported.

Wice allows full customization of pipeline stages per installation. We capture the customer's actual Wice stage names during discovery and generate a stage-mapping table mapping each to the Freshsales pipeline stage that best represents the same sales state. Stage probability percentages transfer from Wice to Freshsales if they are stored as fields.

Wice Tasks exist standalone or inside Projects. Standalone tasks map to Freshsales Tasks with Status, Priority, due date, and description preserved. Task assignment resolves by matching the Wice owner's email address against the Freshsales User table. Tasks without a matching user are assigned to the migrating admin for manual reassignment.

Wice Notes attached to Contacts, Organizations, Deals, or Projects migrate to Freshsales Notes linked to the equivalent Contact, Account, or Deal record. Plain text content transfers directly. Bold, lists, and other formatting present in Wice notes may be simplified to plain text depending on the original note's complexity.

Wice Projects contain tasks, assignees, and custom fields. Freshsales does not have a native Project object. If the customer uses Projects primarily for deal tracking, Projects map to Deals with project-specific custom fields. If Projects represent a distinct data model, we create a Freshsales custom module with a schema matching the Wice Project structure, and tasks inside each project link to the parent custom record.

Wice Campaigns (basic and advanced tiers) map to Freshsales Campaigns. Advanced campaign targeting and tracking properties that do not map to standard Freshsales Campaign fields are stored as custom fields on the Campaign record. Campaign history such as sent, open, and click data does not transfer because Freshsales Campaigns track membership and status but not granular engagement metrics from the source system.

Wice Tickets linked to Contacts or Organizations map to Freshsales Cases if the destination Freshsales plan includes Service Cloud features (Pro and above). Ticket status, priority, and custom fields map to Case Status, Priority, and equivalent custom fields. Ticket numbering sequences do not transfer and restart in Freshsales. If the destination plan lacks Service Cloud, Tickets map to Deals with a ticket-type custom field.

Wice custom fields on Contacts, Organizations, Deals, and Projects require explicit mapping. We capture all custom field names and data types during discovery. Picklist-style custom fields require that the same picklist values are created in Freshsales before import because Freshsales enforces picklist value whitelists during CSV import. Custom field names must match exactly in the import CSV header; we rename them post-import if the customer prefers different labels.

Wice uses a category system for deduplication and classification that does not map 1:1 to Freshsales Tags. We export category assignments as a comma-separated string stored in a Freshsales custom text field, or we create Freshsales Tags from the category values if the customer prefers tag-based segmentation. The customer chooses the strategy during scoping.

Wice Owners referenced on Contacts, Organizations, Deals, and Tasks resolve by email match against the Freshsales User table. Owners without a matching Freshsales User are held in a reconciliation queue; the customer's admin provisions the missing User accounts before record import resumes. Freshsales does not support bulk user import, so User provisioning is a manual admin step.