Migrate from Podio to HighLevel

Podio apps used as contact registries map directly to GoHighLevel Contact records. The app's Name field maps to firstName and lastName (we split on first-space if a single field); Email maps to email; Phone maps to phone; Company maps to companyName (which becomes Account name and triggers Account creation). Status category fields map to a custom multi-select field preserving the original option labels. The destination Contact custom fields are created during schema design before migration begins.

Podio apps with company fields (name, website, address, industry) map to GoHighLevel Account records. The app item name becomes Account name; website maps to website; address fields map to GoHighLevel's address compound field. Account is created before Contact migration so that AccountId is resolved at Contact insert time.

Podio apps used to track deals, projects, or sales pipelines map to GoHighLevel Opportunity records. The app item name becomes Opportunity name; numeric fields for deal value map to opportunity value; stage category fields map to pipeline stages. Client reference fields linking to a Contact app become ContactId lookups on Opportunity. GoHighLevel requires a Pipeline and Stage to be configured before Opportunity import.

Podio Tasks map directly to GoHighLevel Task records. Task title maps to subject; due date maps to date; assignee maps to assignedTo (resolved by email against GoHighLevel User); completion status maps to status; linked item references are preserved as notes text on the Task. Recurring task rules are documented as a text specification for manual recreation in GoHighLevel.

GoHighLevel enforces a strict distinction between Contact custom fields (attached to the person record) and Opportunity custom fields (attached to the deal record). Once created, the field type cannot be switched. During schema design we examine each Podio app field's semantic purpose to determine whether it belongs on Contact or Opportunity. Fields that apply to the person regardless of deal context (birthday, preferred contact method, referral source) become Contact custom fields. Fields that apply only to a specific deal (budget, timeline, property type) become Opportunity custom fields.

Podio reference fields create explicit links between items in different apps (similar to foreign keys). GoHighLevel supports lookup relationships on Contact and Opportunity. We capture all reference field values during Podio export, identify the target app and item, resolve the target record's new GoHighLevel ID during migration, and write the lookup field. Where the reference chain is too complex for direct lookup (cross-workspace references, circular links), we write the original reference as a text field for manual verification.

Podio Comments attach to items, tasks, files, and other objects. We migrate comment text, author, and timestamp to GoHighLevel Note records linked via ContentDocumentLink to the parent Contact, Account, or Opportunity. Rich-text formatting is simplified to plain text. Note timestamps are preserved by setting the Note's createdDate.

Podio file attachments are downloaded to our staging storage and re-uploaded to GoHighLevel using the GoHighLevel file upload API, then attached to the correct parent record by ID. Podio's 100MB per-file limit is respected; GoHighLevel's 10GB per-account storage on Starter accommodates most migrations. We preserve original filenames and attach dates.

Podio status messages are lightweight social-style posts within a workspace or space. GoHighLevel has no direct equivalent. We treat status messages as Notes or Activity Log entries attached to the relevant Contact or Opportunity, preserving the post text, author, and timestamp.

Tags applied to Podio items, tasks, and other objects map to GoHighLevel Tag records. Multi-value tags on a single Podio item become multiple Tag assignments in GoHighLevel. We use GoHighLevel's tag API to create tags on the target Contact or Opportunity record during import.