Migrate from HighQ to Salesforce Sales Cloud

HighQ Sites representing client organizations map to Salesforce Accounts. Site name becomes Account.Name. FlitStack resolves whether the site functions as a client Account or an internal workspace — internal workspaces may map to a designated 'Internal' Account or remain unmapped based on your specification.

When a HighQ Site contains project-level data rather than account-level data, it migrates as a custom Site__c object with a lookup to Account. This approach preserves site-specific metadata and file attachments while maintaining the Salesforce CRM relationship structure. The custom object also inherits standard Salesforce features such as reports, dashboards, and sharing settings.

Each HighQ iSheet becomes a Salesforce custom object. The sheet name becomes the custom object label; the API-safe name uses the __c suffix. Column definitions (text, number, date, picklist, user) translate to Salesforce field types — picklist columns require value-by-value mapping if source uses custom picklist values.

iSheet columns referencing another sheet translate to Salesforce lookup fields. The migration identifies cross-sheet references from HighQ's API metadata and creates corresponding lookup fields on the destination custom object, ensuring referential integrity when both sheets migrate. This also allows for efficient querying of related records across sheets.

HighQ Tasks map directly to Salesforce Tasks. Task subject, description, due date, status, and priority translate to Subject, Description, ActivityDate, Status, and Priority fields. Original HighQ create and modify timestamps are preserved in custom datetime fields for audit continuity. This ensures complete historical tracking for compliance reviews.

HighQ file attachments re-upload to Salesforce Files (ContentDocument + ContentVersion). File name, description, and version history transfer. The parent record link connects the file to the migrated Account or custom object. Salesforce's 25MB per-file limit applies — files exceeding this are flagged for manual chunking before migration.

HighQ user email addresses are matched against Salesforce User records by email. Matched users become the OwnerId on migrated records. Unmatched users are flagged in a pre-migration report — your team either creates Salesforce User accounts for them or assigns their records to a fallback owner before the migration runs.

HighQ discussion threads map to Salesforce Chatter FeedItems on the parent record. Text content, author, and timestamp migrate. Rich-text formatting may simplify during translation — long-threaded discussions are bundled into a single FeedItem with the full thread text to avoid excessive Chatter post counts.

HighQ workflow definitions export as JSON reference files for your Salesforce admin to rebuild in Flow. FlitStack does not migrate logic — the export includes rule triggers, conditions, and actions in a structured format that maps to Flow Builder elements.

HighQ client portal permissions and site-level access controls have no direct Salesforce equivalent. These must be rebuilt using Salesforce Sharing Rules, Account Teams, or Experience Cloud site roles. FlitStack documents the HighQ permission structure as a reference for your admin.