Estateably Compatibility Guide

Overview#

Estateably ↗ is a probate-focused estate administration platform that automates the preparation of court forms, executor task management, and estate accounting across the United States, Canada, and the United Kingdom. It serves estate attorneys, trust companies, and professional executors — providing structured workflows from the moment a death is reported through to final distribution and estate closure.

Estateably’s data model is built around the core entities of probate administration: the deceased, executors, beneficiaries, assets, liabilities, and distributions. It maintains a library of over 3,000 court forms across US, Canadian, and UK jurisdictions, each requiring structured estate data to populate. This probate-centric architecture makes Estateably one of the closest natural fits for INHERIT adoption — its internal entities map almost directly to INHERIT’s core schemas with minimal transformation.

Why INHERIT Matters for Estateably#

Who Uses Estateably#

• Estate attorneys managing probate filings across US and Canadian jurisdictions
• Trust companies administering estates at scale with professional executor obligations
• Probate solicitors in England and Wales handling grant applications, IHT submissions, and estate accounts
• Bank trust departments processing estate distributions and fiduciary accounting

Known Integration Surface#

Estateably has a confirmed internal API (evidenced by its partnership with SideDrawer, which enables document synchronisation between the two platforms). However, the API is not publicly documented at the time of writing. Estateably also offers a Clio integration that imports matter data from Clio into Estateably via a configurable field mapping interface — this one-way import demonstrates that Estateably has a structured data ingestion layer.

This guide documents conceptual mappings based on Estateably’s publicly visible features and data model. Field-level API mappings will require direct API access, which would be established through a partnership or integration agreement.

Conceptual Field Mapping#

The mappings below are based on Estateably’s publicly described features, its user interface, and the data requirements of probate administration. They represent the most likely mapping between Estateably’s internal data model and INHERIT schemas. Exact API field names are marked as [TBC – requires API access].

Deceased / person.json#

Estateably’s primary record is the deceased individual whose estate is being administered. This maps directly to an INHERIT person.json entity with roles: ["testator"].

Estate Record / estate.json#

Each Estateably matter represents one estate under administration. This maps to INHERIT’s estate.json.

Status Mapping#

Estateably’s probate workflow stages map to INHERIT’s estate lifecycle as follows:

Note: Estateably’s workflow is inherently probate-focused. Unlike general practice management tools, its stages align closely with INHERIT’s post-death lifecycle (pre_probate through closed). The estate planning stages (planning, confirmed) are not typically relevant — Estateably picks up where estate planning tools leave off.

Executors / executor.json + person.json#

Estateably tracks executors (personal representatives, administrators) as key participants in estate administration. Each executor maps to both a person.json record (their identity) and an executor.json record (their role in the estate).

Beneficiaries / person.json + bequest.json#

Estateably tracks beneficiaries and their entitlements. Each beneficiary is a person.json record; their inheritance is modelled as one or more bequest.json entries.

Assets / asset.json + Asset Category Schemas#

Estateably captures detailed asset information for estate valuation, court reporting, and distribution. Each asset maps to INHERIT’s asset.json with an appropriate asset category schema.

Liabilities / liability.json#

Estateably tracks the deceased’s debts and ongoing obligations that must be settled from the estate.

Documents / document.json#

Estateably stores estate-related documents. These map to INHERIT’s document.json.

Integration Architecture#

Because Estateably’s API is not publicly documented, integration approaches must account for the current access landscape. There are three realistic architectural paths, each with different prerequisites and capabilities.

Path 1: Clio as Intermediary (Available Now)#

Estateably already integrates with Clio — importing matter data from Clio into Estateably with configurable field mapping. Since Clio has a well-documented public API (see the Clio Integration Guide ), INHERIT can reach Estateably indirectly:

                    Clio API (documented)         Estateably-Clio integration
  INHERIT document ───────────────────────► Clio ──────────────────────────────► Estateably
                                            Matter

Advantages:

• Works today, without any Estateably API access
• Leverages existing, tested integrations on both sides

Limitations:

• One-way only (Clio to Estateably)
• Two-hop translation introduces potential data loss
• Depends on the firm using both Clio and Estateably

Path 2: Direct API Integration (Requires Partnership)#

With access to Estateably’s internal API, a direct integration eliminates the Clio intermediary and enables bi-directional data flow.

Path 3: INHERIT as a Data Exchange Format (Platform-Neutral)#

Rather than building a point-to-point integration, Estateably could adopt INHERIT as its import/export format — enabling interoperability with every INHERIT-compliant platform without custom integration code.

Recommended Architecture#

For immediate value, Path 1 (Clio intermediary) provides a working bridge today. For long-term strategic value, Path 3 (INHERIT as exchange format) is the strongest approach. Path 2 (direct API) is the natural stepping stone between the two.

If you work with Estateably or in probate administration and would like to discuss INHERIT compatibility, please get in touch .

Court Form Data Mapping#

Estateably’s library of over 3,000 court forms across US, Canadian, and UK jurisdictions is one of its most significant features. Each court form requires specific estate data fields to be populated.

How Court Forms Consume Estate Data#

INHERIT as a Canonical Data Layer for Court Forms#

The relationship between INHERIT and Estateably’s court forms is complementary:

1. INHERIT provides the structured data. An INHERIT document contains the people, assets, liabilities, bequests, and jurisdiction-specific details that court forms require.
2. Estateably provides the form templates and jurisdiction logic. Estateably knows which fields each court form requires, which court rules apply, and how to format the output for filing.
3. The integration point is data, not forms. INHERIT does not generate court forms. It provides the data that court forms consume.

Jurisdiction Extensions and Court Form Requirements#