Migrate from Paradym to HighLevel

Paradym contacts map directly to HighLevel contacts. The Paradym contact ID is stored as a custom field (paradym_contact_id__c) for traceability and delta-run de-duplication. Owner resolution happens via email match against HighLevel users. If a Paradym owner email has no corresponding HighLevel user, the record is flagged in a pre-flight report for admin review before migration commits. All standard contact fields transfer with their original values preserved.

Paradym company records map to HighLevel companies. If a Paradym contact has no primary company, we create a placeholder company record and link it via the contact's Company field. Parent-company hierarchies in Paradym map to the HighLevel Company ParentId relationship.

Paradym deals migrate as HighLevel opportunities. The deal name becomes the opportunity name, amount maps directly to the value field, and the deal stage maps to the corresponding HighLevel pipeline stage identifier. We preserve the original close date, probability percentage, and owner assignment as opportunity fields. The Paradym deal ID is stored in a custom field (paradym_deal_id__c) for reconciliation traceability after migration completes.

Paradym pipelines become HighLevel pipelines with configurable stages. Each Paradym pipeline's stage names are mapped value-by-value to the equivalent HighLevel pipeline stage. If a Paradym pipeline contains stages that do not exist in the target HighLevel pipeline, we create those stages before migration data loads. The stage mapping table is delivered as part of the migration plan so your admin can verify the configuration before the bulk import runs.

Paradym tags migrate as HighLevel tags attached to contact records. The full tag taxonomy from Paradym is preserved as a reference CSV in the migration documentation. Tags that exceed HighLevel's 100-character limit are truncated to the first 100 characters. Tag category hierarchies (parent-child groupings) are not supported in HighLevel and are exported as a flat list. Your admin can use the reference CSV to rebuild Smart Lists and automation triggers based on the migrated tags.

Paradym contact properties that are not standard HighLevel fields require custom field creation in HighLevel before migration data loads. We deliver a custom field creation plan listing field names, data types, and pick-list values for your HighLevel admin to create.

Paradym company custom fields map to HighLevel company custom properties. Fields with date, number, or pick-list types require type-aware mapping against HighLevel's schema. Multi-select pick-list fields in Paradym become comma-delimited strings in HighLevel. The field mapping plan identifies each custom property, its target data type, and any truncation or formatting rules applied during transformation. We deliver this as a pre-migration checklist for your HighLevel admin to execute before the bulk import begins.

Paradym credential templates — structured JSON documents with nested attributes for SD-JWT VCs — have no native equivalent in HighLevel. We export the full template payload as JSON and store it as an attachment on the related contact record. Rebuilt credential issuance must use HighLevel's Custom Objects API and Workflow Builder.

Paradym users are matched to HighLevel users by email address. Unmatched users are flagged before migration runs and assigned to a designated fallback owner. If a Paradym owner account has been deactivated, all records owned by that user are reassigned to the fallback owner. Owner resolution is verified in a pre-flight report before the bulk load commits, ensuring no records land in HighLevel without an assigned user.

Files attached to Paradym contacts or deals are downloaded from Paradym's storage and re-uploaded to HighLevel's file storage system. The original file URL from Paradym is preserved in a custom field on the target record for reference. File size limits apply per HighLevel's upload constraints, and files exceeding those limits are flagged for manual handling.

Paradym notes migrate to HighLevel notes attached to the corresponding contact or company record. Original create timestamps and author attribution are preserved during migration. Rich-text formatting in Paradym notes is converted to HighLevel's supported note format. Notes without an associated contact or company are linked to a fallback record and flagged in the migration audit log for admin review.

Paradym activity records — calls, emails, meetings — migrate as HighLevel activities attached to the contact record. Call disposition codes, duration in seconds, and outcome fields map to custom properties on the activity record. Original activity timestamps are preserved to maintain reporting continuity in HighLevel's activity history. Email and meeting activities include subject, body, and attendee data as available in the Paradym export.