Migrate from Maple CRM to Salesforce Sales Cloud

Maple CRM Lead records map directly to Salesforce Lead. Fields including source, status, assigned executive, follow-up dates, and custom intake data migrate to corresponding Salesforce Lead fields. We preserve any IRCC-jurisdiction-specific intake data in custom fields on the Lead object because the jurisdiction-specific labels and validations embedded in Maple's intake forms cannot be transferred; we document all intake field mappings during the discovery phase for manual reconfiguration if needed.

Maple CRM Clients hold contact details, address, nationality, passport data, and links to multiple open Cases. We split this into Salesforce Account (the organization or individual firm) and Contact (the primary person record). Passport data and nationality migrate to custom Contact fields. Client is treated as the parent entity and migrated before Cases to satisfy the AccountId and ContactId lookups on the custom Case__c object. A Client-to-Contact dedupe key is established using email address.

Maple CRM's core immigration Case object maps to a custom Case__c object that we provision in the destination Salesforce org. Process stages (Application, Review, Submission, Approval, Denial/Appeal) map to a Case__c stage picklist. A lookup field Case__c.Client__c links to the Contact record migrated from the Client object. Document attachments linked to the Case migrate separately as ContentDocument records and are linked back to Case__c via ContentDocumentLink.

Documents attached to Cases or Clients in Maple CRM (intake forms, passports, proof of funds, visa applications) migrate as Salesforce ContentDocument records. File binary blobs transfer as ContentVersion. Document type and upload date migrate as ContentVersion metadata fields. ContentDocumentLink records restore the relationship to the parent Case__c or Contact. We do not migrate folder permissions or sharing configurations; these are re-established post-migration in Salesforce sharing settings.

Maple CRM Agreement records (templates with macro placeholders pulled from Client and Case) render into generated agreement documents. The template definitions themselves are not fully exposed via Maple CRM API. We export all generated agreement records with their linked Client and Case data, and the agreement terms (service description, pricing, start and end dates, renewal clauses) map to Salesforce Contract fields. The customer rebuilds agreement templates as Salesforce Sales Agreements or a custom agreement template object post-migration.

Maple CRM Quotations map to Salesforce Quote, which is available from the Sales Cloud Professional tier. Quotation line items migrate to QuoteLineItem with PricebookEntry and Product2 references resolved at migration time. Quotation status (Draft, Sent, Accepted, Rejected) maps to Salesforce QuoteStatus. The quotation PDF is not migrated; only the underlying data record transfers.

Maple CRM Invoice records (line items, amounts, payment terms, outstanding balance, instalment schedules) map to Salesforce Invoice if the destination org includes Salesforce Billing or to custom Invoice__c fields if Billing is not licensed. Historical paid and outstanding invoices migrate with full line-item fidelity. Payment status (Paid, Partial, Overdue) migrates as invoice status fields. Instalment schedules migrate as related custom Invoice_Installment__c records.

Annual Maintenance Contracts in Maple CRM track service terms, renewal dates, and pricing against a Client record. We map these to Salesforce Contract with ContractTerm, StartDate, EndDate, and renewal-related custom fields. Renewal scheduling is mapped to Salesforce's built-in contract renewal alerts, which the customer's admin configures post-migration. Active renewal dates are preserved as field data.

Service Schedules in Maple CRM track field service appointments, technician assignments, and turnaround time. These map to Salesforce Field Service Mobile objects (ServiceAppointment, AssignedResource, WorkOrder) if the destination org includes Field Service. If Field Service is not licensed, Service Schedules map to custom Service_Schedule__c records with the customer's admin configuring the FSM rollout as a separate implementation phase.

Maple CRM Support Request records (status, priority, assignee, timestamps) migrate to Salesforce Case. TAT (Turnaround Time) and SLA escalation rules are platform configurations that have no API export path and must be reconstructed as Salesforce Entitlement Processes and Milestones in Service Cloud. We migrate the Support Request records but the SLA and escalation logic requires post-migration configuration by an admin familiar with Salesforce Service Cloud entitlements.

Maple CRM automation rules (stage-change triggers, email notifications, follow-up reminders, approval chains) are platform configuration not accessible via public API. We do not migrate them. We deliver a written inventory of every active automation during discovery that documents the trigger, conditions, actions, and recommended Salesforce Flow equivalent. The customer's admin or a Salesforce partner rebuilds each automation in Salesforce Flow post-migration. Rebuild time varies from 30 minutes per simple rule to 2 hours per complex multi-step workflow.

Maple CRM user accounts with role-based access control migrate to Salesforce User records. We export user records with role and team assignments. Staff records with HR data such as compensation or PTO are not stored in Maple CRM's CRM layer and therefore are not part of the migration scope. We match Maple CRM users to Salesforce Users by email address. Any Maple CRM user without a matching Salesforce User is placed in a reconciliation queue for the admin to provision before record import proceeds.

Intake form responses for Canada and other IRCC-relevant jurisdictions embed jurisdiction-specific field structures in Maple CRM. When migrating to Salesforce, these fields map to custom properties on the Lead object. The jurisdiction-specific labels and validations are not preserved; we document all intake form field mappings during discovery so the customer's admin can reconfigure them in Salesforce. Any form responses linked to existing Clients migrate to the corresponding Contact record.