Migrate from eBrief Ready to HubSpot

eBrief Ready matters map 1:1 to HubSpot deals (opportunities). The matter name becomes the deal name, and the matter status (Active, Closed Won, Closed Lost) maps to HubSpot deal stage values. Matter create dates are preserved as a custom datetime field since HubSpot's Deal Created Date is set at migration time.

When a firm uses eBrief Ready for non-legal case data (client intake, project tracking), the matter maps to a HubSpot custom object (eBrief_Matter__c) so it does not pollute the sales pipeline. Custom object associations to contacts and companies use HubSpot's association-labels feature.

eBrief Ready party records (with name, email, phone, role) map to HubSpot contacts. The party role (Barrister, Instructing Solicitor, Expert Witness, Client) migrates as a custom pick-list property (Party_Role__c) on the HubSpot contact record. Party create date is preserved as Original_Create_Date__c.

eBrief Ready parties that are firms or organisations (with firm name, ABN/ACN, address) map to HubSpot companies. ABN/ACN numbers are stored as a custom text field (Legal_Registration_ID__c) on the HubSpot company record for Australian compliance reference. These fields enable Australian legal compliance verification and cross-referencing of business entities during due diligence.

eBrief Ready documents and eBrief bundles are downloaded and re-uploaded to HubSpot Files, attached to the corresponding deal record. Document metadata (original filename, upload date, page count, tags) is stored as custom properties on the HubSpot file record or as deal custom properties. HubSpot file size limit (250 MB per file) may require splitting large bundles.

eBrief Ready annotations (highlighted text, comments, tags) export as HubSpot notes on the relevant contact or deal. Annotations include the original document reference, page number, and annotation date so they map correctly to the document in HubSpot Files. Each annotation retains a link to its source file, allowing users in HubSpot to navigate back to the original document for reference.

eBrief Ready billing records (invoice number, fee amount, billing status) have no native HubSpot equivalent. We create HubSpot deal custom properties — Billable_Fee__c (currency), Invoice_Number__c (text), Billing_Status__c (pick-list: Unbilled, Invoiced, Paid) — to preserve the financial record within the deal context.

Court name, jurisdiction, and applicable court rules are stored as HubSpot deal custom text fields (Court_Name__c, Jurisdiction__c, Court_Rules__c). HubSpot has no native court or jurisdiction field, so this data is preserved as reference metadata for legal operations teams. This metadata supports jurisdictional reporting and helps legal operations track which courts are involved across the deal pipeline.

eBrief Ready chronology tool entries (date, event description, document reference) have no direct HubSpot equivalent. We map them as a HubSpot deal custom property (Chronology_Events__c, long-text or JSON array) so the chronological event history is attached to the deal record without creating a separate object.

eBrief Ready matter owners are resolved by email match against HubSpot users. If a HubSpot user with the matching email does not exist, the matter is assigned to a fallback owner and the original owner email is stored as Original_Owner_Email__c for manual reassignment.

eBrief Ready Smart Classification tags (document category, document type, subject-matter labels) are stored as HubSpot deal multi-select custom properties (Document_Tags__c, Subject_Matter__c) using HubSpot's multi-checkbox field type. These tags can be used in HubSpot reporting to filter deals by document type and subject area, providing insight into matter composition and resource allocation.

eBrief Ready client portal access records have no HubSpot equivalent. We preserve the portal access status as a custom contact property (Client_Portal_Access__c, boolean) and recommend rebuilding any client-facing sharing in HubSpot's member portal feature separately. Post-migration, the firm's HubSpot administrator can configure member portal access groups based on the exported contact property to replicate the original sharing model.