Migrate your OnePageCRM data

Persons are the primary record in OnePageCRM. Standard fields include name, emails, phones, addresses, social URLs, and a Next Action date. Custom contact fields are fully supported. We export all fields including Tags and Lead Source. Note that email bodies and attachments are not available via export or API.

Company records are separate from contacts but linked. Export includes company name, phone, address, and custom company fields. We preserve the contact-to-organization linkage during migration by mapping the relationship to the destination's equivalent link table.

Deals are associated with contacts and include deal name, amount, pipeline, stage, close date, margin, commission, cost, and multi-month deal flags. Closed deals (Won/Lost) are a separate export dataset. We handle both Pending and Closed deal exports and map pipeline stages to the destination's stage options.

Admin-created custom fields for contacts must be pre-created in OnePageCRM before import. During migration scoping we verify that all source custom fields exist in the destination or are explicitly dropped. Field types and choice options require explicit mapping to avoid type mismatches.

Company-level custom fields behave identically to contact custom fields — must exist before data lands. We check schema parity and map to equivalent company custom fields in the destination, dropping any that lack a target.

Deal custom fields are included in the deal export. We map these to the destination's deal-level custom properties, flagging any that exceed character limits or use unsupported field types (e.g., multi-select if the destination uses single-select).

Tags are assigned to contacts. Both contact-level and deal-exported tags are included in exports. We carry tags through as labels or tags in the destination, preserving the flat tag namespace without transformation.

Statuses define where a contact is in the sales pipeline (e.g., Prospect, Qualified, Customer). The list is pre-populated but editable per organisation. We capture the full status taxonomy and map each to the destination's lifecycle stage or contact status field.

Classifies how a contact entered the CRM (e.g., website inquiry, phone call, referral). Pre-populated list editable per org. We preserve lead source as a contact property in the destination, creating new picklist values if the destination's taxonomy does not cover the source.

Template task sequences users assign to contacts. Only one email sequence per Autoflow. We do not migrate Autoflow workflows directly; instead we map saved action templates to the destination's task templates or checklist formats where supported.

Predefined Items represent products or services used in deal creation. They support grouping. We map these to the destination's product/catalog objects, preserving name, price, quantity, and grouping hierarchy.

Notes and call records attached to contacts are included in the 'Contacts (Inc. notes, calls, etc.)' export dataset. However, the export does not include email body content. We export notes as plain text and calls with duration and date, but email conversation threads require API-level extraction and are subject to rate limits.