[philo23]

From that diff it looks to me that if ~/.mozilla exists OR if MOZ_LEGACY_HOME is set it uses ~/.mozilla, otherwise it uses the $XDG_CONFIG_HOME/.mozilla directory instead.

So no migration to the XDG directory, but also no throwing away your existing data either.

[paulddraper]

That’s the safest.

Who knows what might be touching that data today. Or backing it up, etc

[gen2brain]

I know a few apps that did the same (mpv for example). If you still have it in home root it uses that, when you move it to .config it uses that instead. Auto migrating could and would create issues.

[shmerl]

So is it safe to just manually move $HOME/.mozilla to $HOME/.config/mozilla ?

[aallaall]

That’s the hard part to answer, that Mozilla leaves to you!

[neilv]

I would guess not. I see `.mozilla` absolute pathnames within some files in a profile directory (specifically, `extensions.json` and `pkcs11.txt`).

(This has bitten me before. I don't know why it was done that way.)

[badsectoracula]

It seems Firefox doesn't really rely on these. My profile directory has been around for more than a decade, went through three computers and even between Windows and Linux and from plain Firefox to Firefox Developer Edition and pretty much everything transferred just by copying the files around (however i didn't copy the full Mozilla directory, first i let Firefox make a new empty profile by itself and copy/pasted the files in it, overwriting whatever was already there).

It even had the original XUL-based DownThemAll version, got disabled after XUL addons were disabled and some time one or two years later it got re-enabled again after the dev released a webextensions compatible version (sadly with several limitations, but still useful for bulk downloads).

Amusingly, there are a couple Windows absolute paths in there even though this profile has been on Linux for a few years now :-P

[neilv]

Interesting. I have had extensions lose their storage when the profile directory path changed, and at the time it seemed to be because of the pathnames within the files.

[shmerl]

I guess we can try replacing the value there manually to the new one before starting Firefox.

[johnisgood]

This is very important to know if this is really the case. And if it is, then what is the best way to migrate? Is there an official, supported method if "mv" is not it?

[shmerl]

There is an answer in the comment to the original bug:

> there is no migration path supported at this point: only new profiles are expected to use the new setup. Migrating manually is at your own risk, make a backup before.

I'll try to do it manually, replacing paths in the couple of files mentioned above first.

[safety1st]

I hate to say it, but if there's no migration path, this improvement may not have been the best use of Mozilla's resources. Because who's creating new Firefox accounts in 2025? I mean I guess the folder will be in the right place the next time I do a fresh install, but I'd rather see them investing in stuff that grows their user base.

[shmerl]

Better something simple than nothing. I'm glad they didn't use it as an excuse not to do it at all. I've seen this happening with other projects.

[Gabrys1]

I think yes. And that's maybe the reason they didn't properly split the files to .cache/ .config etc