Legislative intelligence / 90R
SESSION 2027View project ↗

Business Organizations Code § 10.154: CERTIFICATE OF CONVERSION

No bill in the 90th Legislature changes this section yet

Follow this section in Texas Bill Atlas: a bill filed later that changes it shows up as new.

Part of Business Organizations Code Chapter 10, with every bill that changes it.

Bills are matched to sections automatically from their text and can be missed, for example when a bill changes a whole chapter at once or renumbers sections. No bill listed here does not mean no bill changes this section.

Current law

Sec. 10.154. CERTIFICATE OF CONVERSION. (a) A certificate of conversion must be filed for the conversion to become effective if:

(1) any domestic entity that is a party to the conversion is a filing entity; or

(2) any domestic entity to be created under the plan of conversion is a filing entity.

(b) If a certificate of conversion is required to be filed in connection with a conversion, the certificate must be signed on behalf of the converting entity and must include:

(1) the plan of conversion or a statement certifying the following:

(A) the name, organizational form, and jurisdiction of formation of the converting entity;

(B) the name, organizational form, and jurisdiction of formation of the converted entity;

(C) that a plan of conversion is on file at the principal place of business of the converting entity, and the address of the principal place of business;

(D) that a plan of conversion will be on file after the conversion at the principal place of business of the converted entity, and the address of the principal place of business; and

(E) that a copy of the plan of conversion will be on written request furnished without cost by the converting entity before the conversion or by the converted entity after the conversion to any owner or member of the converting entity or the converted entity; and

(2) a statement that the plan of conversion has been approved as required by the laws of the jurisdiction of formation and the governing documents of the converting entity.

(c) In addition to complying with the requirements of Subsections (a) and (b), if Sections 10.1025 and 10.109 apply to the conversion, the certificate of conversion required by this section must:

(1) be titled "Certificate of Conversion and Continuance"; and

(2) include a statement certifying that the converting entity is electing to continue its existence in its current organizational form and jurisdiction of formation.

Acts 2003, 78th Leg., ch. 182, Sec. 1, eff. Jan. 1, 2006.

Amended by:

Acts 2007, 80th Leg., R.S., Ch. 688 (H.B. 1737), Sec. 54, eff. September 1, 2007.

Acts 2009, 81st Leg., R.S., Ch. 84 (S.B. 1442), Sec. 18, eff. September 1, 2009.

Acts 2015, 84th Leg., R.S., Ch. 32 (S.B. 860), Sec. 14, eff. September 1, 2015.

Acts 2023, 88th Leg., R.S., Ch. 27 (S.B. 1514), Sec. 11, eff. September 1, 2023.

Links

Texas Bill Atlas is an independent research tool, not an official state website.

PLEASE READ

Before you use Texas Bill Atlas

An independent, open-source project. This site is not affiliated with, endorsed by, or operated by the Texas Legislature, the Texas Legislative Council, the Secretary of State, or any state agency.

Data may be incomplete, delayed, or wrong. Bill records are copied automatically from the legislature’s public files. Topic, agency, party, influence and last-action tags, and the full-text summaries written by Luna (an AI model), are automated interpretations and can be mistaken.

Not advice. Nothing here is legal, political, or professional advice. The project and its contributors make no warranty of accuracy or completeness and accept no liability for errors, omissions, or decisions made using this site.

Check the official record. Confirm anything that matters on Texas Legislature Online. Spotted a mistake? Report it on GitHub.

TEXAS BILL ATLAS

Privacy Policy

Last updated: November 11, 2026

Texas Bill Atlas is a free, independent, open-source project. We believe you should be able to research legislation without creating an account or providing personal information.

Information we collect

We do not require registration, names, email addresses, or other personal information to use the service.

We do not sell personal information, serve targeted advertising, or intentionally track individual browsing activity.

Analytics and security

We use Cloudflare for website delivery, security, and traffic analytics.

Cloudflare may process technical information such as IP addresses, browser details, request information, and website usage statistics. Cloudflare may also use cookies necessary for security and abuse prevention.

For more information, see Cloudflare's Privacy Policy.

Watchlists and saved preferences

Watchlists and preferences are stored locally in your browser by default.

If you choose to enable watchlist synchronization, we store the selected bill numbers, the member codes of legislators you follow, your saved searches (their names, search words and filters), filters, and hashed access keys on our server. View-only links show the bill numbers only.

No account or personal information is required. Anyone possessing a valid private access link may access the associated watchlist according to that link's permissions.

You can delete a synced watchlist using its edit access key. Inactive synced watchlists are automatically removed after approximately one year.

Technical data

Our servers may temporarily process IP addresses and request information for security, rate limiting, and reliable operation.

We do not use this information to build individual user profiles.

The site also loads certain external resources, including Google Fonts. Those providers may receive ordinary technical request information.

Third-party services

Links to government websites, GitHub, and other external services are governed by their respective privacy policies.

Changes

We may update this policy as the project develops. The current version will be available on this website with its updated date.

Questions

For questions about the project or its privacy practices, visit our GitHub repository.