Migrate from improveit 360 to Twenty CRM

Salesforce Contact maps to Twenty People. All standard fields (name, email, phone, job title, address) transfer directly. The AccountId lookup in Salesforce becomes companyId in Twenty — the parent Company record must import first so the foreign key resolves correctly.

Salesforce Account maps to Twenty Company. Standard fields (name, website, industry, employee count, annual revenue) transfer directly. ParentId hierarchy in Salesforce — where an Account can have a parent Account — has no native equivalent in Twenty; we flatten to a single company per record and preserve parent linkage in a custom text field.

Twenty has no native Lead object. All Salesforce Leads migrate to Twenty People with a custom lead_status field capturing the original Lead Status value. The original isConverted flag and convertedDate are preserved as custom fields if the Lead was previously converted to a Contact in improveit 360.

Salesforce Opportunity maps to Twenty Opportunity on a 1:1 basis. Deal name becomes Opportunity name, amount transfers as amount, close date maps to closeDate, and stage maps to stage. Stage probability and forecast category do not transfer — Twenty's Opportunity object does not have native probability fields.

Salesforce Tasks (calls, to-dos, follow-up items) migrate to Twenty Tasks. Subject, status, priority, due date, and description transfer directly as standard fields. The WhoId (Contact or Lead reference) resolves to the migrated People record via the source system ID stored in Source_System_ID__c, maintaining the original activity attribution across both systems.

Salesforce Events (meetings, appointments) convert to Twenty Tasks because Twenty has no native calendar Event object. The meeting subject becomes the Task subject, start time becomes due date, and the original duration is preserved in the description field. Activity history remains searchable in Twenty.

Salesforce Notes migrate to Twenty Notes with the same body text. Rich-text formatting is preserved where Salesforce NoteBody supports it. Notes attached to Contacts, Accounts, or Opportunities link to the migrated People, Company, or Opportunity record via the stored source system ID.

Salesforce Attachment records (files attached to records) have no direct Twenty equivalent. During migration, we download all attachment files to local storage, then re-upload them to Twenty's file storage system. After upload completes, we recreate the original attachment links on the corresponding People, Company, or Opportunity record using the stored source system ID cross-reference to ensure proper association.

improveit 360 custom objects (configured in Salesforce) migrate to Twenty custom objects. Custom object names are preserved. Custom field creation must happen in Twenty Settings → Data Model before the migration runs — we deliver a schema setup checklist as part of the migration plan.

improveit 360's project management objects (jobs, schedules, cost tracking, payments) are not native Salesforce objects — they are improveit 360-specific configurations. We audit which project objects exist in your instance and surface them as custom object candidates for Twenty. If your team uses these heavily, we recommend building them as Twenty custom objects post-migration.

Salesforce Users who own records resolve to Twenty Workspace Members by email match. The Twenty workspace must have users invited and active before migration so owner assignments can link correctly. Unmatched owners are flagged and assigned to a fallback user on your instruction.