I have the following code snippet.

const user = await User.findOne({ email: ownerData.email })
            .select('-_id -__v -updatedAt')
            .lean();
        if (!user) {
            throw new HttpException(404, 'User not found');
        }
        await User.deleteOne({ email: ownerData.email });

        console.log(user);

        const newUser = await User.create({
            ...user,
            ...{
                address: ownerData.address,
                city: ownerData.city,
                state: ownerData.state,
            },
            _id: ownerId,
        });
        await newUser.save();

so basically what I want to do is delete the old user that is already present create a new one with the details of the old one. But unfortunately even though I am not taking the old updatedAt field, the old updatedAt field is getting populated on the new user object doc as well.
There is a chance that the ownerId can be the same as the old _id. I believe it's because of that, but I don't get around this problem.
Thanks

EDIT

I got another interesting lead on this problem.
Since I am considering createdAt at the very first line of code

const user = await User.findOne({ email: ownerData.email })
            .select('-_id -__v -updatedAt')
            .lean();

The new doc is taking the time from this createdAt field. Once I removed and checked the newUser is being created at a new time. Is there any relationship between createdAt and updatedAt ?