---
title: "Deprecation: #82902 - Custom Backend Module registration methods"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:deprecation-82902"
source: "Changelog/9.0/Deprecation-82902-CustomBackendModuleRegistrationMethods.rst"
typo3-version: "9.0"
typo3-major: 9
type: "deprecation"
issue: 82902
forge: "https://forge.typo3.org/issues/82902"
tags: ["Backend", "PHP-API", "PartiallyScanned"]
rendered: "2026-09-17T21:17:42+00:00"
---

# Deprecation: #82902 - Custom Backend Module registration methods {#deprecation-82902-custom-backend-module-registration-methods}

See [forge#82902](https://forge.typo3.org/issues/82902)

## Description {#description}

The internal API to register backend modules via `ExtensionManagementUtility::configureModule()` and
`configureModuleFunction` has been marked as deprecated.

It was solely introduced to allow script-based dispatching of backend modules used in TYPO3 v6.2 which
had multiple entry-points (mod1/conf.php and mod1/index.php).

Since TYPO3 v7 Backend Routing is available, thus the old registration API is no longer needed.

## Impact {#impact}

Registering a `configureModuleFunction` will trigger a deprecation warning.

Calling `ExtensionManagementUtility::configureModule()` will trigger a deprecation warning.

## Affected Installations {#affected-installations}

Installations with legacy and/or custom Backend modules in extensions.

## Migration {#migration}

Use either `ExtensionManagementUtility::addModule()` or Extbase's
`ExtensionUtility::registerModule()` to register a module, always providing a `routeTarget`.