Migrate from Centerbase to HighLevel

Centerbase clients map directly to HighLevel contacts. We preserve the client name, email address, phone number, and primary address. Client records that have no associated matter become plain contacts; clients with matter history retain their matter references as custom fields on the contact record.

Centerbase matters (cases) translate to HighLevel opportunities. Each matter becomes an opportunity linked to the client (now contact) who opened it. The opportunity name uses the matter title, and the pipeline stage is assigned based on matter status — active matters become open pipeline stages, closed matters become closed won or lost depending on outcome.

Matter-level custom fields such as case type, practice area, court venue, and opposing counsel translate to opportunity custom fields in HighLevel. During schema setup, FlitStack creates these custom fields on the opportunity object with appropriate field types matching the source data format. Values are then mapped record-by-record during the migration load phase to ensure each opportunity inherits the complete legal context from its originating Centerbase matter record.

Client-level custom fields including billing rate tier, referral source, and preferred contact method are migrated as contact custom fields in HighLevel. These fields are created as contact custom fields so they appear directly on the contact record and are accessible for contact-level workflow triggers and segmentation. The field types are preserved during migration — pick-list values become pick-list fields, text fields remain text fields, and date fields retain their date format to maintain data integrity across systems.

Billable time entries, expenses, and invoice line items from Centerbase are translated to opportunity amount fields and note records on the linked opportunity. Total billed amount maps to the opportunity Amount field; individual line-item details are stored as notes for reference. We do not create invoices in HighLevel since HighLevel lacks a billing module.

Documents attached to Centerbase clients and matters are re-uploaded to the corresponding contact or opportunity record in HighLevel as file attachments. File size limits apply per HighLevel's storage model — large documents over 25MB are flagged before migration so your team can decide whether to compress or store externally.

Centerbase staff records are matched to HighLevel users by email address. Unmatched staff (former employees in Centerbase with no HighLevel account) are flagged — their records can be assigned to a fallback owner or migrated as inactive contacts. Active staff with existing HighLevel accounts receive their records automatically.

Centerbase automated workflows, matter workflow stages, and task templates do not migrate. They must be rebuilt in HighLevel's workflow builder. FlitStack exports the workflow definitions as a reference document that your HighLevel admin can use to reconstruct the automation logic in HighLevel's trigger-action model.

Centerbase billing rate schedules, LEDES billing codes, and billing templates are configuration data that has no direct equivalent in HighLevel. These are exported as reference data and must be recreated manually as opportunity custom fields or external documents for billing reference.

Centerbase custom reports and report writer configurations do not migrate. The underlying data (clients, matters, billing entries) migrates to HighLevel, but report definitions must be rebuilt in HighLevel's reporting interface. We document which Centerbase reports map to which HighLevel opportunity and contact fields for reference.

Centerbase calendar entries and appointments linked to matters are translated to contact activities in HighLevel. Each appointment becomes a task or note on the associated contact record. FlitStack preserves the original appointment date, time, duration, and description as structured fields in the task so that historical appointment data remains searchable and actionable in HighLevel's activity timeline for follow-up scheduling and client communication tracking.

Centerbase lookup fields that link matters to related clients or related matters become custom fields or association notes in HighLevel. Where the lookup points to a single related record, we create a custom text field storing the related record identifier. For N:1 or N:N relationships, we create a note on the parent record documenting the relationship.