Migrate from AddressTwo to HighLevel

AddressTwo Contacts migrate 1:1 to GoHighLevel Contacts. The contact's name, email, phone, and address fields map directly. Custom fields on the Contact migrate as GoHighLevel custom properties. We run a de-duplication pass on email addresses before import to catch any duplicate records that arose from AddressTwo's documented BCC sync gap.

AddressTwo stores company name and address as fields on the Contact record rather than a separate object. We extract these fields during the pre-migration transform, create a GoHighLevel Organization record for each distinct company value, and link the Contact to it via the Organization lookup. Contacts sharing the same company name in AddressTwo attach to the same GoHighLevel Organization.

AddressTwo Deals migrate to GoHighLevel Opportunities. The Deal name, value, close date, stage, and owner transfer directly. We map AddressTwo pipeline names to GoHighLevel pipeline names configured during setup, and Deal stages to GoHighLevel workflow stages matched per the customer's stage matrix.

Each AddressTwo Deal stage value becomes a GoHighLevel workflow stage. We match the stage names and order so that historical Deals retain their correct pipeline position. Stage probabilities migrate to GoHighLevel but do not control workflow routing in GoHighLevel the way they do in AddressTwo — we document this distinction for the customer's admin during handoff.

AddressTwo call activities migrate to GoHighLevel Contact Activities. Call duration, disposition, and timestamp preserve. Each call attaches to the migrated Contact record. The GoHighLevel API accepts activity entries per Contact with the activity type, date, and description fields populated from the AddressTwo export.

AddressTwo email activities from the BCC sync thread migrate as GoHighLevel Contact Activity entries with type email. The thread subject, participants, and body content transfer. The email timestamp and the associated Contact reference are preserved. Note that AddressTwo's BCC email sync stores threads as a flattened conversation log; we import them as-is without reconstructing individual message boundaries.

AddressTwo meeting activities migrate to GoHighLevel Contact Activities with type meeting. The meeting subject, date, duration, and any notes migrate as activity description. Attendees are not a structured object in AddressTwo, so we capture the meeting owner and the associated Contact only.

AddressTwo task activities migrate to GoHighLevel Contact Activities with type task. Task subject, due date, status (pending, completed), and assigned owner migrate. Completion timestamps preserve where available.

AddressTwo free-text Notes on Contacts migrate as GoHighLevel Contact Notes. The note content, author, and creation date transfer. Notes are not structured objects in AddressTwo so they carry no field-level mapping beyond the content text itself.

AddressTwo Contact tags migrate to GoHighLevel Tags as a flat array on each Contact. Tags are string identifiers and migrate directly without transformation. The customer decides during scoping whether to use GoHighLevel's built-in tagging or a separate custom field for additional segmentation.

AddressTwo campaign membership (which contacts received a mass email) migrates to GoHighLevel as a tag per campaign name plus a custom property tracking the most recent campaign membership date. Campaign analytics such as open rates and click rates do not export from AddressTwo and cannot be migrated. We document the campaign names and member lists so the customer can set up equivalent campaigns in GoHighLevel.

AddressTwo custom fields on Contacts migrate as GoHighLevel Contact custom properties of equivalent type. Text fields, number fields, date fields, and picklist fields map to their GoHighLevel equivalents. Any custom field without a clear GoHighLevel type maps to a text property and is flagged for customer review.