Skip to main navigation Skip to main content Skip to page footer

Can I import tt_address data into the Address Manager?

Yes. Starting with version 5.0.0, Address Manager provides a console command to migrate records from tt_address into the Address Manager tables.

What exactly does the command do?

The command reads all records from tt_address and creates the corresponding Address Manager records. It transfers, among others, the following fields:

  • Core data: name, gender, first_name, middle_name, last_name, birthday, title, email, phone, mobile, www
  • Address: address, building, room, company, city, zip → postal_code, region, country
  • Description: description (HTML is stripped)
  • Map data (if present): map_latitude, map_longitude, map_zoom, map_tooltip, map_link, directions from fields prefixed with txaddressmanagerlist in tt_address
  • Images: linked sys_file_reference entries for the images field are copied per address
  • Groups/Taxonomies:
    • company → Position (Address Manager: addressposition)
    • country → Organisation (Address Manager: addressorganisation)
    • tt_address_group via MM → Address Manager groups (addressgroup)

On which pages are new records created?

  • Actual address records keep the same pid as the original tt_address record.
  • New taxonomy entries (positions, organisations, groups) are created on the container page (PID) that you pass to the command.

Usage and syntax

vendor/bin/typo3 address_manager:migrate-from-tt-address <containerPageUid> [truncate]

Examples:

  • Minimal: vendor/bin/typo3 address_manager:migrate-from-tt-address 123
  • With pre-clean (truncate target tables): vendor/bin/typo3 address_manager:migrate-from-tt-address 123 true

Parameters:

  • containerPageUid (required): PID on which new positions/organisations/groups will be created.
  • truncate (optional, default false): true/false or 1/0. If true, relevant target tables are truncated before migration and existing image references of addresses are removed.

Prerequisites and notes

  • Create a database backup beforehand.
  • Ensure the tt_address extension and its tables (tt_address, tt_address_group, tt_address_group_mm) exist.
  • The command migrates all tt_address records; there is no built-in filtering.
  • Running repeatedly without truncate may create duplicates (the migration creates new addresses). Use truncate or clean up data beforehand.

Which tables are written?

  • tx_addressmanager_domain_model_address (addresses)
  • tx_addressmanager_domain_model_addressgroup (groups) + MM: tx_addressmanager_address_addressgroup_mm
  • tx_addressmanager_domain_model_addressposition (positions) + MM: tx_addressmanager_address_addressposition_mm
  • tx_addressmanager_domain_model_addressorganisation (organisations) + MM: tx_addressmanager_address_addressorganisation_mm
  • sys_file_reference (image references for addresses)

Limitations and specifics

  • Free text/HTML in description is reduced to plain text (strip_tags).
  • table_local in sys_file_reference is only set if the column exists (compatible with newer TYPO3 versions).
  • There is no dry-run. Test on a copy/stage environment if needed.

Benefits for agencies and editors

  • Fast migration from legacy tt_address projects to Address Manager
  • Saves time by automatically transferring groups and images
  • Consistent data foundation for search, maps and SEO fields