Migrate from SimplyConvert to Salesforce Sales Cloud

SimplyConvert cases map directly to Salesforce Case records. Each case's intake status, case type, referral source, and assigned attorney carry over as standard and custom fields on the Case object. Case numbers in SimplyConvert are preserved as an external ID field for traceability.

SimplyConvert contacts (prospective and signed clients) map to Salesforce Contact records. The Contact's name, email, phone, address, and primary case association migrate as Salesforce fields and lookups. Contacts without a company association land on a default Account record. If a contact has multiple case associations, each link is preserved as a separate Case Contact Role entry in Salesforce.

SimplyConvert users (intake staff, attorneys) are resolved by email match against Salesforce User records. Unmatched users are flagged before migration — the team either creates Salesforce User accounts first or assigns records to a designated fallback owner to prevent orphaned cases.

SimplyConvert files attached to cases are downloaded and re-uploaded to Salesforce Files as ContentVersion records, linked to the corresponding Case record via ContentDocumentLink. File size limits apply — files over 25 MB are chunked or flagged for manual re-upload by your team.

SimplyConvert tracks referral attribution (Google Ads, partner firm, organic) as a case property. Salesforce has no native referral-source field. We create a custom pick-list field (Referral_Source__c) on the Case object and map each value by name. Firms with free-form referral values may need a value-cleanse pass before migration.

SimplyConvert's qualification status (Qualified, Disqualified, Pending Review, Signed) has no direct Salesforce equivalent. We map it to a custom pick-list field (Intake_Status__c) on Case. If your firm uses Salesforce's native Case Status field for intake routing, FlitStack can map intake stages to custom Case Status values per record type instead.

SimplyConvert case types (Motor Vehicle Accident, Mass Tort, Medical Malpractice) migrate to a custom pick-list field (Practice_Area__c) on Case. Value-by-value mapping is required when the source pick-list values differ from Salesforce's standard Case Type field. If any values are missing or misspellings exist, FlitStack will flag them for correction before the migration load to avoid validation errors.

Salesforce's Case.CreatedDate is set at record creation time in Salesforce, not at the source creation time. Original SimplyConvert creation timestamps are preserved in a custom datetime field (Original_Created_Date__c) so historical intake reports show continuity. This allows reporting tools to generate accurate intake trends over time, even after the migration is complete.

SimplyConvert's case-assigned attorney or intake staff resolves to a Salesforce User by email match and populates Case.OwnerId. If a SimplyConvert user has no matching Salesforce User, the case is assigned to a pre-designated fallback owner and flagged in the migration report for manual re-assignment.

SimplyConvert's case activity history (intake call summaries, status-change notes) migrates as Salesforce Tasks with the Case as the parent. Original activity timestamps and staff names are preserved. Chatbot conversation logs are not migrated — those are rebuild artifacts for your Salesforce Flow intake logic.