Migrate from MarketSharp to Twenty CRM

MarketSharp leads map to Twenty's People object. Every lead field — name, email, phone, address — translates directly. Original create date and last-modified date migrate as custom datetime fields since Twenty's CreatedAt reflects migration time, not source creation time. Owner resolves by email match against invited Twenty workspace members.

MarketSharp customers with closedWon status map to Twenty People with a customer status indicator. Historical deal history attaches via the People-Opportunity relation. The customer flag from MarketSharp migrates as a custom select field on the People record for segmentation clarity in Twenty.

MarketSharp company records map to Twenty's Companies object. Company name, domain, industry, employee count, and annual revenue migrate as direct field mappings. Parent-child company hierarchies in MarketSharp translate to Twenty's Parent Company relation using the Companies.id foreign key. Multi-company associations per contact collapse to a primary company link.

MarketSharp opportunities map to Twenty's Opportunities object. Each opportunity links to a Companies record (via companyId) and optionally to People records (via personId for primary contact). Opportunity amount, stage name, expected close date, and owner all map to the corresponding Twenty fields. The opportunity stage name migrates as a custom select or maps to Twenty's built-in stage options.

MarketSharp appointments — meetings, site visits, estimate presentations — migrate as Twenty Tasks. Each task inherits the linked People or Companies record, the assigned owner, and the scheduled datetime. Task type (call, meeting, site visit) maps to a custom select field on the Task. Completed status and completion notes migrate in the Task body field.

MarketSharp custom lead fields (remodeler type, trade specialty, project source) require corresponding Twenty custom fields created before import. We generate a field creation plan with field names, types, and pick-list options so Twenty's schema is ready before data lands. Fields must exist before the CSV import can populate them per Twenty's import constraint.

MarketSharp project or job records tied to closed opportunities migrate as Opportunities with a project status flag. Project-specific fields like job address, crew assignment, and contract amount map to Opportunity fields and custom fields on the Opportunities object. Historical project data preserves original close dates for reporting continuity.

MarketSharp file attachments on leads, customers, or opportunities re-upload to Twenty and attach to the corresponding People, Companies, or Opportunities record. File size and format are preserved. Inline images in notes download and rehost where the source exposes them. File associations link via Twenty's attachment model on the record.

MarketSharp users and owners resolve to Twenty Workspace Members by email match. Unmatched owners flag before migration — your team invites them to Twenty or assigns records to a fallback member. The ownerId on each record populates from the resolved WorkspaceMember.id after the members list is confirmed.

MarketSharp call logs and activity records migrate as Twenty Tasks with Type set to Call. Each task links to the parent People record, preserves the original timestamp, and surfaces the owner who logged the activity. Subject and body populate from MarketSharp's activity description field.