Migrate from SimplyConvert to HighLevel

SimplyConvert contacts map directly to HighLevel contacts. All standard fields — name, email, phone, address — transfer 1:1. Owner assignment resolves by email match against HighLevel users. Contacts with multiple case associations in SimplyConvert surface as multiple tag entries in HighLevel.

SimplyConvert's Case object is the core record for intake. It translates to a HighLevel Opportunity linked to the contact's pipeline. Case status (New, Qualified, Signed, Closed) maps to a HighLevel pipeline stage. Case value and settlement estimate migrate as custom monetary fields on the opportunity.

SimplyConvert tracks referral source (Attorney Referral, Media, Partner Firm, etc.) per case. This merges into two HighLevel constructs: a referral-source tag on the contact record plus a custom field (Referral_Source__c) storing the specific source value at time of intake. The dual-field approach preserves both the source categorization for reporting and the granular source detail for audit purposes.

SimplyConvert company records map to HighLevel companies. Company name, domain, industry, and address fields transfer directly. Multi-contact companies in SimplyConvert preserve the same contact count in HighLevel companies. All company-to-contact relationships are maintained during migration, ensuring organizational hierarchies remain intact.

SimplyConvert stores document references and attachments against case records. FlitStack re-uploads these files to HighLevel's attachment model linked to the corresponding contact or opportunity. File size limits (25MB per file in HighLevel) are respected during re-upload. Files exceeding the limit are flagged and routed to external storage with URL references maintained in the destination record.

SimplyConvert's Boy Scout TDP Quantifier score is a numeric value specific to mass-tort intake. HighLevel has no native equivalent. We create a custom number field on the Contact object and migrate the score value directly. Firms should verify whether TDP scoring logic needs to be replicated as a workflow formula in HighLevel.

SimplyConvert's trauma-informed client outreach flag marks contacts requiring specialized intake handling. We migrate this as a custom checkbox field on the Contact. The corresponding intake workflow logic must be rebuilt in HighLevel's workflow builder. This ensures trauma-informed clients are properly flagged for specialized handling after migration.

SimplyConvert's claim_type custom field (BSA Litigation, Camp Lejeune, Texas Freeze, etc.) maps to a HighLevel custom pick-list with the same values preserved. If SimplyConvert has custom claim types beyond the standard set, those are added to the pick-list before migration runs.

SimplyConvert user records (attorney, intake specialist, paralegal) map to HighLevel users by email address. Unmatched users are flagged before migration — the firm either invites them to HighLevel first or assigns their records to a fallback owner. This prevents orphaned records and ensures accountability for all migrated data.

SimplyConvert's referral platform tracks referring partners as separate entities. In HighLevel, these become contacts tagged with a Referral_Partner role. Their referral performance is tracked via tag-based reporting rather than a dedicated referral object. Tag-based attribution allows for flexible reporting across multiple referral dimensions.

SimplyConvert pre-built law-firm dashboards (case volume, intake conversion, settlement tracking) have no direct equivalent in HighLevel. The underlying data migrates, but dashboards must be rebuilt using HighLevel's reporting tools after go-live. FlitStack provides dashboard mapping documentation that identifies the source metrics and recommended HighLevel equivalents for reconstruction.

SimplyConvert's automated client intake bots, trauma-informed outreach sequences, and chatbot logic exist only within SimplyConvert's automation engine. These must be redesigned and rebuilt in HighLevel's workflow builder. FlitStack exports the workflow definitions as documentation for the rebuild. This export serves as a functional specification for recreating automation logic in HighLevel.