Migrate from CodeCanyon (Pro + add-ons)

If your site still runs Progress Map Pro (codespacing-progress-map) and optional standalone extensions (List & Filter, Draw a Search, Nearby Places, etc.), Ultimate replaces all of them with one plugin.

Your maps, locations, and most settings live in the WordPress database. Migration is about swapping the plugin code, not rebuilding content.

Goals

  • One active plugin: Progress Map Ultimate
  • Same maps and markers on the front end
  • Modules available under Ultimate toggles instead of separate plugins
  • License and updates via progress-map.com / Freemius

Step-by-step

1. Backup

Backup the database and wp-content/plugins (or the whole site). Keep a way to roll back for 24–48 hours.

2. Inventory

Under Plugins, list what is active, for example:

  • Progress Map (Pro)
  • List & Filter / Markers Filter / Draw a Search / Advanced Search / Nearby Places / Keyword Search / Directions / Submit Locations

Note which features you actually use on production maps.

3. Install Ultimate (do not delete Pro yet)

  1. Install and activate Progress Map Ultimate from your progress-map.com ZIP.
  2. If WordPress or Ultimate shows a conflict notice, use Deactivate conflicting plugins (or deactivate Pro + add-ons manually).
  3. Leave Ultimate active.

You may keep the old plugin folders on disk temporarily for rollback; they must stay inactive.

4. Activate license

Complete license activation for Ultimate.

5. Verify core maps

  1. Open All Maps — existing maps should still be there.
  2. Edit one map; confirm settings.
  3. View the front-end page with the shortcode — markers should load.
  4. Confirm the Google API key is still present in settings.

6. Enable modules you need

Under Ultimate Modules, enable the features that used to be separate plugins. Re-open a map and confirm module settings panels appear (Draw a Search, Markers Filter, etc.).

Old standalone settings are generally reused when option keys match; spot-check each feature once.

7. Remove old plugins (when confident)

After front-end checks pass:

  1. Delete inactive Pro and add-on plugins from Plugins (or leave inactive as a cold backup).
  2. Do not run Pro and Ultimate together again.

8. Clear caches

Purge page cache, minify cache, and CDN cache so browsers load Ultimate’s scripts.

What transfers automatically

  • Map custom post type entries and their settings
  • Location latitude/longitude (and related meta) on posts
  • Most feature options stored in options / post meta

What to re-check manually

  • Front-end shortcodes still point to the correct map IDs
  • Module-specific UI (list layouts, draw tools, nearby shortcodes)
  • Custom CSS that targeted old plugin CSS file names (rare)
  • License (new Freemius product / account on progress-map.com)

Do not

  • Upload the old Pro ZIP “on top of” Ultimate
  • Keep standalone add-ons active “just in case”
  • Expect CodeCanyon download notifications — updates now come through Freemius / progress-map.com

Very old Progress Map v2

If you still use legacy shortcodes such as [codespacing_progress_map], update pages to modern shortcodes like [cspm_main_map id="…"] from the map edit screen. Ultimate follows the post-v3 map architecture (All Maps / Add New Map).

Need help?

See Get support and mention that you are migrating from CodeCanyon Pro + add-ons. Include the list of previously active extensions.

Top