Skip to content
TerritoryKit Territory Map Maker
Open Map Builder

Migrate MapPoint territory data to TerritoryKit

Use open exported files as the bridge from a legacy MapPoint workflow to TerritoryKit.

Open Map Builder

When to use this

Use this guide when you can still export locations or boundaries from MapPoint, a saved report or an intermediate tool.

TerritoryKit import modal with an Excel file loaded and latitude and longitude columns highlighted.
Import an Excel workbook, confirm the coordinate columns, and create the point layer.

Step-by-step workflow

  1. Export an open format

    Export point rows as CSV or Excel with latitude and longitude, and export boundaries as KML when your available MapPoint workflow supports it.

  2. Keep the original backup

    Preserve the source files before cleaning column names or converting formats.

  3. Import locations

    Open TerritoryKit Import, choose the coordinate columns and review the repair summary.

  4. Import boundaries

    Add KML or KMZ zones when you have a compatible boundary export.

  5. Validate and save

    Compare locations and zones, review unassigned records, then export a TerritoryKit project backup.

TerritoryKit map builder showing imported KML neighbourhood boundaries compared with mapped points.
KML or KMZ boundaries can be imported as zones and compared with location points.

Supported formats and inputs

  • Supported bridge formats: CSV, XLSX, XLS, KML and KMZ.
  • Direct .ptm MapPoint project files are not supported.
  • TerritoryKit does not decode proprietary MapPoint binary data.

Tips and common mistakes

  • Check coordinate order and ranges after every legacy export.
  • Use KML for polygon boundaries when available; spreadsheet rows alone do not recreate territory shapes.
  • Treat automatic field suggestions as a starting point and verify the mapped result.

Export and results

After validation, save an editable TerritoryKit project and export open geometry or tables for downstream use.

FAQ

Can TerritoryKit open a .ptm file?

No. Export to CSV, Excel or KML through a tool that can still read the project.

Will a CSV contain my territory polygons?

Usually not. CSV is appropriate for point rows; use KML or another open geometry format for boundaries.

Is there a MapPoint preset?

Not yet. This guide documents the supported open-format workflow first while demand is measured.

Related workflows

Repair imported coordinate rowsChoose KML or KMZBuild territories from Excel

Build your first territory map

Bring your coordinates, draw the zones you need, and see the results as the map changes.

Open Map Builder
No account required