Migrate from Dr.DENTES to HighLevel

Dr.DENTES contact records map directly to HighLevel Contacts. The contact's primary company link becomes the HighLevel Contact's Company assignment. Email, phone, name, and address fields map field-for-field. Owner assignment resolves by email match against HighLevel user accounts. Any custom fields on the Dr.DENTES contact are recreated as custom fields on the HighLevel Contact object prior to migration.

Dr.DENTES company records map to HighLevel Companies. Company name, domain/website, industry, employee count, and annual revenue map to their HighLevel equivalents. Parent-company hierarchies in Dr.DENTES map to HighLevel's parent-company reference field. Address information, social profiles, and any custom company attributes are also transferred to maintain complete company records in HighLevel.

Dr.DENTES deal records map to HighLevel Opportunities. Deal name becomes Opportunity name, deal amount maps to Opportunity Value, and deal stage maps to the appropriate HighLevel pipeline stage. The deal's close date maps to the Opportunity's Close Date field. The deal's associated contacts and companies are linked via their migrated IDs to maintain relationship integrity in HighLevel.

Dr.DENTES pipeline definitions map to HighLevel Pipelines. Each Dr.DENTES pipeline becomes a HighLevel Pipeline with its own set of stages. Stage names and order are preserved; probability values can be reapplied based on your specification. Each stage can be assigned custom probabilities within HighLevel to match historical conversion rates from Dr.DENTES reporting.

Stage names map value-by-value from Dr.DENTES to HighLevel pipeline stages. Custom stage labels in Dr.DENTES are recreated as stage names in HighLevel. Stage-entry timestamps are preserved as custom datetime fields for historical reporting continuity. Custom pick-list values and their sort order are also migrated to ensure consistent data entry options in HighLevel.

Dr.DENTES contact custom fields that have no direct HighLevel equivalent are created as custom fields on the HighLevel Contact object. Field type is inferred from data (text, number, date, pick-list) and created via the HighLevel UI or Custom Objects API before migration.

Dr.DENTES deal custom fields migrate to HighLevel Opportunity custom fields. Priority flags, custom deal type labels, and any revenue-attributed fields get dedicated custom fields on the Opportunity object to preserve reporting granularity. These custom fields are created in HighLevel using the Custom Objects API or through the UI before the migration batch runs.

Dr.DENTES custom objects map 1:1 to HighLevel Custom Objects. Custom object schemas are analyzed and recreated in HighLevel with matching field definitions and relationship structures. HighLevel Custom Objects support junction objects for N:N relationships. Junction objects created in HighLevel enable many-to-many relationships between custom entities to mirror Dr.DENTES associations.

Dr.DENTES file attachments on contacts, companies, or deals are downloaded and re-uploaded to HighLevel Files. File size limits apply — HighLevel's default upload constraints are respected, and files exceeding limits are flagged for manual handling. Attachment metadata including original filenames and upload dates are preserved in HighLevel's file management system.

Dr.DENTES notes associated with contacts or deals migrate to HighLevel Notes attached to the corresponding Contact or Opportunity. Original timestamps and note authors are preserved. Rich-text formatting is converted to HighLevel's note format. Notes are associated with their parent records using the migrated record IDs to maintain the original contextual linkage.

Dr.DENTES task records, call logs, and meeting records map to HighLevel Tasks. Subject, description, due date, completion status, and owner are preserved. Call duration and meeting outcome notes are stored as custom fields on the migrated Task record. Task reminders and recurrence patterns from Dr.DENTES are translated to HighLevel Task reminders where the functionality exists.

Dr.DENTES automations and workflow rules do not migrate to HighLevel. We export your Dr.DENTES automation definitions as a structured reference document so your HighLevel admin can rebuild them in the Workflow Builder. The export captures trigger conditions, action sequences, and field-update logic.