Perhaps it's an idea to apply for a free
https://letsencrypt.org/ certificate for the time being - and get a new one once the server is moved?

The problem with non matching certificates is that the visitor has abolutely no idea whether that certificate
really belongs to your website or whether the website is hacked

and somebody tries to impersonate the site with a different certificate (which means compromised session and risk of data and privay loss

). It was only after I found this thread that I decided to register after all as at least you claim the certifiacte is authentic - but please note you cannot claim nor guarantee that nobody else has access to the https session as it's apparently a generic certificate where the hoster as certificate owner will automatically have access to the session too! Not very wise in the 21st century, certainly not in the post Snowden era...