First establish what your organisation actually uses
Inventory the PIX4Dmapper version, licence arrangement, active devices, operating systems, cameras, processing templates and delivered file types. Include recurring projects and the people responsible for them. A migration plan based only on “we make orthomosaics” misses dependencies such as multispectral indices, custom camera calibration, GCP conventions and downstream scripts.
PIX4D’s release documentation lists PIX4Dmapper 4.10.1 as a stable release dated 16 February 2026. That does not justify presenting every historical licence offer or cloud-processing route as current. Account-specific availability, support and migration options should be confirmed before procurement or decommissioning.
Map workflows to destinations, not product names
RGB aerial and terrestrial mapping may be candidates for PIX4Dmatic Standard. Where the same team needs terrain classification, advanced vectorisation and CAD-oriented work, evaluate Analyst or Pro. Agricultural multispectral work may point toward PIX4Dfields, but its nadir, GCP and CRS constraints must be accepted first.
| Existing requirement | Evaluation route | Migration caution |
|---|---|---|
| RGB aerial mapping | PIX4Dmatic Standard or Pro | Test camera calibration, GCPs, outputs and hardware |
| Survey vectorisation after mapping | PIX4Dmatic Analyst or Pro | Review plan split, seats and legacy PIX4Dsurvey transition |
| Multispectral crop mapping | PIX4Dfields or a specifically supported route | Nadir focus, no GCP marking and fixed CRS behaviour |
| Cloud processing | Current PIX4Dcloud pipeline | Do not assume legacy mapper cloud options or spectral support remain |
Cloud and multispectral dependencies need special attention
PIX4D documentation states that after 28 February 2026 PIX4Dcloud no longer supports processing multispectral or thermal images, including uploads through PIX4Dmapper. A team that relied on that route needs a tested alternative before changing its production process.
Separately, PIX4Dmatic’s current 2.X release notes describe supported thermal orthomosaic capabilities for Standard and Pro. That does not create a blanket migration path for every thermal or multispectral camera. Validate the exact sensor, metadata, radiometric outputs and intended deliverables.
Run a controlled pilot before switching production
Choose representative projects: a routine RGB site, a difficult reconstruction and each specialised spectral workflow. Preserve the original projects and outputs, then process the pilot in the target environment using documented settings.
- Compare camera calibration and georeferencing behaviour.
- Check GCP, checkpoint and coordinate transformations.
- Inspect completeness, orthomosaic seams and surface artifacts.
- Verify every required export in the recipient CAD, GIS or agriculture platform.
- Benchmark processing on the intended hardware.
- Record unsupported functions and decide whether to retain, replace or redesign that step.
Keep an archive and rollback route
Archive original images, project files, control, reports and final exports using a documented folder and naming structure. Do not assume a future application will reproduce every legacy result. Maintain the old environment only within its actual support and security conditions, and set a clear retirement point after the new workflow passes acceptance.