Salesforce to Twenty CRM migration
Move from Salesforce to Twenty CRM, every record mapped and counted
Your accounts, contacts, opportunities, custom objects, notes, tasks and files move into Twenty with the links between them, in Twenty’s cloud or on your own server. Your data model is built in Twenty first, then a test run on a sample of your own records. Before you switch, every object is counted in Salesforce and again in Twenty, and you sign the report.
- Free 30-minute call
- No obligation
- Reply within 2 business days
Updated · by TaskRhino
Salesforce
- Accounts
- Contacts
- Opportunities
- Custom objects
- Activities
- Files
Twenty
- Accounts1,2401,240
- Contacts3,8753,875
- Opportunities912912
- Custom objects2,6042,604
- Activities14,30614,306
- Files2,1182,118
Chapter 1 of 6Safely?
Can you move my Salesforce data into Twenty safely?
Yes, when four things are planned: Twenty’s data model built before any record loads, the links between records, the history and files Twenty’s file import cannot carry, and the limits of your Salesforce edition. The numbers below are the ones that catch most teams out. Then size your own move: six taps.
- 10,000
records a file: all that Twenty’s file import takes. We load through Twenty’s API instead, in batches of 60, with every link set.
- 0
fields or select options a Twenty import creates. We build your objects, fields and options from the signed data map first.
- 18
characters in the Salesforce ID we keep in a unique field on every Twenty record, so each one can be traced back and every link rebuilt.
- 2
counts per object, one in Salesforce and one in Twenty, before you switch Salesforce off.
How big is your move?
Six questions, about a minute. Rough answers are fine. You see what drives the size of your move, which Salesforce limits apply to your edition, and what you get at the end. Nothing is sent anywhere.
Chapter 2 of 6Your data
What exactly happens to my data?
Each Salesforce object becomes a Twenty object, standard or custom, and each field a Twenty field of the right type. Pick an object below and watch where its fields go. Green moves as it is, amber is rebuilt in Twenty, red cannot move, and we tell you why before you pay. Weighing Twenty itself first? Read our honest review of Twenty CRM.
Pick an object, see where it lands
Accounts
Become Companies in Twenty, matched by their web domain.
7 move1 rebuilt1 cannot move
- Account Name, WebsiteName and DomainMovesThe domain is written as https://domain.com, the form Twenty matches on, so email and calendar sync later makes no duplicates.
- Account OwnerAccount Owner (workspace member)MovesYour users are invited to Twenty and accept before the load, as Twenty’s guide says, so each owner matches a member by email. Owners who left are kept as text.
- Parent AccountA relation to CompaniesMovesA relation field we add, set by Salesforce ID through Twenty’s API.
- Type, Industry (picklists)Select fieldsMovesEvery option is created in Twenty first and loaded by its API name; an import adds no options. Inactive values on old records are kept.
- Billing addressAddress fieldMovesStreet, city, state, postal code and country go into the parts of Twenty’s address field.
- Annual Revenue (currency)Currency fieldMovesTwenty keeps the amount and the currency code together, so a multi-currency org keeps each record’s currency.
- Record TypeA select field and viewsRebuiltThe value moves; the page layout per record type is rebuilt as Twenty views.
- Formula and roll-up fieldsRedesigned: a workflow or a BI toolCannot moveSalesforce always leaves them out of its exports, and Twenty has no formula field to receive them. The rebuild list says what replaces each one.
- Salesforce IDA text field marked uniqueMovesThe 18-character ID. Twenty links records by a unique field, so every link and every check can be run again from it.
Contacts
Contacts and leads become People, linked to their company.
6 move
- Name, Email, Phone, TitleName, Emails, Phones, Job TitleMovesTwenty needs each email to be unique, so duplicates are merged in the data map. Phones split into number, country and calling code.
- Account (lookup)Company (relation)MovesLinked by the company’s Salesforce ID; companies always load first.
- Contact OwnerA workspace member fieldMoves
- Email Opt OutA boolean fieldMovesKept so nobody who opted out is emailed again from Twenty.
- Leads and Lead StatusPeople with a lead status, or a Leads objectMovesTwenty has no lead object of its own. You choose in the data map, and whether converted leads move too.
- Person accountsPeopleMovesSalesforce’s contact export holds only the fields contacts and person accounts share; we read the rest from the account.
Opportunities
Become Opportunities, with stages as a select field.
5 move2 rebuilt
- Opportunity Name, Amount, Close DateName, Amount (currency), Close dateMoves
- StageStage (select field)MovesYour stages are created as options first, in your order, and drive Twenty’s Kanban view.
- AccountCompany (relation)Moves
- Contact RolesA custom object linking people and opportunitiesRebuiltTwenty’s import cannot set links that are many on both sides yet, so each role is a record of its own, set through the API.
- Products, price books, line itemsCustom objectsRebuiltTwenty has no product or quote object; a workflow can build a quote PDF on the record.
- Stage and field historyA dated note on the opportunityMovesSalesforce keeps field history for 18 months (24 through the API) unless you have Field Audit Trail. Older history no longer exists.
- Forecast category, ProbabilitySelect and number fieldsMoves
Custom objects
Become Twenty custom objects, with their fields and links built first.
3 move2 rebuilt1 cannot move
- Custom objects (__c)Twenty custom objectsMovesEvery Twenty plan has unlimited custom objects and fields. Each one is created before its data loads.
- Custom fieldsFields of the matching typeMovesText, number, date, boolean, select, multi-select, currency, link, email and phone fields are made to match.
- Lookup and master-detail fieldsRelationsMovesLoaded in dependency order, parents first, each link set by Salesforce ID.
- Junction objects (many-to-many)A custom object of its ownRebuiltTwenty’s import cannot set many-to-many links yet; the junction records keep both sides.
- Validation rulesRequired fields and workflow checksRebuiltTwenty has no validation rules in the Salesforce sense; the rebuild list says what replaces each one.
- Apex triggers and classesRedesigned, or a reason to stayCannot moveCustom code does not move. Twenty’s developers write apps in TypeScript; we scope a replacement or tell you to stay.
Activities
Tasks, events, notes, Chatter and emails stay on the records they belong to.
5 move1 rebuilt
- Tasks and logged callsTasks, linked to the person, company and opportunityMovesLoaded through the API: a file import cannot link one task to several records. Due dates and status kept.
- Events (meetings)Tasks with a date and time, or an Events objectMoves
- NotesNotes on each linked recordMovesPosted through the API with the original date and author written at the top.
- Chatter posts and commentsNotesMovesSalesforce’s export cuts each post at 1,000 characters. With API access we read them in full.
- Emails, Email-to-CaseNotes on the person or caseRebuiltOld Salesforce emails come as notes. From go-live, each user connects their own mailbox and calendar in Twenty.
- Archived activitiesTasks and notesMovesRead with Export All, which also reaches archived and deleted records.
Files
Files and attachments land on the record they belong to, with their real names.
4 move1 cannot move
- Salesforce Files (latest version)Attachments on the linked recordMovesTwenty’s file import carries no files, so each is uploaded through the API, matched through ContentDocumentLink and renamed from its title.
- Classic attachmentsAttachments on the linked recordMoves
- A file shared to several recordsAttached to each linked recordMoves
- Files in libraries, not on a recordAttachments on a Documents objectMovesNeeds the "Query All Files" permission to see files outside your own libraries.
- Older versions of a fileKept in your export, not in TwentyCannot moveTwenty holds one file per attachment. The full export with every version is handed to you.
The details, for your admin
Everything a Salesforce admin will ask, in folds. Open what matters to you.
Records
Your data model is built before any record loads
Twenty’s import creates records, not fields, and adds no select options. So from the signed data map we create every custom object, field, relation and option in Twenty first, with option values in their API names, then load. A missing field or option is found in the test run, never in the full move.
The load order, and links by Salesforce ID
Twenty links a record to its parent through a field marked unique, and the parent must be there first. So the order is fixed: members, then companies, people, opportunities, custom objects in their own order, then tasks, notes and files. Each record keeps its Salesforce ID in a unique field, and every link is set by that ID, never by name.
Owners who have left, and users who never logged in
Twenty matches an owner by the member’s email, and only once that person has accepted their invitation. We invite your active users before the move and wait for every acceptance. Owners who have left are written into a text field with their old name, so nothing is orphaned and you can reassign them later.
Record types, picklists and currencies
A record type is metadata: the value on each record moves to a select field, and each layout is rebuilt as a Twenty view showing its fields. Picklists become select or multi-select fields, keeping inactive values that old records still use; a dependent picklist becomes two fields, and we note where your team relied on the filtering. Twenty’s currency field keeps the amount with its currency code; it does not convert currencies.
Duplicates and soft-deleted records
Twenty needs each person’s email and each company’s domain to be unique, and a record in Twenty’s trash still counts. Duplicates in Salesforce are found and merged in the data map, so the load never stops on them and no deleted record comes back by mistake.
History and files
Attachments versus Files (ContentVersion)
Salesforce has two kinds of file. Classic attachments sit on one record. Files are ContentVersion records, linked to one or more records through ContentDocumentLink. Salesforce’s export writes both as files named by ID, with a CSV that says which is which. We join them back to their records, give each its real name, and upload it to the Twenty record through the API.
Chatter and notes
Posts, comments and notes become Twenty notes on every record they belong to: a note can sit on a person, a company and an opportunity at once, which is why it is loaded through the API. Author and date are written at the top. The Data Export Service keeps only the first 1,000 characters of each Chatter post; with API access we read the full text.
Field history
Salesforce keeps field history for 18 months, or 24 through the API, unless you pay for Field Audit Trail. History from before tracking was switched on does not exist. What exists moves as a dated note on each record. From go-live, Twenty keeps its own change log on every record.
Emails and calendar
Salesforce emails, Email-to-Case included, move as notes on the person or case, attachments included, so the conversation reads in order. Twenty’s email and calendar sync is connected by each user from go-live, and reads their own mailbox from then on.
Automation and reports
Flows, Process Builder and workflow rules
These are metadata, so no data export carries them, and Twenty’s guide says workflows are rebuilt by hand. We list each one, you mark what is still needed, and we rebuild those as Twenty workflows: a record change, a schedule, a button or a webhook starts them, and they can update records, send email, call an API or run code. Twenty describes no approval process like Salesforce’s; the rebuild list says what replaces each one.
Reports, dashboards and list views
Report definitions do not export. We rebuild the reports your team opens every week as Twenty dashboards and views, list the rest so you can drop them on purpose, and name where a BI tool reading Twenty’s API fits better, such as detailed forecasting.
Apex code, Visualforce and Lightning components
Custom code does not move. We scope a replacement with Twenty workflows, an app in TypeScript or an integration, or we tell you plainly to stay: our Twenty and Salesforce comparison says when staying on Salesforce is the better call.
Access
Profiles, permission sets and sharing rules
There is no one-to-one match, and Twenty’s guide says permissions are set up again after a move. We write down who sees what today and rebuild it with Twenty roles. Twenty’s Pro plan has two roles and no single sign-on; custom roles, row-level permissions and SSO need Organization, also on your own server. Anything Twenty cannot express is listed before you sign the map.
A read-only Salesforce user for the move
A read-only Salesforce user for the move, removed at the end, with the date in writing. On Enterprise, Unlimited and Performance it is an integration user with API Enabled and no edit rights. In Twenty we work with an API key your admin creates for the move, removed at the end too.
Your edition
Essentials and Starter Suite
Salesforce lists the monthly Data Export Service for every edition except Database.com, so Essentials has it; its help pages do not name Starter Suite, so we check your Setup screen in the assessment. Salesforce does not list API access for these editions, so tools such as Data Loader are not an option. We plan the move around the monthly export.
Professional and Pro Suite
The Data Export Service runs every 29 days. API access, which Data Loader and every API tool need, is a paid add-on: Salesforce lists Web Services API at $25 per user per month. Without it, a tool stops with API_DISABLED_FOR_ORG, and Chatter posts come out cut at 1,000 characters.
Enterprise, Unlimited and Performance
API access is on, and the export can run weekly. We read through the API with a read-only user, so full Chatter posts, field history and archived activities can come too.
The export rules that catch people out
- Export files are deleted 48 hours after the email, not counting weekends.
- Files download one at a time, a minute apart, in zips of about 512 MB.
- Formula and roll-up fields are never in the export.
- The Recycle Bin is not in it either.
Every way to get data out, by edition, is in our guide to exporting your Salesforce data.
Where Twenty runs
Twenty Cloud, in Frankfurt
Twenty’s legal FAQ says Twenty Cloud runs on AWS servers in Frankfurt, Germany, and that choosing a region comes in 2027, first for new workspaces. Twenty runs hosting, backups and upgrades. Pro and Organization differ in roles, SSO and API calls; our fit check for Twenty says which plan suits your team.
Your own server, in your own country
Self-hosted, your data stays on your server, in the region you choose, such as AWS in Canada. Someone runs it: a server with at least 2 GB of memory, Docker, PostgreSQL and Redis, daily backups and the encryption key kept safe. On a move to your own server we set Twenty up first and test a restore before any record loads. Our guide to running Twenty on AWS yourself shows each step.
Twenty’s limits that shape the load
- The file import takes 10,000 records a file, one object a file.
- Twenty’s import guide gives its API 100 calls a minute with 60 records each; its pricing page caps Twenty Cloud at 50 calls a minute on Pro and 100 on Organization. Self-hosted, your own server sets the limit.
- Many-to-many links and notes on several records are set through the API only.
Words we use
Object, record, field
An object is a kind of thing (Accounts). A record is one of them (Acme Ltd). A field is one piece of information on it (Industry). Twenty uses the same three words, and calls accounts Companies and contacts People.
Lookup and relation
A lookup is a Salesforce field that points at another record (a contact’s account). Its Twenty version is a relation. A unique field holds a value no two records share, such as the Salesforce ID, and is what Twenty links by.
API, freeze window, cut-over
The API is the door programs use to read and write data. The freeze window is a short, agreed time when nobody edits Salesforce, so the final copy is complete. The cut-over is the moment your team stops working in Salesforce and starts in Twenty.
Cut-over, risks, and where your data lives
Cut-over
A short freeze window, agreed in your quote
We read Salesforce; we never change or delete anything in it. Your team works in Salesforce as usual while we build Twenty, map, test and prepare. For the final move we agree a short freeze window in your quote: nobody edits Salesforce, we make the full copy and run the count check, then your team starts in Twenty.
Changes made during a move are not copied across live from Salesforce, which is also what Twenty’s guide advises: no new data in both systems.
A written rollback plan
Before the cut-over you get a written rollback plan: what we do, and who decides, if something is wrong after the switch. Salesforce stays as it was until you sign the check report, so your team can go back to it if the check fails.
14 days of fixes after go-live
For 14 days after go-live we fix anything that did not arrive as agreed in the data map.
Risks
Links break between records
How we handle it: every record keeps its Salesforce ID in a unique field, parents load before children, and links are set by ID through Twenty’s API, never by name. Links that are many on both sides become records of their own. The check report counts orphans: children whose parent did not arrive.
A field or select option is missing at load time
How we handle it: Twenty’s import creates neither, so the data model is built from the signed map first, options in their API names, and the test run on a sample loads exactly as the full move will.
Owners arrive empty
How we handle it: Twenty can match an owner only to a member who has accepted the invitation. We invite your users early, check every acceptance before the load, and keep owners who have left as text.
Files arrive named by ID, on no record
How we handle it: we join ContentVersion and ContentDocumentLink, restore each name and upload the file to its Twenty record. Files are counted like any object.
The export expires, or your edition has no API
How we handle it: export files live 48 hours, not counting weekends, so we start the export early in the week and watch for the email. Salesforce does not promise when an export finishes. Without API access we plan around the monthly export, or you add API access for the month of the move; your assessment says which is cheaper.
Hosting is decided late
How we handle it: cloud or your own server is settled in the free assessment, before the data map, because it decides the API limits, the sign-in rules and where the data sits. A self-hosted Twenty is built and its restore tested before any record loads. The plan is written back from your Salesforce renewal date.
Region
Where your Twenty data lives
On Twenty Cloud, on AWS servers in Frankfurt, Germany, as Twenty’s legal FAQ says; a choice of region comes in 2027, first for new workspaces. Twenty signs its standard data processing agreement on every plan. Self-hosted, it lives wherever your server is. If your data must stay in Canada or the US, that means your own server, decided before we load anything.
Where we process your data during the move
Where your needs say. Our team is in Canada, so Canada is our first choice. We sign a GDPR data processing agreement on request.
What we will not do
Things we say no to
- Change or delete anything in your Salesforce.
- Move data before you sign the data map.
- Send your data to an AI service without your OK.
- Promise that nothing will differ: we count, and the report gives the reason for every difference.
- Rebuild Apex code as if it were a setting: custom code needs its own plan.
Chapter 3 of 6Trust
Can I trust you with it?
Your CRM holds your customers. Here is what happens before we see a single record, who sees it, and what is left of it when we are done. Then a fair look at the other ways to move.
Before we touch your data
Before the assessment
An NDA, signed first
We sign an NDA before the free assessment, before we see any data. Our standard NDA is ready to send.
People
In-house staff only, named
Only our in-house staff work on your data, and they are named in the NDA. Rakesh Patel, our founder, hosts your free call.
Access
The least access that works
A read-only Salesforce user for the move, removed at the end, with the date in writing.
Location
Processed where you need it
Your data is processed where your needs say. Our team is in Canada, so Canada is our first choice.
Contract
A GDPR agreement on request
For EU personal data we sign a data processing agreement with you, on request.
AI
No AI on your data without your OK
Your data goes to an AI service only if you say yes.
After sign-off
Copies deleted, in writing
When you sign off, our working copies are deleted and we confirm it in writing, with the date.
Twenty
We implement Twenty CRM
We implement Twenty CRM, in Twenty’s cloud or on your own server. We are a certified monday.com partner, not a Twenty partner, and we migrate to any CRM.
Book the call before you share anything
A free 30-minute call, no obligation. Leave with clear next steps, whatever you decide.
Chapter 4 of 6How it runs
How does it run, and what do I get?
Seven steps, each agreed before the next one starts. Open a step to see your part, ours, and what you get from it.
The steps
Free call30 minutesYou do / we do / you get
- You do
- Tell us what you use Salesforce for, when your renewal is, and where Twenty should run.
- We do
- Ask about objects, files, flows and your edition, and say honestly whether to move at all.
- You get
- A clear yes, no or not yet.
NDA, then free assessmentFreeYou do / we do / you get
- You do
- Sign our NDA, then give us a read-only user or your record counts.
- We do
- Count objects, records, files, flows and reports, and settle Twenty’s cloud or your own server.
- You get
- The list of what moves, what we rebuild and what cannot move, and a fixed quote.
Data mapBefore any data movesYou do / we do / you get
- You do
- Sign off the map, including the old fields you leave behind, and invite your users to Twenty.
- We do
- Map every object to a Twenty object and every field to a field, then build them in Twenty.
- You get
- Document 1: the data map.
Test run on a sampleYour own recordsYou do / we do / you get
- You do
- Check a sample of accounts with their people, opportunities, notes and files in Twenty.
- We do
- Load the sample exactly as the full move will.
- You get
- Document 2: the test-run sign-off.
Full moveDates fixed in your quoteYou do / we do / you get
- You do
- Keep working in Salesforce while we prepare, then stop editing it for the agreed freeze window.
- We do
- Make the full copy during the freeze window: export, load, link, and rebuild flows as workflows and reports as dashboards.
- You get
- Document 3: the rebuild list.
Count and cut-overWith a written rollback planYou do / we do / you get
- You do
- Sign the check report, then switch your team to Twenty.
- We do
- Still inside the freeze window, count every object in both systems and explain every difference.
- You get
- Document 4: the check report, and your full Salesforce export.
Fixes after go-live14 daysYou do / we do / you get
- You do
- Tell us anything that looks wrong.
- We do
- Fix what did not arrive as agreed, then delete our working copies.
- You get
- The deletion confirmed in writing, with the date.
The check report you sign
A sample of the report, with made-up numbers. We run it inside the freeze window, after the full copy, so both counts describe the same moment. A real one lists every object in your org. It is one of four documents you keep.
Check report
Sample: made-up figures
| Counted | In Salesforce | In Twenty | Result |
|---|---|---|---|
| Accounts | 1,240 | 1,240 | Match |
| Contacts | 3,875 | 3,875 | Match |
| Opportunities | 912 | 912 | Match |
| Custom objects | 2,604 | 2,604 | Match |
| Activities | 14,306 | 14,306 | Match |
| FilesEach opened from its record. | 2,118 | 2,118 | Match |
| Leads32 converted leads left out, as agreed in the data map. | 520 | 488 | Explained |
| Orphans (links with no parent) | 0 | 0 | Match |
Document 1
Data map
Every Salesforce object and field, and the Twenty object and field it became.
Document 2
Test-run sign-off
The sample you checked, and what you asked us to change.
Document 3
Rebuild list
Each flow, rule, report and dashboard, and what replaced it.
Document 4
Check report
Counts in both systems for every object, and the reason for every difference.
Chapter 5 of 6Cost and time
What does it cost, and how long does it take?
A fixed quote after the free assessment, with the dates in it. The price is fixed once you accept, unless you add to the scope. What moves the number is what your answers to the size check showed: records, files, custom objects and flows, connected tools, your edition and your deadline, plus where Twenty runs. The plan is written back from your Salesforce renewal date.
What sets the price and the dates
Volume
Records and files. Many files mean their own run, because Salesforce hands them over in 512 MB zips, one a minute, and each one goes into Twenty through its API.
Rebuilds
Each flow, validation rule and report you keep is rebuilt by hand in Twenty. Dropping the ones nobody uses saves money.
Your edition
Without API access, the move follows Salesforce’s monthly export, which fixes some dates for us.
Where Twenty runs
Twenty’s cloud needs no server work. Your own server is set up, backed up and restore-tested before the move; the build after it is our Twenty CRM implementation work.
Chapter 6 of 6Book
Ready when you are
One free assessment: NDA first, then we size your move, list what moves, what we rebuild and what cannot move, and send a fixed quote. Your answers to the size check come with you.
Book your free call
Free 30-minute call

with Rakesh PatelFounder and CEO of TaskRhino
- Talk through your CRM with the team that implements Twenty
- Leave with clear next steps, whatever you decide
- No obligation
- NDA signed before we see any data
- We reply in 2 business days or less
- A fixed quote after the free assessment
Send a message instead
Your size-check answers are already in the message. Change anything you like.
Questions people ask
Why not just import the Salesforce CSV files into Twenty?
Twenty’s file import takes 10,000 records a file, one object a file, and creates records but not fields or select options. It cannot link a note or task to several records, set links that are many on both sides, or carry files. Your data model has to exist first, and the rest goes in through Twenty’s API, which is what we use.
Should we use Twenty Cloud or host Twenty ourselves?
Twenty Cloud runs on AWS servers in Frankfurt, Germany, and Twenty runs it for you. If your data must stay in Canada or the US, host it on your own server, which someone must keep backed up and upgraded. Our AWS self-hosting guide shows what that takes; the free assessment settles it before the data map.
Can our team keep working during the move?
Yes, until the final copy. For that we agree a short freeze window in your quote when nobody edits Salesforce; we make the full copy and the count check, then your team starts in Twenty. Changes are not copied across live from Salesforce. Salesforce stays untouched until you sign the check report.
What happens to our Salesforce flows and Apex code?
No data export carries them. We list each flow, and rebuild the ones you need as Twenty workflows, which start on a record change, a schedule, a button or a webhook. Twenty describes no approval process like Salesforce’s, and Apex does not move: we scope a replacement, or tell you plainly to stay.
What if something is missing after go-live?
For 14 days after go-live we fix anything that did not arrive as agreed in the data map. Before that, the written rollback plan says what happens if the switch itself goes wrong.
How much does it cost?
A fixed quote after the free assessment. It depends on your records, files, custom objects, flows, edition and where Twenty runs; the size check on this page shows which of those drive your move.
Is Twenty the right CRM to leave Salesforce for?
Often, for a team that wants to own its data and pay less a seat, but not always. Our guide to leaving Salesforce sets Twenty beside the other CRMs, and the open-source Salesforce alternatives page compares the self-hosted ones. Still deciding? Our Twenty CRM consulting team reviews your Salesforce setup before you decide. We migrate to any CRM; see also our Salesforce to monday.com migration.
Sources
- 01Salesforce Help: Export Backup Data from SalesforceEditions, the 7 and 29 day intervals, files options, formula fields left out, the 1,000-character Chatter limit, 512 MB zips, one download a minute, 48 hours not counting weekends.https://help.salesforce.com/s/articleView?id=sf.admin_exportdata.htm&language=en_US&type=5Open Salesforce Help: Export Backup Data from Salesforce in a new tab
- 02Salesforce Help: Data Export FAQRecycle Bin data is not included in the export.https://help.salesforce.com/s/articleView?id=000383962&type=1Open Salesforce Help: Data Export FAQ in a new tab
- 03Salesforce Developers: API compatible editionsAPI access by edition; Professional only with the add-on; API_DISABLED_FOR_ORG.https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_rest_compatible_editions.htmOpen Salesforce Developers: API compatible editions in a new tab
- 04Salesforce: Sales Cloud pricingWeb Services API listed at $25 per user per month.https://www.salesforce.com/sales/pricing/Open Salesforce: Sales Cloud pricing in a new tab
- 05Salesforce Help: Field history tracking18 months, 24 through the API, unless Field Audit Trail.https://help.salesforce.com/s/articleView?id=xcloud.tracking_field_history.htm&language=en_US&type=5Open Salesforce Help: Field history tracking in a new tab
- 06Salesforce Developers: Export data with Data LoaderExport versus Export All (archived and deleted records).https://developer.salesforce.com/docs/atlas.en-us.dataLoader.meta/dataLoader/exporting_data.htmOpen Salesforce Developers: Export data with Data Loader in a new tab
- 07Twenty docs: Migrating from other CRMsFields first, users invited and accepted first, the import order, files not in a file import, views, workflows and permissions recreated by hand, no new data in both systems.https://docs.twenty.com/user-guide/data-migration/how-tos/migrating-from-other-crmsOpen Twenty docs: Migrating from other CRMs in a new tab
- 08Twenty docs: Import relationsLinks by a unique field, parents first; no links to several object types or many-to-many in a file import.https://docs.twenty.com/user-guide/data-migration/capabilities/import-relationsOpen Twenty docs: Import relations in a new tab
- 09Twenty docs: File formatsCSV, XLSX or XLS, 10,000 records a file, one object a file.https://docs.twenty.com/user-guide/data-migration/capabilities/file-formatsOpen Twenty docs: File formats in a new tab
- 10Twenty docs: Prepare your CSV filesSelect values by API name, currency, phone, address and email rules, unique emails and domains, soft-deleted records.https://docs.twenty.com/user-guide/data-migration/how-tos/prepare-your-csv-filesOpen Twenty docs: Prepare your CSV files in a new tab
- 11Twenty docs: Import data via API100 calls a minute, 60 records a call, professional services for 100,000+ records.https://docs.twenty.com/user-guide/data-migration/how-tos/import-data-via-apiOpen Twenty docs: Import data via API in a new tab
- 12Twenty docs: Legal FAQTwenty Cloud on AWS servers in Frankfurt, Germany; region choice from 2027; the data processing agreement on every plan.https://docs.twenty.com/user-guide/legal/how-tos/legal-faqOpen Twenty docs: Legal FAQ in a new tab
- 13Twenty: PricingPro and Organization, roles, SSO and API calls a minute, unlimited custom objects and fields, the core free to self-host.https://twenty.com/pricingOpen Twenty: Pricing in a new tab