Migrate from solve 360 to Twenty CRM

Solve 360 Contacts map directly to Twenty Person records. Standard fields (name, email, phone, address) migrate with type preservation. Custom fields on the Contact record migrate as Twenty Person custom fields, which we pre-create via the /metadata GraphQL API before import. The Contact's linked Company becomes a Company record with the relationship preserved via the Person's companyLink field.

Solve 360 Companies map to Twenty Company records. Company name, domain, and address fields migrate directly. Custom fields on the Company record pre-create as Twenty Company custom fields via the /metadata API. If the same company domain appears across multiple Contact records in Solve 360, we deduplicate by domain and attach all Persons to the single Company record in Twenty.

Solve 360 Tasks map to Twenty Task records with Status, Priority, due date, and assignee preserved. The Task's linked Contact or Company becomes the Task's TaskTargetable record (Person or Company) via the Twenty activity model. Time tracking data from Solve 360 Task entries migrates as Twenty Task custom fields capturing duration, billing flag, and time-entry date.

Solve 360 Follow-ups are time-stamped activity entries tied to a Contact or Company. If the Follow-up has a scheduled date without a duration, we migrate it as a Twenty Event with StartDateTime and EndDateTime set to the Follow-up timestamp. If it has a duration, we migrate it as a Task with the completion date preserved. The original Follow-up type and notes migrate as Task description.

Solve 360 Support Requests track issues end-to-end against a Contact or Company. We migrate Support Requests as Twenty Tasks linked to the Person or Company record, with status transitions preserved in Task custom fields. If the customer uses a dedicated support workflow, we can create a Case custom object in Twenty matching the Support Request schema, which requires pre-creating the custom object via the /metadata API before import.

Solve 360 Time Records attach to Tasks, Site Notes, Calls, and Meetings with duration, date, billing flag, and parent object. We flatten time records into the parent Task record as custom fields (time_duration_minutes, time_billing_flag, time_entry_date). The association to the parent object is preserved via the TaskTargetable relationship on the Twenty Task.

Solve 360 Pipelines and their stages are configurable. We export the full pipeline structure (stage names, order, probabilities) and create matching Opportunity stages in Twenty via the /metadata API before Opportunity import. Each stage maps as a Stage field on the Twenty Opportunity object with the original probability preserved as a custom field.

Solve 360 Users are both system actors and assignment targets. We export the user list and map owner IDs to Twenty WorkspaceMember records by email match. Any Solve 360 owner without a matching Twenty WorkspaceMember goes to a reconciliation queue for the customer to provision before record import resumes. Inactive Solve 360 users are mapped as inactive WorkspaceMembers in Twenty.

Solve 360 supports user-defined custom fields on Contacts and Companies with types including text, number, date, and selection. We export field definitions and values, then create matching custom fields on the Twenty Person or Company object via the /metadata API with the correct field type (text, number, date, select). Selection fields with multiple options migrate as Twenty select fields with the original option values preserved.

Solve 360 Tags label Contacts, Companies, and other records. We export all tag values and re-apply them as Twenty native tags on the Person, Company, or Task record. The tagging association per record is preserved using Twenty's tag API.

Attachments on Contacts, Companies, Tasks, and Support Requests are downloaded as files and re-uploaded to Twenty via the GraphQL API, re-linked to the parent record (Person, Company, or Task) using the attachment's name, type, size, and upload date metadata. Files over 50 MB require chunked upload handling.