Planning Your Migration from MapVision to VectoStar

Planning a migration from MapVision? VectoStar preserves your historical data, GIS layers, treatment records, and operational workflows with a step-by-step methodology validated by your team.

What Your Agency Has Built Inside MapVision

Before discussing migration, it's worth being specific about what's at stake: sites, zones, trap locations, adult and larval surveillance records, treatment history, GIS layers, spray routes, catch basins, storm drains, service requests, operational notes, attachments, and historical reporting. A migration that loses any significant portion of this institutional knowledge is not a successful migration.

Your Data Is More Valuable Than Your Software

The five concerns agencies raise most often: (1) Losing historical data — addressed by a complete data inventory before anything moves. (2) Losing GIS layers — addressed by a dedicated GIS validation phase. (3) Breaking workflows — addressed by explicit workflow documentation. (4) Staff retraining — addressed by training built around your migrated data. (5) Reporting disruption — addressed by mapping reporting structures before go-live is approved.

How VectoStar Handles Migration

VectoStar uses a relational database architecture that preserves the relationships between operational records. Supported import formats include SQL database exports, CSV and Excel, ArcGIS Feature Services, Shapefiles, GeoJSON, KML/KMZ, and standard GIS feature layer exports. Undocumented proprietary formats are reviewed on a case-by-case basis.

Migration Methodology: Discovery to Go Live

  1. Discovery — Review your data categories, GIS inventory, workflows, and export formats.
  2. Data Review — Evaluate exported data for completeness and structure.
  3. Schema Mapping — Map each source field to VectoStar's data model.
  4. GIS Validation — Import and validate all GIS layers before operational data moves.
  5. Trial Migration — Import a representative subset into staging to confirm mappings.
  6. Customer Review — Your team reviews the staged data. Required before production.
  7. Production Migration — Full dataset migrated using the validated mapping.
  8. Verification — Record counts, relationships, and GIS rendering confirmed.
  9. Training — Built around your migrated data, not hypothetical examples.
  10. Go Live — Operations begin in VectoStar with ongoing support.

GIS Is the Foundation

VectoStar is built around GIS — not treating it as an add-on. When sites, zones, catch basins, spray routes, and surveillance stations are imported as GIS features first, every subsequent operational record can be spatially anchored. Learn more about GIS-first mosquito control.

Beyond Migration

Once migration is complete, agencies gain: AI-assisted reporting, GIS-first workflows, mobile field operations, dashboard analytics, public request management, Storm Drain Intelligence, and IoT integrations. See the full mosquito control software platform.

Request a Migration Assessment

Every agency's situation is different. Before discussing software, we'll review your current environment, GIS layers, workflows, and export formats. Request a free migration assessment — no commitment required.

Frequently Asked Questions

Can VectoStar migrate MapVision data?
Yes. VectoStar's migration methodology is specifically designed to evaluate and preserve your operational history from MapVision. We start with a technical review of your available export formats and data inventory before any migration work begins.
Will we lose our GIS information?
No — GIS preservation is a primary objective. VectoStar can import GIS data from ArcGIS Feature Services, Shapefiles, GeoJSON, KML/KMZ, and standard GIS feature layer exports. A dedicated GIS validation step runs before any operational data is migrated.
Can historical surveillance records be migrated?
Yes. Historical adult and larval surveillance records, trap counts, species identifications, and field notes are included in the migration scope. Our relational architecture preserves the links between surveillance data and the sites and zones they belong to.
Can treatment history be preserved?
Yes. Historical treatment records — including chemical applications, application rates, equipment details, and field conditions — are included in the migration scope wherever the source data is available in a structured export format.
Can our zones be migrated?
Yes. Service territories, treatment zones, spray areas, and operational boundaries can be migrated as GIS features and linked to the sites, routes, and records they contain.
Can ArcGIS data be imported?
Yes. VectoStar supports import from ArcGIS Feature Services, ArcGIS REST API layers, and standard Shapefile and GeoJSON exports from ArcGIS environments.
Can we validate the migration before going live?
Yes — this is a required step. After the trial migration, your agency's operational staff review the migrated data in a staging environment before any production go-live decision is made.
How long does a migration usually take?
Migration timelines vary based on data volume, GIS complexity, and the export formats available. A typical migration from initial discovery to production go-live takes 4–10 weeks. We provide a timeline estimate after the technical review.