Migrate your Rooftop data
Small-team helpdesk with per-seat pricing starting at $49/month, good customer service ratings, and a small but positive review profile.
In its favor
Why people choose Rooftop
The signal that keeps Rooftop on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Small teams choose Rooftop because the per-seat starting price of $49/month is competitive for SMB budgets without requiring annual commitments or enterprise contracts.
Reviewers consistently praise the customer service quality, with an average customer service rating of 4.8 out of 5 across available Capterra reviews.
Users rate ease of use at 4.4 out of 5, indicating the platform has a straightforward onboarding curve that teams can navigate without extensive training.
Value for money scores around 4.0 to 4.1 out of 5 suggest customers feel the feature set matches the price point for small support teams.
Loading time complaints and slow search performance appear in G2 reviews, indicating the platform can become sluggish when handling larger ticket volumes or searching across historical data.
The limited review count of 11 verified reviews on Capterra suggests low market adoption, which may signal insufficient enterprise features or integrations for growing teams.
No public API documentation means teams requiring programmatic data access or third-party integrations face significant friction or must build custom solutions.
Reasons to switch
Why people leave Rooftop
The recurring reasons buyers give for replacing Rooftop. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Rooftop 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
Rooftop pricing overview
Rooftop uses a per-user, per-month pricing model with three tiers starting at $49 for Starter, $99 for Professional, and $199 for Enterprise. No free tier or free trial was documented in available public sources.
Starter
Tier 1 of 3
$49/user/month
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Rooftop's schedule — see our quote-based pricing →
What gets migrated
Rooftop object support
Object-by-object support for Rooftop migrations. Per-pair details surface during scoping.
Customers
Fully supportedCustomer records in Rooftop hold contact information and metadata. We map these to the destination system contacts object, preserving email, name, phone, and any custom properties found in the export.
Companies
Fully supportedCompany or account records are standard objects. We migrate company names, domains, and association fields, mapping them to the destination equivalent or merging into contacts where the target system lacks a separate account object.
Conversations
Fully supportedConversations represent the message thread attached to a ticket. We preserve message ordering, timestamps, sender attribution, and internal notes flag. HTML or plain-text formatting is normalized at import.
Agents
Fully supportedAgent profiles include name, email, role, and team assignment. We migrate agent records and reconstruct team and permission hierarchies in the destination system based on available export data.
Custom Ticket Fields
Mapping requiredCustom fields vary by Rooftop deployment. We inventory all custom field names and data types during scoping, then map each to destination custom fields or convert to standard properties where equivalents exist.
Tags
Mapping requiredTags applied to tickets for categorization are migrated as label or tag arrays. Where the destination system uses a different tagging model, we flatten or restructure the tag list to match the target schema.
Attachments
Mapping requiredFile attachments associated with tickets or conversations are migrated by URL reference or re-uploaded to the destination. Attachment size limits and supported file types may constrain the migration scope.
Knowledge Base Articles
Mapping requiredKB articles and categories are migrated where Rooftop exports them. Article body content is preserved, but internal article ID references are remapped to destination IDs.
| Object | Support | Notes |
|---|---|---|
| Customers | Fully supported | Customer records in Rooftop hold contact information and metadata. We map these to the destination system contacts object, preserving email, name, phone, and any custom properties found in the export. |
| Companies | Fully supported | Company or account records are standard objects. We migrate company names, domains, and association fields, mapping them to the destination equivalent or merging into contacts where the target system lacks a separate account object. |
| Conversations | Fully supported | Conversations represent the message thread attached to a ticket. We preserve message ordering, timestamps, sender attribution, and internal notes flag. HTML or plain-text formatting is normalized at import. |
| Agents | Fully supported | Agent profiles include name, email, role, and team assignment. We migrate agent records and reconstruct team and permission hierarchies in the destination system based on available export data. |
| Custom Ticket Fields | Mapping required | Custom fields vary by Rooftop deployment. We inventory all custom field names and data types during scoping, then map each to destination custom fields or convert to standard properties where equivalents exist. |
| Tags | Mapping required | Tags applied to tickets for categorization are migrated as label or tag arrays. Where the destination system uses a different tagging model, we flatten or restructure the tag list to match the target schema. |
| Attachments | Mapping required | File attachments associated with tickets or conversations are migrated by URL reference or re-uploaded to the destination. Attachment size limits and supported file types may constrain the migration scope. |
| Knowledge Base Articles | Mapping required | KB articles and categories are migrated where Rooftop exports them. Article body content is preserved, but internal article ID references are remapped to destination IDs. |
Gotchas
What to watch for in Rooftop migrations
Issues we've hit on past Rooftop migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No documented public API for data export
Slow search and loading performance impacts data review
Small verified review base limits migration confidence
| Severity | Issue |
|---|---|
| High | No documented public API for data export |
| Medium | Slow search and loading performance impacts data review |
| Low | Small verified review base limits migration confidence |
Leaving Rooftop?
Where Rooftop customers move next
7 destinations Rooftop can migrate to.
How a Rooftop migration works
Four steps, Rooftop-specific
Connect
Not publicly documented into Rooftop. Scopes limited to read-only on the data we move.
Map
We translate Rooftop-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Rooftop quirks before production.
Migrate
Full migration with Rooftop rate-limit handling. Rollback available throughout.
FAQ
Rooftop migration FAQ
Answers to the questions buyers ask most during Rooftop migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Rooftop migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther helpdesks we support
Ready when you are
Migrate Rooftop.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Rooftop setup and destination — written quote back within a business day.