Migrate from Spiro to HighLevel

Spiro Companies map to GHL Locations attached to Contact records. The Spiro Company name becomes the Location name, and the primary address fields (street, city, state, zip, country) map to the Location address fields. For organizations without a Location relationship preference, Company name can alternatively be stored in a custom Contact field (e.g., Organization__c) for simpler data models. We extract the full Company address schema during Spiro field definition export and recreate Location fields in GHL before import.

Spiro Contacts migrate directly to GHL Contacts with standard field mapping: first name, last name, email, phone, title, and website. Custom Contact fields from Spiro are recreated as GHL Contact custom fields before migration. Email address serves as the primary dedupe key; we flag any duplicate email addresses found across Spiro Contacts during scoping so the customer can resolve before import begins.

Spiro Opportunities map to GHL Opportunities with deal name, value (amount), close date, and stage mapping. Spiro stage names are mapped to GHL pipeline stage values during scoping; we configure the GHL pipeline and stage definitions before migration so that the stage mapping is valid at insert time. The Opportunity owner (Spiro user) resolves to the matching GHL user by email.

Spiro Company custom fields are recreated as GHL Location custom fields. Text, number, date, and picklist field types map directly; multi-select picklist from Spiro maps to GHL multi-select fields. We extract the full Spiro custom field definition inventory from the UI (requires Spiro CSM coordination if not accessible) and pre-create all Location custom fields in GHL before any Company data is imported.

Spiro Contact custom fields map to GHL Contact custom fields using equivalent data types. We extract the field definitions from Spiro's schema and recreate them in GHL's Contact custom fields section before importing Contact records. Custom field labels and API names are preserved where possible to minimize downstream mapping confusion.

Spiro Opportunity custom fields map to GHL Opportunity custom fields. Note that GHL treats Contact custom fields and Opportunity custom fields as distinct field types with separate UI sections and different API namespaces; Opportunity custom fields cannot be accessed from the Contact record. We configure all Opportunity custom fields in GHL before importing any Opportunities.

Spiro email engagements (logged when the email integration is connected) migrate to GHL Contact activity entries on the timeline. Each email engagement becomes a dated activity entry with subject, body preview, and direction (sent/received). We warn customers that Spiro email disconnects silently mean any emails sent during a disconnection window were never logged and cannot be backfilled; we verify email sync status during scoping and recommend exporting any manually-saved email logs before the migration window.

Spiro call engagements map to GHL Contact activity entries of type call. Duration, call direction, and disposition notes migrate to the activity entry. We preserve the original call timestamp as the activity date to maintain the chronological timeline in GHL.

Spiro meeting engagements map to GHL Contact activity entries of type appointment or meeting. Start time, duration, location (if applicable), and meeting title migrate as the activity entry. Attendee information from Spiro meeting records is stored in the activity notes field in GHL.

Spiro Notes linked to Contacts or Companies migrate as Notes attached to the corresponding GHL Contact or Opportunity. We resolve the parent record (Contact or Opportunity) at migration time and create the Note with the original creation timestamp preserved. Notes attached to Spiro Companies map to Notes on the related GHL Contact if a 1:1 Company-to-Location mapping exists.

Spiro user records map to GHL user accounts by email address. We extract all distinct owner references from Spiro records (Contacts, Companies, Opportunities, Engagements) and attempt to match each by email against GHL's user table. Unmatched owners go to a reconciliation queue; the customer provisions GHL user accounts for any Spiro users without existing GHL access before migration resumes. Inactive Spiro users are flagged separately for the customer's decision on whether to create inactive GHL accounts to preserve activity attribution.

Spiro stores attachments as linked file URLs rather than embedded files. During migration, we verify each Spiro attachment URL is reachable, download critical files to a temporary location, and re-upload them to GHL's native file storage where possible. If the Spiro workspace access is revoked post-migration, original attachment URLs will break; we flag this risk during discovery and recommend downloading all critical files before the migration window closes. Re-uploaded files in GHL are linked to the corresponding Contact or Opportunity record.