Migrate from MiniCRM to Freshsales

MiniCRM Cards are hybrid containers holding contact details, company associations, deal associations, and custom fields simultaneously. We split Card fields during transformation: primary contact fields (name, email, phone, address) map to Freshsales Contact; any fields the customer designates as prospect-specific (prior to deal qualification) map to Freshsales Lead. We preserve the original Card ID in a custom field mini_crm_card_id__c on both Lead and Contact for reconciliation. The split rule is defined during scoping based on the customer's MiniCRM pipeline usage and business process.

MiniCRM Company records map to Freshsales Account. Company name becomes Account Name; available fields (industry, website, address) map to Freshsales Account fields. Where MiniCRM Company records are sparse (MiniCRM supports fewer normalized fields than typical CRM Account objects), we map the available fields and note any gaps in the scoping report. Account is created before Contact import so the AccountId lookup is satisfied at Contact insert.

MiniCRM Deals are called 'Interests' and are associated with Cards. Deal name, value, stage, and close date map to Freshsales Deal fields. MiniCRM pipeline stage names (often in Polish) are mapped to Freshsales Deal stage values during scoping. The customer configures the Freshsales pipeline stages before migration so that deal stages land in the correct positions.

MiniCRM Tasks linked to Cards migrate to Freshsales Tasks with due date, status, assignee (resolved via email to User), and description preserved. Task recurrence patterns and reminder settings in MiniCRM require explicit mapping; these do not have direct Freshsales equivalents and are documented in the scope for admin rebuild in Freshsales Workflows if needed.

Free-text notes attached to Cards migrate as long-text Note records in Freshsales, linked via ContentDocumentLink to the parent record (Contact, Account, or Deal). Note body migrates as-is; we preserve the association to the original Card record via mini_crm_card_id__c.

MiniCRM custom fields on Cards (text, number, date, choice types) require pre-creation in Freshsales before migration begins. Choice fields require value mapping: MiniCRM picklist values must be matched to Freshsales picklist values. For Lead custom fields specifically, Freshsales requires explicit field mapping in Admin Settings > Leads Module > Field Mapping or data is lost during Lead conversion. We configure this mapping during Freshsales setup before any Lead records import.

MiniCRM user records (name, email, role) map to Freshsales User by email match. Role distinctions in MiniCRM may not map directly to Freshsales' permission model; we document the gap in the scoping report and the customer's Freshsales admin configures role-based access post-migration.

Tags applied to MiniCRM Cards for segmentation migrate to Freshsales Tag fields on the corresponding Contact or Account. We deduplicate tags during import to avoid carrying over messy taxonomy from the source system.

File attachments stored against MiniCRM Cards migrate where the platform exposes them via export. We flag any attachment size limits during scoping and handle file references to ensure records point to the correct attachments in the destination. Full file binary transfer depends on MiniCRM's export capability for the specific account.