Currently the add-on is designed to use WordPress as the backend. No one on the internet would have to know or ever see WordPress, but it is necessary as the add-on pulls content from WordPress, and never actually copies it to Concrete.

This enables WordPress add-ons to function as designed, and to allow email, app or web-based blogging through WordPress.

However, I think even a basic ability to blog without a WordPress backend could be a good thing down the road.

So if it would be alright with you, I would recommend leaving your blog, then in the add-on, drop in the URL of your WordPress blog and it should all pull in and integrate with Concrete.

Then (its in the documentation) you can add a small snippet of code to the WordPress theme header, so all traffic to the old blog redirects back to Concrete automatically, so no one sees WordPress anymore. If the blog is using a URL you need for Concrete, you could perform the steps to move the WordPress blog to a new URL, then continue from there.

Let me know if there's anything I can do to help or improve the add-on :)