Migrate your solve 360 data

Contacts are the primary person record in Solve 360 with fields for name, email, phone, address, and lifecycle properties. We export all standard fields plus any user-defined custom fields and preserve the relationship links to the parent Company record.

Companies are the primary organizational record. They carry standard fields (name, domain, address) plus custom fields. We preserve company-level attributes and re-link child Contact records in the destination system.

Tasks are the work-unit object in Solve 360, supporting status, priority, due date, assignee, and time tracking. We export task records with their metadata and carry over status values by mapping them to destination equivalents.

Follow-ups are a distinct activity type tied to contacts or companies. We export them as time-stamped activity records and map them to the destination CRM's activity or engagement object.

Support requests track ongoing issues end-to-end against a contact or company. We preserve the full request history including status transitions, descriptions, and linked conversations.

Time records attach to tasks, site notes, calls, and meetings. We export duration, date, billing flag, and associated parent object so time can be reconstructed at the destination.

Users in Solve 360 are both system actors and assignment targets. We export the user list and map owner IDs to destination user IDs, flagging any orphaned assignments where the source user does not exist in the destination.

Solve 360 supports user-defined custom fields on Contacts and Companies. Field types include text, number, date, and selection. We export field definitions and values, then create matching custom fields at the destination or map to existing fields of compatible type.

Pipelines and their stages are configurable in Solve 360. We export the full pipeline structure (stage names, order, probability) and map opportunities to the destination pipeline, creating the pipeline if it does not exist.

Tags in Solve 360 label contacts, companies, and other records. We export all tags and re-apply them as native tags or labels at the destination, preserving the tagging associations per record.

Attachments on contacts, companies, tasks, and support requests are downloaded as files and re-uploaded to the destination, re-linked to the parent record. File metadata (name, type, size, upload date) is preserved where available.

Workflows in Solve 360 define automated sequences of tasks, notifications, and assignments. We export workflow definitions as structured configuration and advise customers to manually recreate them at the destination, as automation engines vary significantly between platforms.