Migrate from MiniCRM to Zoho CRM

MiniCRM Cards are the primary record container holding contact details, deal associations, and custom fields. We split Cards into Zoho Leads and Contacts based on the Card's status and lifecycle stage: unqualified Cards with no associated deal map to Zoho Lead, and Cards linked to an active deal or marked as customer map to Zoho Contact tied to an Account. The original MiniCRM Card ID is preserved in a custom field minicrm_card_id__c on both Lead and Contact for audit and reconciliation.

MiniCRM Contact-level fields including name, email, phone, and address map directly to Zoho Contact. These fields are well-structured in MiniCRM and migrate cleanly. Email maps to Email field, phone maps to Phone, and address fields map to the corresponding Zoho mailing address fields. We deduplicate by email during import to prevent duplicate Contact records.

MiniCRM Company records map to Zoho Account. The company name maps to Account Name, and available address and industry fields map to their Zoho equivalents. Companies are created before Contact import so that Account lookup is satisfied at the moment of Contact insert. Any custom company properties require explicit field-level mapping during scoping, as MiniCRM companies may have fewer normalized fields than Zoho's Account schema.

MiniCRM Deals (called Interests) map to Zoho Deals. The deal name, value, and stage status map to Zoho Deal Name, Amount, and Stage respectively. Pipeline stage names in MiniCRM require explicit mapping to Zoho's Deal Stage values, which we configure before migration. The MiniCRM Card-to-Deal association is preserved through the Contact lookup on the Deal record.

MiniCRM Tasks map to Zoho Tasks. Due date, status, assignee, and description migrate directly. Task recurrence patterns and reminder settings require explicit mapping because they may not have a direct Zoho equivalent; we document any recurrence rules during scoping so the customer's admin can configure these in Zoho after migration. Owner assignment resolves via email match against Zoho Users.

Free-text notes attached to MiniCRM Cards migrate to Zoho Notes linked via ContentDocumentLink to the parent record (Lead, Contact, or Deal). Note body migrates as-is, and Polish-language labels are preserved with a reference note flag for the customer's admin to review. We deduplicate notes with identical timestamps and content to avoid recreating noisy histories.

MiniCRM custom fields on Cards are detected during scoping, and field types (text, number, date, choice) are mapped to their Zoho custom field equivalents. Choice fields require value mapping to match the Zoho picklist values. Custom fields are created in Zoho before data import begins. Note: Custom fields are not available in Zoho CRM's Free edition; if the customer is on a paid Zoho tier, we provision the fields before migration.

MiniCRM user records include name, email, and role. We map these to Zoho Users by email match. Role distinctions in MiniCRM may not map directly to Zoho's permission model, so we document role mappings during scoping for the customer's admin to configure post-migration. Any MiniCRM user without a matching Zoho User is held in a reconciliation queue until the admin provisions the account.

Calendar events and meeting records associated with Cards migrate to Zoho Events. Event title, start datetime, end datetime, and location map directly. Full attendee lists and calendar-specific metadata (recurrence, reminders) require supplemental mapping; we document these during scoping. Event relations link to the migrated Contact or Lead records.

File attachments stored against MiniCRM Cards migrate as Zoho Attachments where the MiniCRM export exposes them. We flag any attachment size limits during scoping and handle references to ensure records point to the correct files. If MiniCRM does not expose attachments via export, we document which records have attachment references so the customer can manually transfer files post-migration.

Tags applied to MiniCRM Cards for segmentation migrate as Zoho Tags. We deduplicate tags during import to avoid recreating messy taxonomy in the new system. Tag values that exceed Zoho's tag character limit are truncated with a note in the migration report. If tags represent a critical segmentation strategy, we recommend reviewing the Zoho tag taxonomy post-migration to ensure the customer is not duplicating a complex label structure that should be rebuilt as Zoho's more structured approach to categorization.

MiniCRM automation rules (trigger/action workflows tied to card status changes, field fills, and deadlines) do not export via API. We document every active automation rule during discovery, capturing trigger type, conditions, actions, and associated Card types. This documentation serves as the specification for rebuilding each rule in Zoho Blueprint or as a workflow rule. We prioritize documenting revenue-impacting sequences (deal stage triggers, follow-up assignments) first. This is a documentation-only step; no automation logic migrates as code.