If I deploy the lightning community, in destination org I see the community as classic.
No matter what I do or how many times I redeploy, the outcome is same. I even tried comparing the metadata locally, no differences.
The value of setting
Enable ExperienceBundle Metadata API doesn't make any difference.
Even the login page type shows as default page which is classic:
Had to convert the classic to lightning communities and the older community was build with basic OOTB features.
- I was easily able to create a new lightning (based on the old classic community) on our DEV environment.
- Next was easy step to do the deployment.
Now I had heard/read issues with lightning community deployment but this time I was lucky to experience this issue myself.
We have our CI/CD process with copado (copado here is not very relevant as I have same problem with SFDX/ANT migration tool and even changeset).
Following components I tried to deploy with changeset (and other tools):