Key takeaways
- Record volume matters, but mapping complexity often matters more.
- Count the costs that are not on the quote: your team’s testing time, overlapping licences and records that fail.
- Ask for a written mapping and a sample run of your own records before you commit.
Three pricing models
| Model | How it works | What to check |
|---|---|---|
| Per record | Priced by the number of records moved | What counts as a record, and whether attachments, notes and articles cost extra |
| Hourly | Time is billed | Who carries the risk when a run fails or the mapping changes |
| Fixed price | Agreed after a review of what you have | What is in scope, and what happens if volumes change |
What drives the cost
- Record volume: companies, contacts, tickets, replies and articles.
- Objects in scope: tickets only, or tickets plus knowledge base, custom objects and attachments.
- Mapping complexity: many custom fields, nested dropdowns, several brands, statuses that do not line up.
- Timing: a fixed cut-over date or a weekend window.
Not on the quote, but real: your team’s time to review the mapping and check the sample, paying for both helpdesks during the overlap, and records that fail and need fixing by hand.
Getting a DataGrine quote
DataGrine does not publish prices, because they depend on the drivers above. You can run the migration self-serve on the DataGrine platform or have the migration team handle it end to end, with 24/7 support either way, and a sample run on your own records comes before the full run. Tell us what you are moving.