PHPackages                             minnur/location\_migration - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. minnur/location\_migration

ActiveDrupal-module[Utility & Helpers](/categories/utility)

minnur/location\_migration
==========================

Migration plugins for migrating Drupal 7 location data from Drupal 7 to Drupal 9

1.0.6(2y ago)0178GPL-2.0-or-laterPHPPHP >=7.1

Since Mar 20Pushed 2y ago1 watchersCompare

[ Source](https://github.com/minnur/location_migration)[ Packagist](https://packagist.org/packages/minnur/location_migration)[ Docs](https://www.drupal.org/project/location_migration)[ RSS](/packages/minnur-location-migration/feed)WikiDiscussions main Synced 3w ago

READMEChangelog (1)Dependencies (2)Versions (3)Used By (0)

INTRODUCTION
------------

[](#introduction)

The [Drupal 7 Location module](https://www.drupal.org/node/18723) allows users to store locations in a `location` field (`location_cck` submodule), and also directly for `node`, `taxonomy_term` and `user` entities (`location_node`, `location_taxonomy` and `location_user` submodules).

With `location_email`, `location_fax`, `location_phone` and `location_www`submodules, the data stored for a location can be extended with additional *email*, *fax number*, *telephone number* and *www address* properties.

**The Location Migration module provides migration path for these data.**

### HOW IT WORKS

[](#how-it-works)

For location data stored in a field,

- The original `location` field type gets mapped to `address` field, and every *address-like* location property is migrated into this address field.
- Non-empty geographical coordinates are migrated into a new `geolocation`field with `_geoloc` field name suffix.
- When `location_email` is enabled on the source site, the email addresses stored for a location will be migrated into a new `email` field with `_email`field name suffix. The `email` field type is available in Drupal 8/9 by default.
- When `location_fax` is enabled on the source site AND the `telephone` field type is available on the destination site (core *Telephone* module), the fax number of a location will be migrated into a new `telephone` field with `_fax`field name suffix.
- If `location_phone` is enabled on the source site AND the `telephone` field type is available on the destination site, the telephone number stored for a location will be migrated into a new `telephone` field (`_phone` field name suffix).
- When `location_www` is enabled on the source site AND the `link` field type is available on the destination site (core *Link* module), the www address stored for a location will be migrated into a new `link` field (`_url` field name suffix).

For location data stored directly for `node`, `taxonomy_term` and `user`entities, Location Migration basically repeats the same what it does for the location fields, but the name of the (this time new) address field, and the base name of the additional fields will be `location_node`, `location_taxonomy_term`and `location_user`, accordingly. If this *entity location* was configured to store multiple locations, the new field's name will have an additional `_` suffix as well.

**Location Migration wants to migrate as much data as possible**. If you don't need any of the additional fields, you can delete them **after the migration was executed**.

REQUIREMENTS
------------

[](#requirements)

This module depends on the following modules:

- Address ()
- Geolocation ()
- Migrate Drupal (included in Drupal core)

INSTALLATION
------------

[](#installation)

You can install Location Migration as you would normally install a contributed Drupal 8 or 9 module.

CONFIGURATION
-------------

[](#configuration)

This module does not have any configuration option.

MAINTAINERS
-----------

[](#maintainers)

Current maintainer:

- Zoltán Horváth (huzooka) -

This project has been sponsored by [Acquia](https://www.acquia.com/)

###  Health Score

21

—

LowBetter than 18% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity13

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity37

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~0 days

Total

2

Last Release

825d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/27d64866885eb274531503f8cff7b4cc6d9a1ff7a2dd03d3b3182ccbb549b967?d=identicon)[minnur](/maintainers/minnur)

---

Top Contributors

[![minnur](https://avatars.githubusercontent.com/u/4031934?v=4)](https://github.com/minnur "minnur (2 commits)")

### Embed Badge

![Health badge](/badges/minnur-location-migration/health.svg)

```
[![Health](https://phpackages.com/badges/minnur-location-migration/health.svg)](https://phpackages.com/packages/minnur-location-migration)
```

###  Alternatives

[voidagency/vactory_starter_kit

Vactory is a custom Drupal profile which is developed and released by VOID Agency.

1020.9k](/packages/voidagency-vactory-starter-kit)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)