Switching is the point
Self-serve CSV import (available now)
Every Glime workspace imports CSV exports as they come out of the old system: Settings → Your data → Import from another CRM. There is no reordering columns in Excel first:
- Columns are matched by header name (HubSpot's "Company name", Salesforce's "Account Name", a "First name" and "Last name" pair), and you see the mapping and a preview before anything is written. Change any match you disagree with.
- Duplicates are skipped: an account by name (ignoring "Inc", "LLC" and the like), a contact by email, a deal by name and account. Running the same file twice adds nothing.
- Every import can be undone on its own. Settings lists each import with what it created; Undo removes exactly those records and nothing anyone typed. The sample records a new workspace starts with are an import too, so you can clear them in one click before bringing your own.
- An import lands in one transaction and is recorded in the audit trail. A file that fails halfway leaves nothing behind.
Products go in through the Quote Builder's catalog import, which takes CSV or Excel, so quotes are priced from your own price list from the first day.
From HubSpot, directly (available now)
Skip the export: paste a HubSpot private-app token in Settings → Your data → Move from HubSpot directly and Glime reads your companies, contacts and deals through HubSpot's own API, so each contact and deal arrives already linked to its company. It is one import, so one Undo removes it. The token is used for that read and never stored, and nothing is written back to HubSpot. This is a move, not a sync: Glime does not keep the two in step afterwards.
| From | Export path | Maps to Glime |
|---|---|---|
| Salesforce | Setup → Data Export, or a report exported as CSV | Accounts, Contacts, Opportunities, Leads; products through the catalog import |
| HubSpot | The direct move above, or CRM → Import/Export → Export views as CSV | Companies → Accounts, Contacts, Deals → Opportunities |
| Microsoft Dynamics | Advanced Find → Export to Excel, saved as CSV | Accounts, Contacts, Opportunities, Leads |
Scripted migration
A migration script can use the same import the app uses: POST /api/v1/_imports
with an object and rows in Glime's column order. It skips duplicates the same way, so a script
can re-run safely, and DELETE /api/v1/_imports/{id} undoes a run. It needs an Admin's
signed-in session today; key-authenticated API access is on the
developer roadmap.
White-glove migration (paid onboarding)
From $1,500 flat. We take your export (or API credentials), then map, deduplicate, migrate, and verify — including opportunity history and open quotes rebuilt as versioned Glime quotes. Typical timeline: one week, zero downtime, parallel-run before cutover.
What about getting out?
The same door swings both ways: one-click full export, documented format, published exit process. We'd rather earn the renewal.