When I try to convert from old colors to new colors I get a failure message and I am not able to evaluate what must be set or available to convert.
Is there a documentation for the color conversion process?
Here you see my current âoldâ color palette from version 2.14:
Hi Joachim,
Thanks so much for your report!
I can replicate the problem and have added it to the internal bug tracker. We will update this thread as soon as it is fixed.
The reason for this is relatively simple: In your color palette, you can see that your primary color has an HSL value. All other colors are probably created within the variable manager and added to the palette via RAW input. The current logic does not establish a connection to the variable manager, so your colors have no value in this sense (at least thatâs how the color manager sees it).
If you want to define your colors in the color manager now, there is a relatively cumbersome workaround. Just let me know and Iâll be happy to explain the necessary steps.
However, you can also just leave everything as it is and wait until we have found a solution that makes working with colors from the variable manager more intuitive, so that the color and variable managers work hand in hand 
â and not against each other.
Best regards,
timmse
Hi Timmse,
the screenshots are from my test-site. It could be that I entered HSL by random, not by default.
I work only with color varialbles since around 2 years, so I did not use the Bricks Colors at all.
And it was always weird to me, how to safely enter the hex codes into old Bricks Color manager, because each color had 4 option (hex, raw, rgb,hsl). I never knew which is those is active, how to make one active and so on. Thatâs why I dedecided to work only with color variables.
and there was the problem, that the main-body color was always overwritten from somewhere in the hidden/background and I have never found out, what was causing this error.
This is my backstory with Bricks color manager, not so niceâŠ
In the screenshot I marked the color with an arrow, with was named originally main-body, but as said above was overwritten by kind of a ghost.
So, I would be very happy, if you tell me, what is your suggested way to convert the bricks colors to the new Bricks Color manager. Currently I can not edit the colors in the new manager and I am unsure what is going on.
So, your help is very welcome 
Thanks for the background info, but Iâm afraid it wouldnât change anything if you defined the colors in the color manager instead of the variable manager. Accordingly, I would suggest that you send us your access data, specific information which body color (variable) should be used/where itâs set (theme styles?), and a link to this thread by email, and Iâll try to find out whatâs causing your actual problem:
Once weâve sorted that out, Iâll be happy to explain how to transfer the colors manually to the color manager.
Ok, color error (lost color hexcode) appeared again:
Send me an email, and I can send you a duplicator backup to install on your site, because this is a local installation.
Hi Joachim,
We fixed this issue (convert âvariable manager colorsâ to âcolor manager colorsâ in Bricks 2.2, now available as a one-click update in your WordPress Dashboard. If you want to manage your colors in the color manager in the future, you can delete the color variables in the variable manager after conversion, since the color manager variables override them anyway.
Regarding your âlostâ color: I see in your screenshot that the value refers to --body-text, but should be --axcolor-body-text. If this is not the cause, please provide us with an accessible installation, as you have done in the past.
Please take your time to read the changelog entry before updating, and let us know if you continue to experience issues.
Naaa, not really solved.
Here is why:
I was able to convert all colors, except one, the body color 
This body text color remains with error:
If I delete the body text color, I can NOT add it, due to error belowâŠ
If I want to add the body text color as a new variable there is also en error, more text in the screenshot.
Interestingly, thatâs exactly the variable (âbody-text) you had problems with before. My guess is that it simply has no value, which is why the âconversion failedâ error occurs.
As for the second error, the variable (âaxcolor-body-text) should already be present in the color manager after conversion, since it was (and still is) present in the variable manager, as can be seen here:
All in all, very confusing and unfortunately impossible to understand without logging in, so please
Hey Timmse,
just sent you an email with all details.
So you can test and install on your site.
Hi Joachim,Thanks! My theory is as follows: --body-text is a âcorpseâ from Advanced Themer, which is no longer installed. I can see this when I look at the entry in the color palette, as the syntax corresponds to that of AT:
{
"raw": "var(--body-text)",
"rawValue": {
"light": "hsla(209, 90%, 8%, 1)",
"dark": "#000000"
},
"id": "fwxgzp",
"name": "Body Text"
},
Since youâre not using AT anymore, just delete the variable from the palette and everything is fine.