Migrate from Sentian Solutions to HighLevel

Sentian's merged Client record requires Contact-Company disambiguation during migration

Sentian stores individual and organizational data in a single Client object — both a person's name and their company name can exist on the same record. HighLevel enforces separate Contact and Company objects with a required Contact-to-Company relationship for most features. We inspect Sentian Client records for non-empty organization_name fields and split those into HighLevel Company records before linking the Contact. Records where both individual and organizational data exist on the same Sentian Client record produce both a Contact and a Company in HighLevel. This disambiguation step adds validation overhead for high-volume client databases and must be reviewed in the sample migration phase before the full run.

Sentian's Matter-to-billing linkage requires a custom object strategy for firms with time-intensive matters

Sentian's Time Entries and Billing Records are linked to Matters through foreign keys. HighLevel has no native time-tracking or billing objects, so these records must land as custom fields or a Time_Entry__c custom object. Firms with matters that generate dozens of billable time entries per month face a decision: migrate each time entry as a separate Time_Entry__c record (maintains granular history but creates high record counts) or summarize billing totals as Opportunity custom fields (cleaner schema but loses per-entry detail). We surface this choice in the migration plan and apply the firm's preference before the full run. Either approach requires the Opportunity to exist first, so we sequence Time Entry migration after Opportunity creation.

HighLevel's API rate limit of 200,000 requests/day constrains bulk migration throughput

HighLevel API v2 enforces 200,000 requests per day per sub-account and 100 requests per 10 seconds. For migrations with over 50,000 records including custom objects and time entries, we batch API calls and pace writes to avoid hitting the daily limit. If your Sentian instance has dense matter histories (hundreds of time entries per matter), the total record count can exceed the daily limit and require a multi-day migration run with delta pickup on subsequent days. We estimate the total API call count before migration and notify you if a multi-day run is required. The delta-pickup window (24–48 hours) captures any Sentian changes made during the run.

Sentian workflow rules cannot migrate to HighLevel Workflow Builder

Sentian uses rule-based automation triggers scoped to matter lifecycle events (e.g., when a matter status changes to 'Closed Won', send a notification). HighLevel's Workflow Builder operates on a fundamentally different model — visual trigger-action flows with conditions, branches, and delay nodes. There is no automated conversion path between Sentian rules and HighLevel workflows. We export your Sentian rule definitions as a JSON reference file that documents each rule's trigger, conditions, and actions. Your HighLevel admin uses this as a rebuild guide. We do not attempt to migrate automation logic because any automated translation would produce non-functional workflows that your team would need to fix anyway.

HighLevel's flat-rate model eliminates Sentian's per-contact billing constructs

Sentian's pricing tiers charge per user and may have contact-count limits that create billing anxiety as client databases grow. HighLevel's flat-rate plans include unlimited contacts, which eliminates per-contact overage risk. However, usage-based services funded through HighLevel's Agency Wallet (SMS, phone calls, email validation, AI features, Workflow Premium Features) operate on a separate credit model that Sentian does not have. We document which Sentian-integrated services (e.g., SMS alerts, email confirmations) will need to be reconfigured as HighLevel Wallet-funded services post-migration. Your team decides whether to enable these features and funds the Agency Wallet accordingly.