Migrate your Results data
A CRM platform with limited publicly available data; migration specifics require direct verification.
In its favor
Why people choose Results
The signal that keeps Results on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Tight QuickBooks Desktop and Online sync — Results positions itself explicitly as a 'must-have for any business that uses QuickBooks', eliminating double-entry between CRM and accounting.
All-in-one SMB suite covering CRM, Sales, Business, and Field Service Management modules in one platform, reducing tool sprawl for service operators.
Field Service module includes mobile photo capture (before/after/during), signature capture, and onsite checklists at $10/user/month, an unusually low add-on price.
Choice of one-time perpetual license OR rent-to-own monthly subscription — no long-term contract requirement, accommodating SMB cash flow preferences.
Pre-built integrations beyond QuickBooks include AvaTax, Zapier, Outlook, Gmail, SMS/Text, WhatsApp, and Calendly — covering common SMB communications and tax-compliance stacks.
Architecture limits — the platform is positioned for SMBs and not designed to scale beyond ~15 users or 15,000 contacts, prompting growing teams to migrate to enterprise platforms.
No public REST API documentation or developer portal — custom integrations beyond the published connectors depend on vendor engagement or Zapier middleware.
QuickBooks-centric integration story leaves teams running NetSuite, Xero, or Sage looking elsewhere for native bidirectional accounting sync.
Heavy reliance on Windows and Office desktop environments may not fit fully browser-native or macOS/Linux remote workforces.
Limited public review volume on G2 and a small community footprint make benchmarking and peer-comparison harder than for category leaders.
Reasons to switch
Why people leave Results
The recurring reasons buyers give for replacing Results. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Results 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
Results pricing overview
Results uses per-user monthly pricing with module-based tiers per Capterra: CRM at $29/user/month, Sales at $59/user/month, Business at $89/user/month, and Field Service Management as a $10/user/month add-on. A one-time perpetual license is also offered as an alternative to monthly subscription, with no long-term contract requirement on the subscription option. A free trial is available; specific duration is not published.
CRM
Tier 1 of 5
$29/user/month
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Results's schedule — see our quote-based pricing →
What gets migrated
Results object support
Object-by-object support for Results migrations. Per-pair details surface during scoping.
Contacts
Fully supportedContacts are the primary object across the CRM module. We export with name, email, phone, address, and custom fields preserved 1:1.
Companies
Fully supportedCompany/account records link contacts, deals, and projects. We preserve company-to-contact associations during migration.
Deals (Opportunities)
Fully supportedOpportunities with stage, value, expected close date export from the Sales module. Custom pipeline stages export as configuration data.
Leads
Mapping requiredLeads are tracked alongside Contacts. Where the destination separates Lead and Contact objects, we map by stage; where it does not, we merge into Contacts with a lifecycle property.
Activities
Fully supportedActivities (calls, emails, meetings, tasks) export with timestamp, owner, and parent record association preserved.
Notes
Fully supportedFree-text notes attached to contacts, companies, deals, and projects export 1:1.
Custom Fields
Mapping requiredCustom fields per object export with name and type. We map each to the destination's custom field schema during scoping.
Quotes / Estimates / Sales Orders
Mapping requiredSales module documents (quotes, estimates, sales orders, purchase orders) export with line items. Tax and pricing rule logic is module-specific and may require reconfiguration in the destination.
Invoices (via QuickBooks)
Mapping requiredInvoices live in QuickBooks rather than Results itself in most setups. Migration scoping must coordinate which system holds invoicing as the source of truth.
Field Service Jobs
Mapping requiredField Service Management jobs include scheduling, technician assignment, photo and signature attachments, and checklist completions. We map jobs to destination FSM objects, preserving attachments and capturing the checklist results as structured notes.
Attachments (Photos, Signatures, Documents)
Mapping requiredField-captured photos, signatures, and document attachments export as binary files. We re-attach in the destination using migrated record IDs as keys.
Users
Mapping requiredUser accounts export with role, email, and permissions. We map active users to destination accounts and flag inactive ones for optional import.
| Object | Support | Notes |
|---|---|---|
| Contacts | Fully supported | Contacts are the primary object across the CRM module. We export with name, email, phone, address, and custom fields preserved 1:1. |
| Companies | Fully supported | Company/account records link contacts, deals, and projects. We preserve company-to-contact associations during migration. |
| Deals (Opportunities) | Fully supported | Opportunities with stage, value, expected close date export from the Sales module. Custom pipeline stages export as configuration data. |
| Leads | Mapping required | Leads are tracked alongside Contacts. Where the destination separates Lead and Contact objects, we map by stage; where it does not, we merge into Contacts with a lifecycle property. |
| Activities | Fully supported | Activities (calls, emails, meetings, tasks) export with timestamp, owner, and parent record association preserved. |
| Notes | Fully supported | Free-text notes attached to contacts, companies, deals, and projects export 1:1. |
| Custom Fields | Mapping required | Custom fields per object export with name and type. We map each to the destination's custom field schema during scoping. |
| Quotes / Estimates / Sales Orders | Mapping required | Sales module documents (quotes, estimates, sales orders, purchase orders) export with line items. Tax and pricing rule logic is module-specific and may require reconfiguration in the destination. |
| Invoices (via QuickBooks) | Mapping required | Invoices live in QuickBooks rather than Results itself in most setups. Migration scoping must coordinate which system holds invoicing as the source of truth. |
| Field Service Jobs | Mapping required | Field Service Management jobs include scheduling, technician assignment, photo and signature attachments, and checklist completions. We map jobs to destination FSM objects, preserving attachments and capturing the checklist results as structured notes. |
| Attachments (Photos, Signatures, Documents) | Mapping required | Field-captured photos, signatures, and document attachments export as binary files. We re-attach in the destination using migrated record IDs as keys. |
| Users | Mapping required | User accounts export with role, email, and permissions. We map active users to destination accounts and flag inactive ones for optional import. |
Gotchas
What to watch for in Results migrations
Issues we've hit on past Results migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
QuickBooks-linked records have dual sources of truth
Suite is not architected to scale beyond ~15 users / 15K contacts
No documented public REST API
Field Service photos and signatures require separate binary extraction
| Severity | Issue |
|---|---|
| High | QuickBooks-linked records have dual sources of truth |
| Medium | Suite is not architected to scale beyond ~15 users / 15K contacts |
| Medium | No documented public REST API |
| Medium | Field Service photos and signatures require separate binary extraction |
Leaving Results?
Where Results customers move next
12 destinations Results can migrate to.
How a Results migration works
Four steps, Results-specific
Connect
Not publicly documented — vendor relies on pre-built integrations into Results. Scopes limited to read-only on the data we move.
Map
We translate Results-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Results quirks before production.
Migrate
Full migration with Results rate-limit handling. Rollback available throughout.
FAQ
Results migration FAQ
Answers to the questions buyers ask most during Results migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Results migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Results.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Results setup and destination — written quote back within a business day.