Migrate from Moskit to Salesforce Sales Cloud

Moskit Contact records map directly to Salesforce Contact. We extract all standard fields (name, email, phone, custom properties) and map them to typed Salesforce fields. A custom field moskit_contact_id__c stores the original Moskit record ID for audit reconciliation. The Brazilian Portuguese field labels are preserved as-is in the migration package with a Portuguese-to-English glossary provided separately.

Moskit Empresa records map to Salesforce Account. The Account's Name, Website, Industry, and Phone fields map directly. We use the Company record name as the dedupe key during import. Account is created before any Contact import so that the AccountId lookup on Contact is satisfied at insert time.

Moskit Deals map to Salesforce Opportunity. The dealstage property maps to Salesforce StageName, and the pipeline assignment maps to a Salesforce Record Type and Sales Process that we configure before migration. Deal monetary values map to Amount, close date maps to CloseDate, and owner assignment maps to OwnerId via the User email lookup.

Moskit Activities are a unified object for tasks, calls, meetings, and notes. We split them by activity type: tasks map to Salesforce Task with Status and Priority; calls map to Task with TaskSubtype=Call and disposition preserved in a custom field; meetings map to Salesforce Event with StartDateTime and EndDateTime; notes map to Salesforce Note linked via ContentDocumentLink. All activities retain their original timestamps for timeline ordering.

Moskit Projects are deal-centric and must be imported in a second pass after Deals. We create a Salesforce custom object Projeto__c with a lookup field linked_deal__c pointing to the Opportunity. During the first pass, we capture source deal IDs. During the second pass, we resolve each project's source deal ID to the corresponding destination Opportunity ID and inject it into linked_deal__c. This two-pass approach is required because Moskit Projects carry a mandatory deal reference that cannot be satisfied until the destination Opportunity exists.

Moskit allows custom fields on Contacts, Companies, Deals, and Activities. We extract the custom field definition per object by querying the schema individually (Moskit does not expose a bulk field-enumeration endpoint). Each custom field is created in Salesforce with the closest matching field type (text to Text, number to Number, date to Date, picklist to Picklist or Multi-Select Picklist). Field API names preserve the original Portuguese label slugified into a __c suffix.

Moskit User records (name, email, role) map to Salesforce User by email match. We export all users including inactive ones with an is_active__c flag set to false for the customer's admin to activate in Salesforce before the production migration. Owners referenced on Deals, Activities, and Projects are resolved via this User map before those objects are imported.

Moskit pipeline stages (custom-named with stage-order sequencing) map to Salesforce OpportunityStage values. We configure the destination stages in Salesforce Setup before migration, preserving stage order and any probability percentages set in Moskit. Stage-level win/loss probability migrates to StageProbability on each stage entry.

Moskit's WhatsApp Business sync stores conversation metadata (timestamps, participants, message count) linked to Contact records. The actual message content lives in WhatsApp infrastructure and cannot be extracted from Moskit. We import the metadata as Salesforce Tasks with a custom WhatsApp_conversation__c flag set to true, linked to the migrated Contact. Full message history is flagged as a separate data gap for the customer to address via WhatsApp data export tools.

Moskit attachments linked to Contacts, Companies, Deals, or Activities migrate as Salesforce ContentVersion records attached to the corresponding parent record via ContentDocumentLink. We extract the binary file data and re-upload it to Salesforce's Content workspace during migration, preserving file names and sizes. If Moskit stores attachments as URLs rather than binaries, we migrate the URL as a custom text field on the parent record.

Moskit Deals may include line-item product data. We map this to Salesforce OpportunityLineItem by resolving the Product2 reference and Pricebook2 entry at migration time. Quantity, unit price, and total amount migrate directly to the corresponding OpportunityLineItem fields.

Moskit tags and labels stored as multi-checkbox properties migrate to Salesforce multi-select picklist fields on the appropriate object. Tags used for segmentation migrate as-is; the customer chooses whether to convert tags to Salesforce Topics during scoping.