I had the same issue, managed to get the liquidity back from PancakeSwap v1, then added it to v2 correctly. The whole problem seems to stem from setting the wrong IUniswapV2Router02 in the contract constructor. I copied the router address after seeing it in multiple threads and other forums too, should have spent a little more time to double check the address.
I had 1 BNB plus 90% of my token supply in v1 so I really wanted to get it back.
Here is how I got my BNB and tokens back (hope it helps):
From remix, go to the deploy and run section, then under deployed contracts you can see the token contract that you deployed to mainnet (you can also do this under the contract → write tab in your contract on bscscan but will probably need to verify the contract first).
These are the methods I called:
excludeFromFee: 0x05fF2B0DB69458A0750badebc4f9e13aDd608C7F
setLiquidityPercent: 0
setTaxFeePercent: 0
setMaxTxPercent: 100
swapAndLiquifyEnabled: false
I think the issue was the fees for liquidity and tax.
I used pancakeswap v1 in the browser to remove liquidity. You probably won’t see your liquidity at first, but paste in your token’s contract address and make sure your wallet is connected with the account that holds the LP tokens.
Once you see your pair, set the remove liquidity to 100%. You will probably leave 1 single token on the v1 but that is it (got 0.9999 BNB back plus the rest of the tokens). You will be requested to sign first, after accepting then click the remove and then you can approve the transaction.
If you add liquidity to Pancake v2 after this, you will need to keep swapAndLiquifyEnabled set to false, otherwise nobody can purchase your token, still trying to figure this part out 
The bad news:
Since the router is hard coded in the safemoon contract, you will probably need to deploy a new token to mainnet if you want the liquidity fee to go back to the v2 liquidity pool as the swapTokensForEth function uses the hard coded router address.
Pancakeswap V2 router (looks correct but double check it… I found this in my browser console under network requests):
0x10ED43C718714eb63d5aA57B78B54704E256024E
