Skip to main content

AssemblyAI Migration Guide

Availability
Available CoreAvailable StandardAvailable PlusAvailable ProAvailable Enterprise FlexAvailable PyAirbyte
Connector type (beta)
Available Data replicationNot available Agent(learn more)
Support Level
Marketplace
Connector Version
1.0.0 (last updated an hour ago)
Sync Success Rate
Low
Usage Rate
Low
Data workers used
0.2 per sync (Learn more)
Definition ID
dcb2f998-6493-4078-8390-e320487157a0

Upgrading to 1.0.0​

Optional backfill can delete historical data

Clearing transcripts deletes destination data. Back up the affected tables before an optional backfill: AssemblyAI's listing API only returns transcripts from the last 30 days of usage, so older transcripts can't be re-synced.

What changed​

The lemur_response stream and its optional request_id setting have been removed. The four transcript streams retain their names, schemas, primary keys, and state format. This release also fixes API-key authentication, pagination to older transcripts, and parsing of transcript timestamps without a trailing Z.

Why​

AssemblyAI deprecated LeMUR on March 31, 2026. Its GET /lemur/v3/{request_id} retrieval endpoint now returns HTTP 404. The replacement LLM Gateway generates new responses via a chat-completions request; it is not a documented replacement for retrieving previously generated LeMUR responses.

Who is affected​

Connections that select lemur_response must update their configured catalog. Connections selecting only transcript streams do not need a schema or state migration.

Migration steps​

  1. Upgrade the AssemblyAI connector to version 1.0.0 or later.
  2. For each affected connection, open the Schema tab and select Refresh source schema. Accept the removal of lemur_response and save the catalog. For API-managed connections, remove lemur_response from the configured catalog.
  3. Remove request_id from manually managed source configurations. Existing configurations containing it remain accepted, but it is no longer used.
  4. Run a sync of the remaining streams. No data reset is required to remove LeMUR; existing destination data is not a source for new LLM Gateway responses.

An optional backfill can recover transcripts missed by the previous pagination bug. Back up the destination tables first, then clear and resync the transcripts stream if needed. The re-sync is bounded by start_date and AssemblyAI's 30-day listing window; older history cannot be recovered from this API. Skipping the backfill leaves previously missed records before the saved cursor absent from the destination.

Downstream consumers​

Update any SQL, dbt models, dashboards, or exports that expect new lemur_response records (request_id, response, and usage). Historical data does not become LLM Gateway data automatically; applications using LLM Gateway must persist its generated responses themselves.

Connector upgrade guide​

Review the following information to prepare for and execute your upgrade.

Review the changelog​

Before updating a connector, review the changelog to understand the changes and their potential impact on your existing connections. Find the changelog for any connector by navigating to the bottom of the documentation for that connector. Major version releases also include a migration guide.

Plan for major updates​

Major updates may require you to adjust connection settings or even make changes to your data pipelines. Allocate enough time and resources for this. Use the migration guide to ensure your transition process goes smoothly.

Airbyte provides tooling that guarantees safe connector version bumps and enforces automated version bumps for minor and patch updates. You always need to manually update for major version bumps.

Self-managed plans: pin a specific version if you can't update​

If you're unable to upgrade to the new version of a connector, you can pin that connector to a specific version.

  1. In the navigation bar:

    • If you're on the Self-Managed Enterprise plan, click Organization settings > Sources/Destinations.

    • If you're on any other plan, click Workspace settings > Sources/Destinations.

  2. Edit the entry for the connector you want to pin.

  3. Set the Default Version to the version you want to use.

Self-managed plans: update the local connector image​

If you self-manage Airbyte, you must manually update the connector image in your local registry before proceeding with the migration. Follow the steps below.

  1. In the navigation bar:

    • If you're on the Self-Managed Enterprise plan, click Organization settings > Sources/Destinations.

    • If you're on any other plan, click Workspace settings > Sources/Destinations.

  2. Find the connector you want to update in the list of connectors.

    note

    Airbyte lists two versions, the current in-use version and the latest version available.

  3. Click Change to update your OSS version to the latest available version.

Update the connector version​

Update each instance of the connector separately. If you have multiple instances of a connector, updating one doesn't affect the others.

  1. In the navigation bar:

    • If you're on the Self-Managed Enterprise plan, click Organization settings > Sources/Destinations.

    • If you're on any other plan, click Workspace settings > Sources/Destinations.

  2. Select the instance of the connector you wish to upgrade.

  3. Select Upgrade.

  4. Follow the prompt to confirm you are ready to upgrade to the new version.

Clear data from affected streams​

After upgrading a connector with a breaking change, you must refresh affected schemas and clear your data.

  1. In the nav bar, click Connections.

  2. Find the connection affected by the upgrade.

  3. Click the Schema tab.

  4. Click Refresh source schema (looks like ). When Airbyte finishes, it shows you any detected schema changes.

  5. Click OK.

  6. Click Save changes

  7. Clear the data for the streams affected by this upgrade.

Once the clear is complete, you can begin syncing your data again as usual.

Was this page helpful?