Migrate your Eddy data
All-in-one HRMS platform for small businesses combining onboarding, payroll, PTO tracking, and document management under a flat per-employee pricing model.
In its favor
Why people choose Eddy
The signal that keeps Eddy on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Low monthly cost with predictable per-employee pricing ($4–$10/user/month plus base fee) appeals to small businesses avoiding per-seat enterprise costs.
Single platform covering onboarding, payroll, PTO, and document storage reduces tool fragmentation that plagues growing teams.
Straightforward setup with guided onboarding workflows documented in reviews as a reason teams choose and stay on Eddy.
Employee directory and self-service portal give small HR teams a centralized record of employment data without spreadsheets.
Capterra reviewers highlight excellent customer support as a differentiating factor compared to competitors with similar pricing.
Reporting limitations frustrate teams requiring custom HR analytics—reviewers explicitly note needing workarounds for basic workforce reports.
Incomplete payroll integration means users manage HR records in Eddy but run payroll separately, reducing the all-in-one value proposition.
Limited customization of workflows and fields forces growing companies to adopt workarounds that do not scale past 50–100 employees.
Some users note missing features common in dedicated payroll or benefits platforms, requiring data re-entry between systems.
Custom field support is restricted, pushing companies with industry-specific HR requirements toward more flexible alternatives.
Reasons to switch
Why people leave Eddy
The recurring reasons buyers give for replacing Eddy. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Eddy 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
Eddy pricing overview
Eddy uses a per-employee plus monthly base fee model. Starter starts at approximately $4 per active employee plus $50/month; Growth increases to approximately $8 per employee plus $75/month. Premium pricing is negotiated based on company size and required features.
Starter
Tier 1 of 3
$4/user/month + $50/month base
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Eddy's schedule — see our quote-based pricing →
What gets migrated
Eddy object support
Object-by-object support for Eddy migrations. Per-pair details surface during scoping.
Employees
Fully supportedCore employee records with name, contact, job title, department, hire date, and employment status. Eddy stores these as the primary HR object. We migrate Employee records 1:1 with field-level mapping to destination HRMS field names.
PTO Balances
Fully supportedTime-off tracking including accrued balances, requests, and approval statuses. PTO policies are tied to the employee record. We preserve balance snapshots and carry-forward rules during migration.
Documents
Fully supportedEmployee documents such as offer letters, contracts, and signed agreements stored per employee. Eddy supports PDF and standard document formats. We migrate document blobs and preserve file names and associations.
Onboarding Workflows
Mapping requiredOnboarding step checklists and task assignments. Workflow structure varies by plan. We map active tasks and completed steps to the destination's equivalent onboarding object, flagging any steps that cannot be represented.
Training Records
Mapping requiredTraining completion tracking tied to employees. Field naming and completion-date storage vary. We extract training history and map to the destination's training/certification object, preserving completion status and dates.
Employee Directory
Fully supportedThe directory view is derived from employee records. We migrate the underlying employee data that populates the directory, preserving organizational hierarchy information.
Payroll Data
Mapping requiredReviewers report incomplete integration between Eddy's HR and payroll modules. Pay run history export requires manual steps or CSV export where available. We extract available payroll records and flag gaps in the migration scope.
Company Settings
Mapping requiredOrg-level settings including departments, locations, and policy configurations. These export in limited formats. We map department names and locations, noting any policy settings that require manual reconfiguration at destination.
| Object | Support | Notes |
|---|---|---|
| Employees | Fully supported | Core employee records with name, contact, job title, department, hire date, and employment status. Eddy stores these as the primary HR object. We migrate Employee records 1:1 with field-level mapping to destination HRMS field names. |
| PTO Balances | Fully supported | Time-off tracking including accrued balances, requests, and approval statuses. PTO policies are tied to the employee record. We preserve balance snapshots and carry-forward rules during migration. |
| Documents | Fully supported | Employee documents such as offer letters, contracts, and signed agreements stored per employee. Eddy supports PDF and standard document formats. We migrate document blobs and preserve file names and associations. |
| Onboarding Workflows | Mapping required | Onboarding step checklists and task assignments. Workflow structure varies by plan. We map active tasks and completed steps to the destination's equivalent onboarding object, flagging any steps that cannot be represented. |
| Training Records | Mapping required | Training completion tracking tied to employees. Field naming and completion-date storage vary. We extract training history and map to the destination's training/certification object, preserving completion status and dates. |
| Employee Directory | Fully supported | The directory view is derived from employee records. We migrate the underlying employee data that populates the directory, preserving organizational hierarchy information. |
| Payroll Data | Mapping required | Reviewers report incomplete integration between Eddy's HR and payroll modules. Pay run history export requires manual steps or CSV export where available. We extract available payroll records and flag gaps in the migration scope. |
| Company Settings | Mapping required | Org-level settings including departments, locations, and policy configurations. These export in limited formats. We map department names and locations, noting any policy settings that require manual reconfiguration at destination. |
Gotchas
What to watch for in Eddy migrations
Issues we've hit on past Eddy migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Contract data cannot be exported via API
Reporting limitations require workarounds
Payroll and HR integration is incomplete
Per-employee pricing counts all employees including inactive
| Severity | Issue |
|---|---|
| High | Contract data cannot be exported via API |
| Medium | Reporting limitations require workarounds |
| Medium | Payroll and HR integration is incomplete |
| Low | Per-employee pricing counts all employees including inactive |
Leaving Eddy?
Where Eddy customers move next
5 destinations Eddy can migrate to.
How a Eddy migration works
Four steps, Eddy-specific
Connect
Not publicly documented in detail. into Eddy. Scopes limited to read-only on the data we move.
Map
We translate Eddy-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Eddy quirks before production.
Migrate
Full migration with Eddy rate-limit handling. Rollback available throughout.
FAQ
Eddy migration FAQ
Answers to the questions buyers ask most during Eddy migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Eddy migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther HR systems we support
Ready when you are
Migrate Eddy.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Eddy setup and destination — written quote back within a business day.