Migrate your SimplyConvert data

Cases are the central object containing all claimant intake data, incident details, incident type, litigation reference, TDP score, and conversion status. The v2 API supports full CRUD at 2000 req/min and list retrieval at 300 req/min. We map SimplyConvert Cases 1:1 to the destination CRM's Matter or Case object, preserving trauma notes and TDP Quantifier values as custom fields.

SimplyConvert does not expose a standalone Contact or Client object; claimant details are embedded within the Case record. We extract these into a separate Contacts/Individuals object at the destination and create a link back to the Case. Any chatbot conversation history attached to the claimant is preserved as activity notes.

Document upload and download endpoints operate at 200 req/min per endpoint. We export all attached files linked to a Case—including claim forms, medical records, and correspondence—and recreate the same file-to-case associations at the destination, preserving original filenames and upload timestamps.

Referral sources are tracked per Case but the referral object is not a top-level entity in the API. We extract referral_source and referral_channel fields and map them to the destination's standard referral or utm_field schema, flagging Cases with missing referral attribution.

Bot conversations are stored as structured intake data linked to Cases but are not individually exported via API. We retrieve the conversation summary and key intake answers stored in Case custom fields and reproduce these as activity or engagement records at the destination.

SimplyConvert organizes Cases under named litigations such as Boy Scouts BSA, Camp Lejeune, or Allergan BIOCELL via an internal litigation_id. We carry this as a custom Litigation_Tag field on the destination Case object and advise customers to configure a matching picklist or segment in the destination CRM.

The TDP Quantifier is a trauma-informed scoring output stored as a Case custom field. We preserve the raw score and flag it in the destination as a read-only custom field since most destination CRMs do not have an equivalent concept. Scores are sourced from the Case GET endpoint in JSON form.

SimplyConvert user accounts and role assignments exist but the API does not expose a dedicated users endpoint. We extract assigned case owner and team member IDs from the Case record and attempt to match by email to destination user accounts, creating unmapped entries for staff without a destination match.

Law firms can define custom fields per litigation type stored within the Case object. We enumerate all custom field names and values from the Case GET response and create matching custom fields at the destination, applying the same field type (text, number, date, picklist) where supported.

Traffic source attribution (organic, referral link, paid ad) is captured during intake but not as a first-class object. We map the utm_source and utm_medium values into standard lead-source fields at the destination Contact, preserving the original capture context for marketing attribution.