Migrate from Unim to monday CRM

Unim Contact records map to Monday.com People. The standard name, email, phone, and address fields translate directly. Every bespoke custom field on the Contact ModelID is resolved against the DataType lookup before a Monday.com column of the matching type is created on the People board. Column dependency ordering in Monday.com (some column types require another column to exist first) is computed from the dependency graph before any records insert.

Unim Company records map to Monday.com Organizations. The Company name becomes the Organization name, and the domain field maps to the website column. All bespoke Company-level custom fields are created as Organization columns with the same dependency ordering rules applied as for People. Organization is created before People import so that link resolution between a Contact and its Company is satisfied at insert time.

Unim Deal records map to Monday.com's native Deals entity. Deal name, amount, stage, expected close date, and owner map to the corresponding Monday.com fields. Unim's bespoke deal-stage values are reproduced as Monday.com Deal Status column options, and the stage sequence is preserved as written. If Unim supports multiple deal pipelines, each pipeline becomes a separate Monday.com Deals board.

Unim Activity records are disaggregated by type. Call logs become a custom Column (number or text) on the linked People Item; emails become a Long Text column with email body content; meetings become a Date column with a text column for attendees; notes become a Long Text column. Activity-to-record linkage is preserved by updating the linked People Item in Monday.com rather than creating a separate Activity object, since Monday.com does not have a standalone Activity object equivalent. Historical timestamps are stored as custom Date columns.

Unim custom fields are discovered via the custom-fields API and catalogued with their DataType and ModelID references. Each custom field is mapped to a Monday.com column type using a type-mapping matrix (text fields to Text columns, date fields to Date columns, picklists to Dropdown or Tags columns, numeric fields to Numbers columns). Custom field dependencies in Monday.com are resolved from the dependency graph, and columns are created in topological order before any record data is inserted.

Unim bespoke object types beyond Contacts, Companies, and Activities are discovered during schema introspection and mapped to Monday.com equivalents. Simple custom objects with flat schemas become Monday.com boards with standard columns plus any bespoke column types. Custom objects with cross-references to Contacts or Organizations become separate boards with Item linking enabled. Relationship cardinality (1:1, 1:N, N:N) is documented from the Unim schema and reproduced as Monday.com Connect board links or mirror links. The admin receives a written schema map of the destination structure before data moves.

Unim owner IDs are scoped to the specific Unim instance and cannot be reused in Monday.com. We extract every distinct owner referenced on Contacts, Companies, Deals, and Activities and match by email address against the Monday.com workspace Team Members. Any owner with no matching Monday.com user is held in an orphan queue with the owner email listed; the customer provisions the corresponding Monday.com account before the record import phase resumes.

Unim file attachments are stored via the Files dimension and require a separate API call per attachment to retrieve the binary blob. We paginate file extraction to stay within Unim API rate limits, apply retry logic on 429 responses, and re-associate each file with the target Monday.com Item using the File column type. Original filenames and MIME types are preserved. Files without a resolvable parent Item are held in a separate reconciliation board for admin review.

Unim tag associations are extracted as join-table records (tag name plus source record ID). Tags are mapped to Monday.com Tags columns on the corresponding Items. Where the tag vocabulary is small and closed (industry labels, status tags), Tags columns are used; where tags represent open-ended classification, Label columns are used. The choice is confirmed with the customer during scoping.