Migrate from MiniCRM to Salesforce Sales Cloud

Cards are the primary record container in MiniCRM and hold contact details, custom fields, notes, and task associations. We resolve the Card-to-Lead-Contact split during scoping based on whether the Card is associated with an Interest (Deal). Cards with no linked Interest map to Salesforce Lead; Cards with a linked Interest map to Salesforce Contact tied to the matching Account. The split rule is documented in the scoping report and applied as the first transform. We preserve the original Card ID in a custom field minicrm_card_id__c on both Lead and Contact for audit and reconciliation.

Contact-level fields including name, email, phone, and address migrate directly to Salesforce Contact. We map MiniCRM contact fields to the corresponding Salesforce Contact standard fields. When a Contact originates from a Card with a linked Interest, we resolve the AccountId by first looking up the associated Company (Firma) or creating the Account inline during migration.

MiniCRM Company records map to Salesforce Account. The company name becomes Account.Name and is used as the dedupe key during import. We map available company fields to Account standard fields; custom company properties require explicit field-level mapping during scoping. Account is created before Contact import so that the AccountId lookup is satisfied at Contact insert time.

Deals in MiniCRM are called Interests and are associated with Cards. The Interest pipeline stage names map to Salesforce Stage values, and the pipeline assignment maps to a Salesforce Record Type and Sales Process that we configure before migration. Deal value, close date, and any custom Interest properties migrate to standard and custom Opportunity fields respectively.

MiniCRM's pipeline structures map to Salesforce Opportunity Record Types, each with its own Page Layout and Sales Process that scopes the available stage values. Stage probability percentages migrate from MiniCRM to Salesforce StageProbability, rounded to the nearest integer allowed by Salesforce.

MiniCRM Tasks linked to Cards migrate to Salesforce Task. Due date, status, assignee (resolved via owner email match to User), and description migrate directly. Task recurrence patterns and reminder settings require explicit mapping during scoping because they may not have direct Salesforce equivalents. We set Task.OwnerId by resolving the MiniCRM Pracownik (Worker) reference against the User mapping.

Free-text Notes attached to Cards migrate as Salesforce Note records linked via ContentDocumentLink to the parent Lead, Contact, Account, or Opportunity. We preserve the association to the parent Card record and set the note body as rich text where MiniCRM supports it. Note timestamps are preserved as Salesforce CreatedDate equivalents.

MiniCRM custom fields on Cards (added via Settings) include text, number, date, and choice types. We detect each custom field during scoping, map its type to the corresponding Salesforce field type (Text, Number, Date, Picklist), and pre-create the custom fields in Salesforce before migration. Choice fields require explicit value mapping to match the destination picklist values. Polish-language field labels are translated in coordination with the customer's team.

MiniCRM automation rules (trigger/action workflows tied to card status changes, field fills, and deadlines) are stored server-side and are not exposed through any documented export endpoint. We do not migrate them programmatically. During scoping, we document every active automation rule the customer has configured — including trigger, conditions, and actions — so they can rebuild them in Salesforce Flow. Revenue-impacting sequences (deal stage triggers, follow-up email actions) are prioritized in the inventory. This is explicitly a rebuild step, not a transfer.

MiniCRM User records include name, email, and role. We map Users to Salesforce User by email match. Role distinctions in MiniCRM may not map directly to Salesforce's permission model (profile and permission set assignments), so we assign a default Salesforce profile during migration and flag permission set requirements for the customer's admin. Users without a matching Salesforce User go to a reconciliation queue.

Calendar events and meeting records associated with Cards or Contacts migrate to Salesforce Event. Event title, start time, end time, and location transfer directly. Attendee lists may require supplemental mapping if MiniCRM stores attendee relationships separately; we link attendees via EventRelation records pointing at the matched Lead, Contact, and User records.

File attachments stored against Cards migrate where the MiniCRM export exposes them. We flag any attachment size limits during scoping and handle file references to ensure records point to the correct ContentVersion. If MiniCRM's export does not expose raw file content, we document the attachment gaps in the scoping report and recommend a manual attachment migration step using Salesforce Content or Files.

Tags applied to Cards for segmentation migrate as Salesforce custom multi-select picklist fields on the parent record. We deduplicate tags during import to avoid recreating a messy taxonomy in Salesforce. The customer chooses the target field (on Lead, Contact, or Account) during scoping based on their segmentation strategy.