Migrate from Fulcrum Snap to HighLevel

Fulcrum Snap contact records migrate directly to HighLevel Contacts. Each record receives its original create timestamp preserved as a custom datetime field since HighLevel's native Created Date is set at import time. Owner resolution happens by email match against HighLevel users.

Fulcrum Snap organizations and client companies map directly to HighLevel Companies. Company-level address, industry classification, and web-domain data migrate to corresponding HighLevel Company fields. Multi-address setups in Fulcrum Snap that include billing, shipping, and office locations collapse to a single primary address in HighLevel's Company model. Parent-subsidiary relationships are preserved where they exist as separate Company records in Fulcrum Snap.

Fulcrum Snap matters have no native HighLevel equivalent. We create a Matter custom object in HighLevel with fields for matter name, matter number, matter type, responsible attorney, open date, and status. Matter-to-contact linkage uses the custom object relationship schema available in HighLevel API 2.0.

Time entries carry billable hours, date, narrative, and activity type. We aggregate time entries by matter and migrate them as Notes on the associated Matter custom object in HighLevel, preserving original date, duration, and narrative text. Individual line-item hours become custom numeric fields for reporting purposes.

Fulcrum Snap invoices and LEDES-format billing records have no HighLevel equivalent — HighLevel does not support legal billing, trust accounting, or e-billing. We preserve invoice metadata (invoice number, amount, date, status) as custom fields on the Matter custom object. Actual billing must be handled by a separate legal billing tool post-migration.

Trust accounting and IOLTA records are financial instruments specific to legal compliance. HighLevel has no trust-accounting module and cannot receive these records. We export a full backup of trust data before migration and recommend preserving it in your accounting system of record. This is a business-level decision, not a technical limitation we override.

Fulcrum Snap conflict-check records are tied to SAP's access-control and matter-intake workflow. HighLevel does not have a conflicts module. Conflict checks must be re-run against HighLevel's contact database after migration, typically using a third-party conflicts tool or manual review before opening new matters.

Fulcrum Snap contact categorizations, segment tags, and classification labels migrate as HighLevel Tags attached to the corresponding Contact records. Tags function as flat labels in HighLevel's tagging system and do not support hierarchical nesting or parent-child relationships. Nested Fulcrum Snap category structures therefore collapse to the lowest applicable tag name during migration. Tag-to-contact associations and all existing tag assignments are fully preserved throughout the migration process.

Documents and file attachments linked to Fulcrum Snap contacts, companies, or matters are downloaded and re-uploaded to HighLevel's Files section. Files are re-associated with the corresponding HighLevel record (Contact, Company, or Matter custom object) after upload. Size limits per file apply based on HighLevel's upload constraints.

Fulcrum Snap staff records map to HighLevel Users by email address. Active Fulcrum Snap staff with login access become HighLevel users; read-only or archived staff are excluded from user creation but their contact records still migrate. Role and permission parity requires manual configuration in HighLevel since SAP role structures do not translate.

Fulcrum Snap calendar events associated with matters, contacts, or staff members migrate as HighLevel Appointments in the designated calendar. Original start times, end times, attendee lists including guest invitees, location information, and owner assignments are all preserved during migration. Recurring event series such as weekly check-ins or monthly status meetings are flattened into individual standalone appointments in HighLevel, with each occurrence maintaining its original date and time.

Fulcrum Snap custom fields and objects (e.g., practice area codes, billing arrangements, client hierarchy levels) map to HighLevel custom fields on the appropriate object or to HighLevel custom objects via API 2.0. Complex custom-object schemas with N:N relationships require junction-table configuration in HighLevel's relationship model.