Migrate your karmaCRM data

Contacts is a first-class object with full CRUD via the REST API and native CSV export. The knowledge base documents export options including filtered subsets and full-account dumps. We map standard contact fields (name, email, phone, address) directly and preserve custom field values as text.

Companies can be exported to CSV from the UI with role-based permission controls. We replicate the company name, domain, address, and any custom fields stored against the company record. The export respects pagination and filter state in the UI.

The support docs refer to Deals and Gigs interchangeably. Deals track pipeline values, stages, and associations to contacts and companies. We map deal name, value, stage, owner, and created/updated dates. Stage names are preserved as custom properties if the destination does not share the same stage vocabulary.

Tasks support assignment, due dates, status, and priority. The platform coordinates tasks across the team and event calendar. We replicate task records with their linked contact or company association and preserve due dates and completion status.

Events represent calendar entries with time, duration, attendees, and linked contact or company associations. We map event records including title, start/end times, location, and attendee lists into the destination calendar or activity log.

Email campaigns are available on Pro and Premium tiers. Campaign records include audience lists, subject lines, send dates, and open/click stats. We import campaign metadata and statistics; email body content and design assets require re-upload at the destination since HTML is not always cleanly extractable.

User records include name, email, role, settings, and API token. Active user assignments on Deals, Tasks, and Events are remapped to matching users in the destination. Role structures differ between platforms so we map role names to the nearest equivalent or to a default owner.

karmaCRM supports fully customizable fields across screens, tabs, labels, and background colors. Custom field definitions and values are preserved as freeform name-value pairs during migration. The destination must support custom field creation or the values are appended as a structured note.

The platform stores files and attachments linked to contacts, companies, and deals, but the backup/export documentation does not describe a programmatic attachment export path. We flag attachments as a manual step requiring the customer to download originals from the UI and re-upload to the destination after primary record migration.

karmaCRM integrates with Google Calendar/Contacts and MailChimp. Integration configurations and OAuth tokens do not transfer between platforms. We document which integrations are active so they can be reconfigured in the destination CRM manually.

Tags can be applied to contacts and companies to categorize records. Tag names and associations are preserved as custom multi-select properties or native tags in the destination.

The support knowledge base lists a Webhooks section with 5 articles, indicating webhook configuration exists, but the webhook definitions are not exportable via the standard API. We document active webhook URLs so they can be recreated in the destination system.