Migrate your SortScape data
iOS-first field service CRM purpose-built for garden and lawn care businesses, with Xero invoicing built in.
In its favor
Why people choose SortScape
The signal that keeps SortScape on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Purpose-built for gardening businesses — customers describe it as the only tool that actually matches how lawn and garden crews operate day-to-day.
Stable pricing with no surprise increases — reviewers explicitly contrast SortScape with competitors who raised prices repeatedly before switching.
Xero integration streamlines invoicing — multiple reviewers cite the ability to link schedules directly to Xero as saving significant administrative time.
Australian-based support team with fast response — local support is highlighted as a differentiator for Australian garden maintenance businesses choosing SortScape.
Low barrier to entry for small operators — a solo landscaper managing 100 clients describes the tool as replacing their entire paper-based system.
iOS mobile app requires frequent restarts — at least one reviewer notes the iPhone app becomes sluggish and needs regular reloading to stay functional.
Mapping features missing from the mobile app — route visualization and map interactions are available on desktop only, forcing field staff to switch devices.
Export functionality locked to desktop — only administrators on desktop screens can export data, which creates friction for teams working primarily from mobile devices.
Limited platform ecosystem — SortScape integrates primarily with Xero, leaving businesses that use other accounting platforms with manual workarounds.
Reasons to switch
Why people leave SortScape
The recurring reasons buyers give for replacing SortScape. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where SortScape fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
SortScape pricing overview
SortScape offers three tiers: a per-user plan at $11/month per user, and two flat-rate plans at $45 and $79/month, designed to scale with team size. The flat-rate tiers are more cost-effective for teams with multiple users.
Plan 1
Tier 1 of 3
$11/user/month
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on SortScape's schedule — see our quote-based pricing →
What gets migrated
SortScape object support
Object-by-object support for SortScape migrations. Per-pair details surface during scoping.
Customers
Fully supportedCustomers export cleanly as a CSV from the admin desktop panel. Name, contact details, address, and notes fields map 1:1 to standard CRM contact schemas. We preserve all custom fields stored as text columns in the export.
Jobs
Fully supportedJob records export as part of the visit CSV. Each job includes its assigned customer, description, status, and pricing. We split these into separate Job and Visit objects on the destination side where the target schema distinguishes them.
Visits
Fully supportedVisits export from the Schedule page as a CSV file containing visit date, time, customer, job details, and status. This is the primary unit of work in SortScape and migrates cleanly. Export is desktop-only; administrators only.
Route Optimizations
Not in this platformRoute optimization settings are computed locally within the SortScape app and are not stored as persistent data. The optimization result — the reordered visit sequence — is transient. We do not migrate this object; we recommend re-running route optimization on the destination platform post-migration.
Schedules
Mapping requiredSchedules are structured as ordered lists of visits per day or per crew. We extract visit date and sequence from the CSV and reconstruct the schedule as date-grouped task lists in the destination, preserving visit order where the target allows sequential task ordering.
User Assignments
Mapping requiredSortScape crews and user names appear in the visit CSV but there is no separate user directory export. We extract crew assignments from visit records and map them to users in the destination, creating new user accounts if needed.
Xero Invoices
Mapping requiredSortScape links directly to Xero for invoicing. Invoice IDs and amounts exist in SortScape records but reference Xero's own objects. We preserve the invoice amount, date, and customer association, but the live Xero linkage does not transfer. Customers must re-connect Xero on the destination platform.
Custom Fields
Mapping requiredSortScape supports custom fields on customer and job records. These appear as additional columns in the CSV export if configured by the admin. We map each custom column to a corresponding custom field on the destination object, renaming where naming conventions differ.
| Object | Support | Notes |
|---|---|---|
| Customers | Fully supported | Customers export cleanly as a CSV from the admin desktop panel. Name, contact details, address, and notes fields map 1:1 to standard CRM contact schemas. We preserve all custom fields stored as text columns in the export. |
| Jobs | Fully supported | Job records export as part of the visit CSV. Each job includes its assigned customer, description, status, and pricing. We split these into separate Job and Visit objects on the destination side where the target schema distinguishes them. |
| Visits | Fully supported | Visits export from the Schedule page as a CSV file containing visit date, time, customer, job details, and status. This is the primary unit of work in SortScape and migrates cleanly. Export is desktop-only; administrators only. |
| Route Optimizations | Not in this platform | Route optimization settings are computed locally within the SortScape app and are not stored as persistent data. The optimization result — the reordered visit sequence — is transient. We do not migrate this object; we recommend re-running route optimization on the destination platform post-migration. |
| Schedules | Mapping required | Schedules are structured as ordered lists of visits per day or per crew. We extract visit date and sequence from the CSV and reconstruct the schedule as date-grouped task lists in the destination, preserving visit order where the target allows sequential task ordering. |
| User Assignments | Mapping required | SortScape crews and user names appear in the visit CSV but there is no separate user directory export. We extract crew assignments from visit records and map them to users in the destination, creating new user accounts if needed. |
| Xero Invoices | Mapping required | SortScape links directly to Xero for invoicing. Invoice IDs and amounts exist in SortScape records but reference Xero's own objects. We preserve the invoice amount, date, and customer association, but the live Xero linkage does not transfer. Customers must re-connect Xero on the destination platform. |
| Custom Fields | Mapping required | SortScape supports custom fields on customer and job records. These appear as additional columns in the CSV export if configured by the admin. We map each custom column to a corresponding custom field on the destination object, renaming where naming conventions differ. |
Gotchas
What to watch for in SortScape migrations
Issues we've hit on past SortScape migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Export is desktop-only and admin-restricted
Route optimization settings do not persist as data
Xero invoice links break on migration
| Severity | Issue |
|---|---|
| High | Export is desktop-only and admin-restricted |
| Medium | Route optimization settings do not persist as data |
| Medium | Xero invoice links break on migration |
Leaving SortScape?
Where SortScape customers move next
12 destinations SortScape can migrate to.
How a SortScape migration works
Four steps, SortScape-specific
Connect
Not publicly documented into SortScape. Scopes limited to read-only on the data we move.
Map
We translate SortScape-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate SortScape quirks before production.
Migrate
Full migration with SortScape rate-limit handling. Rollback available throughout.
FAQ
SortScape migration FAQ
Answers to the questions buyers ask most during SortScape migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your SortScape migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate SortScape.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your SortScape setup and destination — written quote back within a business day.