Migrate from Data Team DDS to HighLevel

Direct one-to-one map. Every Data Team DDS contact record — name, email, phone, address, and all custom properties — lands as a HighLevel Contact with the same create date preserved as a custom field since HighLevel's native CreatedDate reflects migration time.

Direct one-to-one map. Data Team DDS company records transfer to HighLevel Companies. Company name, domain, address, industry, and any custom fields map to their HighLevel equivalents. Multi-contact companies in the source maintain the same association in HighLevel. If the source company record references a parent company, the parent-child relationship is preserved using HighLevel's company hierarchy feature.

Data Team DDS deals map to HighLevel Opportunities. Deal name, value, expected close date, owner, and pipeline stage all transfer. Stage names from the source are used to configure matching HighLevel pipeline stages before migration runs. If the source uses custom probability weights per stage, those values are stored as custom number fields on each stage in HighLevel's pipeline configuration.

Each pipeline stage in Data Team DDS becomes a stage in a HighLevel Pipeline. We create the pipeline structure first so stage mapping is clean at migration time. Probability weights transfer as stage-level metadata if they exist in the source.

Completed tasks, calls logged, and notes with timestamps migrate as HighLevel Tasks. Original due dates, completion dates, and assigned owners are preserved. Uncompleted tasks transfer with their original due dates and status flags. Call logs include duration and outcome metadata where available in the source system, mapped to HighLevel's task custom fields for call activity tracking.

Email records and text notes from Data Team DDS transfer as HighLevel Notes attached to the parent Contact, Company, or Opportunity record. Rich-text formatting is preserved where the source supports it. Notes that were created by automated workflows rather than manual entry are flagged in the migration report so your team can review their relevance in the new system.

Files attached to contacts, companies, or deals are downloaded from the source and re-uploaded to HighLevel Files, re-attached to their parent records. File size limits in HighLevel apply (standard limit 25MB per file). Files exceeding HighLevel's size limit are noted in the pre-migration audit and can be hosted externally with links stored in the appropriate record fields.

Any custom properties on contacts that have no direct HighLevel equivalent are created as custom fields on the Contact object before migration runs. Field type is matched as closely as possible: dropdowns become choice fields, text fields become text fields, etc.

Custom deal properties migrate as custom fields on HighLevel Opportunities. These are created in the destination before the migration batch runs so all values land in the correct fields during the load. Dropdown-style deal properties become HighLevel choice fields with the same picklist values, while numeric and date fields map to their corresponding HighLevel field types for proper sorting and reporting.

Data Team DDS custom objects map to HighLevel custom objects. Relationships between custom objects and standard objects (Contact, Company, Opportunity) require junction object setup in HighLevel — this is flagged in the pre-migration audit and delivered as a configuration plan.

Owner and user records from Data Team DDS are resolved by email match against HighLevel users. Unmatched owners are flagged before migration — records are assigned to a designated fallback owner or held for your team to create the user first.

Tags applied to contacts, companies, or deals in Data Team DDS transfer as HighLevel Tags. Tag names are preserved exactly; no value mapping is required since tags are string-based on both platforms. If your source uses a hierarchical tag taxonomy, the full tag hierarchy is preserved in HighLevel's tag structure so segmentation and filtering logic remains functional post-migration.